I am having an issue with a node I pull a feed from differing from my main hub.

This node uses mystic.

I am using binkd.

For my main hub I've set up session passwords and it polls and sends stuff in a secure mode.

If I poll node y, the special node, it will poll in secure mode, but, if I create a message, and let binkd send it on the next run, it doesn't send in secure mode. Or if the node y calls me, its not secure.

Any ideas????


Log info below.. some changed to protect the guilty.

Here is a poll:

$ cat binkmystic.txt
automated poll via cronjon every 4 horus

rcvd msg NUL VER Mystic/1.12A24 binkp/1.0
- 15 Nov 08:20:01 [2636] VER Mystic/1.12A24 binkp/1.0
15 Nov 08:20:01 [2636] remote uses binkp v.1.0
15 Nov 08:20:01 [2636] rcvd msg ADR 1:39donet
15 Nov 08:20:01 [2636] created /.bsy
+ 15 Nov 08:20:01 [2636] addr: 1:8@fidonet
15 Nov 08:20:01 [2636] created /0.bsy
+ 15 Nov 08:20:01 [2636] addr: 1:0@fidonet
15 Nov 08:20:01 [2636] created /015.bsy
+ 15 Nov 08:20:01 [2636] addr: 11@fidonet
15 Nov 08:20:01 [2636] created /5.bsy
+ 15 Nov 08:20:01 [2636] adonet
15 Nov 08:20:01 [2636] Source IP not checked
15 Nov 08:20:01 [2636] send message NUL TRF 0 0
15 Nov 08:20:01 [2636] send message PWD CRAM-MD5-4c3b5c91ffd1
15 Nov 08:20:01 [2636] rcvd msg OK secure


