In portable mode a "unwanted" file /pybitmessageqt.conf  will appear in the local dir.

To get rid of it, put an

export statement in your ~/.bashrc  for XDG_CONFIG_HOME

Then the  ~/.config/PyBitmessage   will stay absolutely empty in portable mode.

> ~/.config/PyBitmessage/pybitmessageqt.conf file is not a
> PyBitmessage configuration file.

> The pybitmessageqt.conf file is a qt thing, it stores the settings
> of the PyBM window size and whatever you can resize or move (with)in
> it. You may try to set the XDG_CONFIG_HOME env variable.

Try running it like this:
>
> XDG_CONFIG_HOME=/some/portable/path/ python bitmessagemain.py
>
> and check whether the pybitmessageqt.conf gets created there.

http://bm6hsivrmdnxmw2f.onion/chan/gene … f97f3e2d93

back reference into BM 

> Correction:
>
> > nodes will delete an object that has a PoW for less than 5 minutes
> Objects that expire in less than 5 minutes have, for the purpose of
> PoW validation, a TTL of 5 minutes (line 468 - 469 shared.py).
> Objects are deleted between 3 hours and 5 hours 3 minutes past their
> expiry (line 210 of shared.py; called by singleCleanerThread every 2
> hours 3 minutes)
>
> ------------------------------------------------------
> Correction:
>
> > The minimum TTL that PyBitmessage will currently allow for new
> > messages is 1 hour.
> This is for sending broadcasts, for normal messages it's 5 minutes
> (nodes will delete an object that has a PoW for less than 5 minutes)
> but the TTL label doesn't have sufficient precision to describe
> times lower than 1 hour. Also, the PoW adds some randomness to the
> TTL, and the expiration date is determined when the PoW starts
> rather than when it finishes so I don't recommend going as low as 5
> minutes.

above post refers to pyBM installed in Arch or a derivate like Manjaro or Parabola Linux.

what is missing is the wiki-undocumented way to use green light BM over tor

with hidden service keys.dat setting

set up BitMessage over TORnet - version 11 :
############################################

check the settings table at

https://bitmessage.org/wiki/FAQ#How_do_ … ice_on_Tor

Edit your torrc - on Ubuntu, Arch, etc. it's /etc/tor/torrc -
and add a hidden service for bitmessage:

HiddenServicePort     8444   127.0.0.1:8444
HiddenServiceDir             /var/lib/tor/bitmessage

look up the content of        /var/lib/tor/bitmessage/hostname afterwards to fill in keys.dat  at onionhostname , e.g.

onionhostname = yufrurfrkv64.onion 

hint 1: delete hostname + privKey file, then restart tor to have a new .onion generated, then update "keys.dat" accordingly (i.e. copy the value).

hint 2: using SelekTOR or TorBrowser-bundle (hardened or soft) is not recommended for a quick success of getting the green traffic light in pyBM.
        Use "regular system tor" via systemD-KCM or CLI instead.

------------------------------------------------------------------------ torrc section for reference

############### This section is just for location-hidden services ###

## Once you have configured a hidden service, you can look at the
## contents of the file ".../hidden_service/hostname" for the address
## to tell people.
##
## HiddenServicePort x y:z says to redirect requests on port x to the
## address y:z.

# inside of the HiddenServiceDir
# you'll find the value for "onionhostname = " of keys.dat file , stored in file hostname

HiddenServiceDir   /var/lib/tor/bitmessage
HiddenServicePort  8444 127.0.0.1:8444

#HiddenServiceDir /var/lib/tor/hidden_service/
#HiddenServicePort 80 127.0.0.1:80

#HiddenServiceDir /var/lib/tor/other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServicePort 22 127.0.0.1:22

----------------------------------------------------------------  end of section

----------------------------------------------------------------  example tor unit file for ref.:

[Unit]
Description=Anonymizing Overlay Network
After=network.target

[Service]
User=tor
Type=simple
ExecStart=/usr/bin/tor -f /etc/tor/torrc
ExecReload=/usr/bin/kill -HUP $MAINPID
KillSignal=SIGINT
LimitNOFILE=8192
PrivateDevices=yes

[Install]
WantedBy=multi-user.target

----------------------------------------------------------------- end of unit file for ref.

Then restart tor , possibly using the selekTOR GUI.

----------------------------------------------------------------- edit the keys.dat

