Subj : why one aka vs another
To   : Paul Hayton
From : Oli
Date : Mon Jun 19 2023 09:53 am

Paul wrote (2023-06-18):

 PH> I have a node in fsxNet running 21:1/167 and have credentials set up in
 PH> BinkD for it.

 PH> When it polls BinkD is showing/logging the fidonet AKA for the incoming
 PH> poll and not the Zone 21 AKA that has been configured at my end.

 PH> I don't have a Fidonet AKA setup in my BinkD for this node, yet my
 PH> instance of BinkD seems to like/accept it?

Are you 100% sure that there is not anything about fidonet in you binkd.cfg (or the included config files)? If there is no fidonet AKA, you should get a "(n/a or busy)" for fidonet too. But maybe I'm missing something.

 PH> Any ideas how I can ensure just the Zone 21 is accepted?

You cannot. It's a flaw of the binkp protocol (inherited from EMSI). The moment you have a password protected session, the incoming connection can dump anything in your ("secure") inbound. That is the reason we have pkt (and tic) passwords.

You can configure some restrictions with the "skip" and "check-pkthdr" keyword, but I'm not sure, if check-pkthdr secure would prevent it.

---
 * Origin: No REPLY kludge - no reply (2:280/464.47)

.