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.
The domain lines will cause your node to not find/send outgoing mail
if they are setup wrong.
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)
* 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.
? 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.
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.
? 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.
Sysop: | Fercho |
---|---|
Lugar: | La Plata, Buenos Aires |
Usuarios: | 33 |
Nodos: | 10 (0 / 10) |
Uptime: | 33:18:36 |
Llamadas: | 118 |
Archivoss: | 15,607 |
Mensajes: | 33,522 |