outbound
05 Nov 16:23:43 [997] started client #1, id=31999
05 Nov 16:23:43 [31999] created /home/r4.csy
+ 05 Nov 16:23:43 [31999] call to 1:fidonet
05 Nov 16:23:43 [31999] resolving `m'...
05 Nov 16:23:43 [31999] trying 764...
05 Nov 16:23:43 [31999] connected
05 Nov 16:23:43 [31999] binkp init done, socket # is 3
+ 05 Nov 16:23:43 [31999] session with .com (4)
05 Nov 16:23:43 [31999] send message NUL SYS
05 Nov 16:23:43 [31999] send message NUL ZYZ
05 Nov 16:23:43 [31999] send message NUL LOC
05 Nov 16:23:43 [31999] send message NUL NDL 115200,TCP,BINKP
05 Nov 16:23:43 [31999] send message NUL TIME Sat, 5 Nov 2016 16:23:43 -0400
05 Nov 16:23:43 [31999] send message NUL VER binkd/0.9.11/Linux binkp/1.1
05 Nov 16:23:43 [31999] send message ADR 1:@fidonet
05 Nov 16:23:43 [31999] send message NUL OPT NDA CRYPT
05 Nov 16:23:43 [31999] touched /home/44.csy
05 Nov 16:23:43 [31999] rcvd msg NUL OPT CRAM-MD5-ebb6d945f0855a45d135642d4f12f659
- 05 Nov 16:23:43 [31999] OPT CRAM-MD5-ebb6d9445d135642d4f12f659
+ 05 Nov 16:23:43 [31999] Remote requests MD mode
05 Nov 16:23:43 [31999] rcvd msg NUL SYS
- 05 Nov 16:23:43 [31999] SYS
05 Nov 16:23:43 [31999] rcvd msg NUL ZYZ
- 05 Nov 16:23:43 [31999] ZYZ
05 Nov 16:23:43 [31999] rcvd msg NUL VER Mystic/1.12A24 binkp/1.0
- 05 Nov 16:23:43 [31999] VER Mystic/1.12A24 binkp/1.0
05 Nov 16:23:43 [31999] remote uses binkp v.1.0
05 Nov 16:23:43 [31999] rcvd msg ADR 1:3
05 Nov 16:23:43 [31999] created /home/4.bsy
+ 05 Nov 16:23:43 [31999] addr: 1:8@fidonet
05 Nov 16:23:43 [31999] created /home/0.bsy
+ 05 Nov 16:23:43 [31999] addr: 1:3/0@fidonet
05 Nov 16:23:43 [31999] created /home/5.bsy
+ 05 Nov 16:23:43 [31999] addr: 1:@fidonet
05 Nov 16:23:43 [31999] created /home/5.bsy
+ 05 Nov 16:23:43 [31999] addr: @fidonet
05 Nov 16:23:43 [31999] Source IP not checked
05 Nov 16:23:43 [31999] send message NUL TRF 0 884
05 Nov 16:23:43 [31999] send message PWD CRAM-MD5-3a49376cc66c1b4e91096bdc33eb7a04
05 Nov 16:23:43 [31999] rcvd msg OK non-secure
- 05 Nov 16:23:43 [31999] sending /home/6a7.sa0 as 6a7.sa0 (884)
05 Nov 16:23:43 [31999] send message FILE 6a7.sa0 884 1478377419 0
05 Nov 16:23:43 [31999] removing flo: /home/4.dlo
05 Nov 16:23:43 [31999] rcvd msg EOB


Inbound:

- 01 Nov 05:00:40 [956] incoming from r.net (4)
01 Nov 05:00:40 [956] started server #1, id=22564
01 Nov 05:00:40 [22564] binkp init done, socket # is 4
+ 01 Nov 05:00:40 [22564] session with r.net ()
01 Nov 05:00:40 [22564] send message NUL OPT CRAM-MD5-2f1b20522956375bbf33bca1a6c0d470
01 Nov 05:00:40 [22564] send message NUL SYS
01 Nov 05:00:40 [22564] send message NUL ZYZ
01 Nov 05:00:40 [22564] send message NUL LOC
01 Nov 05:00:40 [22564] send message NUL NDL 115200,TCP,BINKP
01 Nov 05:00:40 [22564] send message NUL TIME Tue, 1 Nov 2016 05:00:40 -0400
01 Nov 05:00:40 [22564] send message NUL VER binkd/0.9.11/Linux binkp/1.1
01 Nov 05:00:40 [22564] send message ADR 1
01 Nov 05:00:40 [22564] rcvd msg NUL SYS
- 01 Nov 05:00:40 [22564] SYS T
01 Nov 05:00:40 [22564] rcvd msg NUL ZYZ
- 01 Nov 05:00:40 [22564] ZYZ
01 Nov 05:00:40 [22564] rcvd msg NUL VER Mystic/1.12A25 binkp/1.0
- 01 Nov 05:00:40 [22564] VER Mystic/1.12A25 binkp/1.0
01 Nov 05:00:40 [22564] remote uses binkp v.1.0
01 Nov 05:00:40 [22564] rcvd msg ADR 1fidonet
01 Nov 05:00:40 [22564] created /home/r4.bsy
+ 01 Nov 05:00:40 [22564] addr: 1:fidonet
01 Nov 05:00:40 [22564] created /0.bsy
+ 01 Nov 05:00:40 [22564] addr: 1:3@fidonet
01 Nov 05:00:40 [22564] created /home/r15.bsy
+ 01 Nov 05:00:40 [22564] addr: 1:@fidonet
01 Nov 05:00:40 [22564] created /home/5.bsy
+ 01 Nov 05:00:40 [22564] addr: 1@fidonet
01 Nov 05:00:40 [22564] Source IP not checked
01 Nov 05:00:40 [22564] rcvd msg PWD CRAM-MD5-df1d0f640871f84df
? 01 Nov 05:00:40 [22564] unexpected password digest from the remote
01 Nov 05:00:40 [22564] send message OK non-secure
01 Nov 05:00:40 [22564] send message EOB
01 Nov 05:00:41 [22564] rcvd msg FILE b.tu1 788 1477972780 0
01 Nov 05:00:41 [22564] file not found, trying to create a tmpname
- 01 Nov 05:00:41 [22564] receiving 0cb.tu1 (788 byte(s), off 0)
+ 01 Nov 05:00:41 [22564] 0102fecb.tu1 -> /home/b.tu1
01 Nov 05:00:41 [22564] unlinked `/home/b8.hr'
+ 01 Nov 05:00:41 [22564] rcvd: 01b.tu1 (788, 788.00 CPS, 18@fidonet)
01 Nov 05:00:41 [22564] send message GOT 01b.tu1 788 1477972780
01 Nov 05:00:41 [22564] rcvd msg EOB
--- SBBSecho 3.00-Win32
* Origin: Stepping Stone BBS - telnet://vintagebbsing.com (1:298/25)

Hello Lindsay,

On 25 Nov 16 08:15, Lindsay Zellner wrote to All:

I am having an issue with a node I pull a feed from differing from my
main hub.

This node uses mystic.

I am using binkd.

For my main hub I've set up session passwords and it polls and sends
stuff in a secure mode.

In one of your log snips, it says "Remove requests MD mode". Since you're using
binkd, are you using the "-md" switch in your node definition for that system? That will enable MD (CRAM-MD5 encryption) mode for your outgoing polls to that system.

Regards,
Nick

... "?? ????. ? ????? ?????? ???????."
--- GoldED+/LNX 1.1.5-b20160827
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi Lindsay,
it seems that either areafix or the tic passwords are not correct:
rcvd msg PWD CRAM-MD5-df1d0f640871f84df
? 01 Nov 05:00:40 [22564] unexpected password digest from the remote

Try to ask if is possible set the CRAM-MD5 to YES on Mystic or double check
the password systems are case sensitives.

Thanks

Tony

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Friends BBS UK (2:250/4)

25 Nov 16 16:06, Tony wrote to you:

Try to ask if is possible set the CRAM-MD5 to YES on Mystic or double check the password systems are case sensitives.

make sure you do this per node that needs it and not in the default mailer settings area... that one should remain to no because you don't want to force it for all nodes... just only those you connect to and have an agreement to use
it with your connections...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... No one has more driving ambition than the boy who wants to buy a car.
---
* Origin: (1:3634/12.73)