Hello All!

So I am not so convinced this issue is with my setup, I scoured my binkd logs and cannot find where that micronet system has ever sent me anything even though they claim there is traffic. So I sent that sysop a message to make sure that system is even packing anything for mine, however I did see an odditity atleast to me in the logs, and it only exists while polling this system, none of the others

? 11 Feb 00:00:36 [78274] Warning: remote set UNSECURE session
+ 11 Feb 00:00:36 [78274] pwd protected session (MD5)

Could that keep my system from picking up mail at this particular hub? Just trying to find anything and this is all I can find. Everything else is as it should be. I will add the system I am polling is running synchronet.

Regards,

Rick

... Taglines: the license plates of BBSing.
--- GoldED+/LNX 1.1.5-b20220504
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

So I am not so convinced this issue is with my setup, I scoured my binkd logs and cannot find where that micronet system has ever sent me anything even though they claim there is traffic. So I sent that sysop a message to make sure that system is even packing anything for mine, however I did see an odditity atleast to me in the logs, and it only exists while polling this system, none of the others

Regardless of your domain lines if that node has sent you anyhing it should arrive in your inbound. Check the unprotected inbound also.

? 11 Feb 00:00:36 [78274] Warning: remote set UNSECURE session
+ 11 Feb 00:00:36 [78274] pwd protected session (MD5)

I am not certain but I think this happens when the remote node doesn't have both an inbound and secure inbound set. It's nothing you need to worry about. Binkd reposts a secure session.

Could that keep my system from picking up mail at this particular hub? Just trying to find anything and this is all I can find. Everything else is as it should be. I will add the system I am polling is running synchronet.

The domain lines will cause your node to not find/send outgoing mail if they are setup wrong.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Rick,

The domain lines will cause your node to not find/send outgoing mail
if they are setup wrong.

My last comment.. ;)

Question 22 in the binkd faq that is posted in this area talks about the domain lines when using a tosser that doesn't support a 5D outbound.

Ttyl :-),
Al

... "640K ought to be enough for anybody." Bill Gates '81
--- GoldED+/LNX 1.1.5-b20230205
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Rick wrote (2023-02-11):

Hello All!

So I am not so convinced this issue is with my setup, I scoured my binkd logs and cannot find where that micronet system has ever sent me anything even though they claim there is traffic. So I sent that sysop a message to make sure that system is even packing anything for mine, however I did see an odditity atleast to me in the logs, and it only exists while polling this system, none of the others

? 11 Feb 00:00:36 [78274] Warning: remote set UNSECURE session
+ 11 Feb 00:00:36 [78274] pwd protected session (MD5)

This means your system is sending a session password, but the remote session has no password set for incoming connections and returns M_OK 'non-secure', which gets logged as "Warning: remote set UNSECURE session".
(a wrong password should return an error)

It is not a password protected or encrypted session, even if binkd tells you so. It is a security flaw of binkd though.

---
* Origin: War is Peace. Freedom is Slavery. Ignorance is Strength. (2:280/464.47)

Hello Alan!

Saturday February 11 2023 07:38, you wrote to me:

* Forwarded from area 'BINKD'
Hello Rick,

The domain lines will cause your node to not find/send outgoing
mail if they are setup wrong.

My last comment.. ;)

Question 22 in the binkd faq that is posted in this area talks about
the domain lines when using a tosser that doesn't support a 5D
outbound.

Thanks Al, since I cant find a record of my system receiving anything from that node, I am going to have to assume that the issue is on his end. I can send out and post to micronet echos, others see them and respond but I do not get any mail back. I have looked in all dir, binkd never reports receiving a pkt from that node. But thanks again for your help.

Regards,

Rick

... Citation for slow BBSing: Going v.32bis in a v.FC lane
--- GoldED+/LNX 1.1.5-b20220504
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)

? 11 Feb 00:00:36 [78274] Warning: remote set UNSECURE session
+ 11 Feb 00:00:36 [78274] pwd protected session (MD5)

This means your system is sending a session password, but the remote session has no password set for incoming connections and returns M_OK 'non-secure', which gets logged as "Warning: remote set UNSECURE session".
(a wrong password should return an error)

It is not a password protected or encrypted session, even if binkd tells you so. It is a security flaw of binkd though.

Is that a misconfiguration at the remote end, there is no (or an incorrect) password set?

Binkd should not log "pwd protected session (MD5)" in that case.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Rick,

Thanks Al, since I cant find a record of my system receiving anything
from that node, I am going to have to assume that the issue is on his
end.

Somethings up but hard to say what. Going by Oli's comments it sounds like there may be an unconfigured or wrong password at one end of the link. Double check your password. Session passwords are case sensitive so "PASSWORD", "password" and "PassWord" are all different.

You may have to email the sysop at the other end and compare logs/notes.

Question: Is your tosser working in 5D mode, and if so what tosser are you using?

Ttyl :-),
Al

... But that trick never works! -Rocky
--- GoldED+/LNX 1.1.5-b20230205
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)

Alan wrote (2023-02-11):

? 11 Feb 00:00:36 [78274] Warning: remote set UNSECURE session
+ 11 Feb 00:00:36 [78274] pwd protected session (MD5)

This means your system is sending a session password, but the remote
session has no password set for incoming connections and returns M_OK
'non-secure', which gets logged as "Warning: remote set UNSECURE
session". (a wrong password should return an error)

It is not a password protected or encrypted session, even if binkd
tells you so. It is a security flaw of binkd though.

Is that a misconfiguration at the remote end, there is no (or an incorrect) password set?

See http://ftsc.org/docs/fts-1026.001

* M_OK "non-secure"
report to remote about normal password unprotected
session; usually used for empty password;

I think an incorrect password should return an M_ERR and close the connection.

But it depends on the server. A man in the middle, a compromised server or a weird implementation could just ignore the password and send back M_OK "secure".

Binkd should not log "pwd protected session (MD5)" in that case.

I always use the -md option (require CRAM-MD5) for the node and check for CRYPT in the perl hook script. A CRYPT session works only if both parties use the same password.

---
* Origin: War is Peace. Freedom is Slavery. Ignorance is Strength. (2:280/464.47)