04 Sep 16 09:46, you wrote to Fred Riccio:

 RB> Which still does not address the problem of passwords. I explaind this in
 RB> my message. If you want to communicate with a passworded system, binkd.cfg
 RB> must have the final lines I mentioned, which include the password. Any
 RB> binkd nodelists generated on site or downloaded as you mention are only
 RB> valid for communication with systems not requiring a password.

You can use a separate password file.

=== cut ===
# Format of the password file:
#   [password]  [,[][,]]
# where:
#   [password]               optional "password" token;
#               address of a link in the form 1:2/3.4@domain
#                            or 1:2/3@domain or 1:2/3 or 1:2/3.4;
#                     password for incoming sessions;
#                    packet password, used when "share" token
#                            is handled;
#                    password for outgoing sessions.
# Any password is one word without spaces or tabs. If  or 
# is omitted, it will be assumed equal to . If a password is defined for
# a node by the "node" token, then the passwords for the node in the password
# file will be ignored.
#
passwords ~/ftn/binkd/passwords
=== cut ===

'Tommi

---