https://wiki.bitmessage.org/api.php?action=feedcontributions&user=Sunny256&feedformat=atomBitmessage Wiki - User contributions [en]2024-03-29T05:49:25ZUser contributionsMediaWiki 1.34.0https://wiki.bitmessage.org/index.php?title=Keys.dat&diff=19634Keys.dat2013-08-18T20:55:50Z<p>Sunny256: /* Debugging */ Typo fix</p>
<hr />
<div>keys.dat is a mixture of Bitmessage configuration and [[Address Block|Address blocks]]. It should be protected since it contains sensitive data that can be abused to impersonate others.<br />
<br />
== Location ==<br />
The file is located in the bitmessage directory (if run in portable mode).<br />
On a Windows system in non-portable mode it is in the [http://en.wikipedia.org/wiki/Special_Folders#File_system_directories AppData] and can be reached by typing '''%APPDATA%\PyBitmessage''' in the windows explorers address bar. (Windows Explorer, not Internet Explorer)<br />
<br />
Under Linux it is found in the users home directory: ~/.config/PyBitmessage<br />
<br />
Under OSX it is found in the users home directory: ~/Library/Application Support/PyBitmessage<br />
<br />
== Configuration ==<br />
The keys.dat contains multiple sections:<br />
<br />
=== [DEFAULT] and [bitmessagesettings] ===<br />
Example Configuration<br />
<pre><br />
[DEFAULT]<br />
label = unused address<br />
<br />
[bitmessagesettings]<br />
settingsversion = 5<br />
port = 8444<br />
timeformat = %%a, %%d %%b %%Y %%I:%%M %%p<br />
blackwhitelist = black<br />
startonlogon = False<br />
minimizetotray = True<br />
showtraynotifications = False<br />
startintray = False<br />
socksproxytype = none<br />
sockshostname = localhost<br />
socksport = 9050<br />
socksauthentication = False<br />
socksusername = USER<br />
sockspassword = PASS<br />
keysencrypted = false<br />
messagesencrypted = false<br />
apienabled = true<br />
apiport = 8442<br />
apiinterface = 127.0.0.1<br />
apiusername = API-Username<br />
apipassword = API-Password<br />
defaultnoncetrialsperbyte = 320<br />
defaultpayloadlengthextrabytes = 14000<br />
</pre><br />
<br />
The [[API_Reference|API settings]] are not present by default.<br />
The section may additionally contain a [[Daemon]] entry.<br />
<br />
=== Address Sections ===<br />
The keys.dat contains sections, called [[Address Block|address blocks]].<br />
<br />
== Editing ==<br />
Editing requires shutdown of the client first or changes may be overwritten again by the client.<br />
All fields (except the '''DEFAULT''' section) can be edited in the clients settings dialog. changes can prevent the client from loading or addresses from working and should be taken with care. The keys.dat can be edited in any text editor and has to be saved back as raw text file, rendering office applications rather complicated to use. On windows, [http://en.wikipedia.org/wiki/Notepad_(software) notepad.exe] can be used for this purpose. Notepad can be opened and then the file can be loaded either by using '''File > Open''' or dragging it into the editor.<br />
<br />
== Deleting ==<br />
Deleting the keys.dat renders all addresses generated unusable and causes the client to revert to its default sections.<br />
Messages that were received prior to deletation remain in the [[messages.dat]] file and are still readable.<br />
<br />
== Debugging ==<br />
Instead of deleting, removing of entries is recommended, using the following steps:<br />
* Create a copy of keys.dat in case something rouls up.<br />
* Delete the file and restart bitmessage.<br />
* Close bitmessage, open the newly generated keys.dat and add a message block from the backup.<br />
* Restart bitmessage, if it works, continue adding address blocks.<br />
* If bitmessage no longer works, the invalid message block should be removed from keys.dat and be sent to atheros (on github or the forum) for further debugging.</div>Sunny256