Subj : Questions about nodelist and Binkd...
To   : Fred Riccio
From : Robert Bashe
Date : Sun Sep 04 2016 09:46 am

Fred Riccio wrote to Robert Bashe on Saturday September 03 2016 at 09:07:

FR> 03 Sep 16 13:39, Robert Bashe wrote to Richard Menedetter:

RB>> That is NOT enough. I also use a nodelist converter, but the result
RB>> does NOT include passwords.

FR> Or you can hook into the I-BINKD file area, and Binkd.Txt will be
FR> delivered to your door weekly.

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

RB>> An example of a line at the END of binkd.cfg (with with word
RB>> "PASSWORD" instead of the real password) is:

RB>> # Fred Riccio
RB>> node 1:132/174 asok.dtdns.net PASSWORD -

FR> You can get rid of that line.  I removed the password from my end when
FR> we finished testing that SRIF program.

;-) Actually, the line had no password to begin with. I just used it as an 
example.

Perhaps I should add the information that I had a "super-GAU" (both motherboard 
AND HDD became defective at the same time) a couple of weeks ago, and had to 
jury rig a replacement based on a backup from April 2014. I've meanwhile 
adjusted the configuration to work properly, but anything between April 2014 
and July 2016 is not necessarily included. So any password we might have agreed 
on during the meanwhile has been lost.

Cheers, Bob

--- GoldED+/W32 1.1.5-0613
 * Origin: Jabberwocky System - 02363-56073 ISDN/V34 (2:2448/44)

.