keys.dat is the control file of pyBM  -- SUMMARY:
----------------------------------------------------------------- example of keys.dat
[bitmessagesettings]
settingsversion = 10

timeformat        = %%a, %%d %%b %%Y  %%I:%%M %%p
keysencrypted     = false
messagesencrypted = false

## put in YOUR value from HiddenServiceDir ---> /var/lib/tor/bitmessage/hostname
onionhostname = yufrurfrkv64.onion   

onionbindip = 127.0.0.1
onionport   = 8444
port        = 8444

sockshostname       = 127.0.0.1  ## otherwise you will only be able to accept one (simultaneous) connection. This will be fixed in the future.
sockslisten         = False      ## then no clearnet connects are made at all

socksport           = 9054
socksproxytype      = SOCKS5

socksusername       =
sockspassword       = without it a hacker can hack ure sox !
socksauthentication = False

sendoutgoingconnections = True

-------------------------------------------------------------------- end of example keys.dat

The first port (in this case 8444) you (then) have to put as
"onionport" variable into "keys.dat" file in PyBitmessage portable (or non-p.) dir.

onionport = 8444

The second port (in this case: 8444 , too)
is the port you have in PyBitmessage network settings
as "Listen for connections on port" (variable "port" in keys.dat).

port = 8444

The IP address (here 127.0.0.1) is the internal (local) address of
your PyBitmessage.

If you run Tor and PyBitmessage on the same (local) system,
it will usually be 127.0.0.1.

This address 127.0.0.1 you then have to  put as "onionbindip"
into your keys.dat control file.

onionbindip = 127.0.0.1

If you want to accept  connections from both clearnet and tornet,
that step is not necessary, however.

onionhostname = hostname_of_YOUR_individual_hidden_service.onion # is taken from the file "hostname" in the respective hidden service directory, usually

/var/lib/tor/bitmessage

  or whatever was defined in torrc (see above).

----------------------------------------------------------------- launch pyBM and that's it ! you're good to go. you might want to delete the knownNodes file.

--- remarks:

It can take a long time to actually get an incoming connection on
the hidden service, depending on circumstances and your other
settings, it may be hours. However, once your onion address makes it
onto the list in the network ("known nodes"), it should be faster.

PS. I just committed some minor fixes to the Tor code, you may want
to pull them.

Peter Surda
Bitmessage core developer

 
 
------------------------------------------------------------------------ 

   You probably want to tell people what exactly to do to use onions,
   step by step. Lines in torrc, etc.   --> find it above!

 

  yeah, the minimum steps to get green light.

  using SelekTOR would be helpful as it is a GUI.
  If so, remember to have port to 9054 by default in both pyBM and SelekTOR.

A note about security: using the Bitmessage API remotely

---

It is insecure to use a remote Bitmessage API directly, as all XMLRPC API calls go over the web using http in cleartext. That means when your Inbox is downloaded, or when you send a message, the content goes out over the web in plain text (unencrypted).

To protect against this, it is better to open an SSH tunnel to the host your PyBitmessage API/server is running on.

You can forward a local port on your computer to a destination port (typically 8442) on the server

(you only need to open up  port 8444 in your firewall on the server
to transmit to and from the Bitmessage peers,

you do not need to open up port 8442 for the API,
as the tunnel will connect locally to it on the server).

This command will forward port 8422 on your local computer to port 8442 on the server,
using SSH as a tunnel (typically port 22) to your Bitmessage server host:

ssh -N -L 8442:localhost:8442 <remote-bitmessage-server-hostname>

When you use an API based app such as Bmr,  when you  login to Bmr locally, just use localhost as the hostname and port 8442.

This will encrypt all communication to the API using SSH before it leaves your computer.
You can use whatever port you want locally (the first port defined above).

For windows: use Putty and setup an SSH tunnel for Source port 8442 and
Destination localhost:8442 under Tunnels. Then connect normally to your host via SSH Session

By doing this, you are effectively making the API calls directly on the server over SSH.

So they are not going out over the web using http to the API.

Login to PyBitmessage server (use SSH tunnel for remote access): ...

in other words:

nobody wants       ~/.config/PyBitmessage/pybitmessageqt.conf

in ~./bashrc

export XDG_CONFIG_HOME=/someShitPathToDumpCrapIn

bitmessage.mybb.rocks/viewtopic.php?id=8#p38