Subj : Re: Packet passwords
To : Mark Hofmann
From : Nicholas Boel
Date : Sat May 28 2016 07:37 am
Hello Mark,
On 27 May 16 11:41, Mark Hofmann wrote to Nicholas Boel:
NB>> While I have limited ways to look at this unless I load DB up in
NB>> dosemu, I suppose it's easy enough to ask. Is there by chance a
NB>> "Session password" setting in the echomail section of DB's config
NB>> as well as a "Session password" setting in the BinkD config
NB>> section?
MH> There is only one location in the DB config for session password. It
MH> is located under "Advanced/Misc Security".
Does the "Advanced/Misc Security" section have any other binkd specific
settings? The session password should only be used during binkd's handshake,
and not in echomail itself.
MH> There is a separate location for a "Packet Password" that is located
MH> under "Packet/Mail Control".
MH> I have verified that I only have "Session Passwords" setup with no
MH> "Packet Passwords". The Packet Password field is totally blank -
MH> never has been used.
Understood.
MH> I can also verify that my hub instance is sending echomail with a
MH> packet password - using what I have setup under "Session Password".
MH> I'm assuming that packet passwords were previously ignored in both
MH> Synchronet and Mystic. That's an assumption, but I have no other
MH> explanation as to why we just recently started noticing this issue.
From what Rob tells me, there was a certain configuration with the old sbbsecho
(which I apparantly used) where it ignored packet passwords. This has been
fixed in the new version.
MH> The solution was simple. I just asked my uplinks to add a Packet
MH> Password to match our session password.
That's definitely a simple "workaround", but not really a solution if we want
to help get the issue found and fixed. :)
