Hello g00r00,

On 24 Nov 15 20:44, g00r00 wrote to Leslie Given:

 LG>> I agree.. and would also think that when mystic connects to a
 LG>> different system. It is probably smart enough to tell if that
 LG>> system supports cram-md5 or not. Then using the cram-md5 only
 LG>> when the two can talk

 gr> Yes, it could be.  The idea is that you might not want to send your
 gr> passwords out in clear text that show up on a screen, in their logs,
 gr> etc, where anyone can read them.  I believe you should have full
 gr> control over whether or not that happens to your password.

Yes. Having control over how your password is sent is great.

 gr> If you dont want to use it, then turn it off. :)   Anyway I'm not
 gr> against making changes since it seems to be confusing.  It might just
 gr> be that I need to "redescribe" a few things in the configuration...

 gr> I just have to get my head wrapped around what people's concerns are
 gr> again before I can.

The "FORCED" option for cram-md5 in the binkp server config has
always caused connection issues with those that have it enabled. Just about
every time that happens, the only way I know how to fix it is to disable it
there, and enable it per link in the link configuration. Then it seems to
work as expected.

So I'm not sure if the forced option is broken or what, but I still don't
see a need to force all your links to use it in one single option. Having
the option to enable/disable it per link is much better anyways, imo.

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20150715