22 Apr 20 14:12, you wrote to me:
AI> Hello Oli,
Ol>> But you have to define the filebox for every node in advance. I
Ol>> thougt it would be nice to create a filebox for every incoming
Ol>> connection automatically. Argus is very flexible (search for
Ol>> filebox):
Ol>> http://www.artur.pl/hack/ritlabs.ii.pl/argus/hlp/eng/index.html
AI> That's an interesting idea but you'd have to communicate the location
AI> of that inbound filebox to your tosser somehow.
It could be like BSO for inbound. You just need a good specification for the
format.
E.g. Node 7:8/9 calls and received files are put into
inbound/othernet.7.8.9.0/trusted/
or if there is no session password into
inbound/othernet.7.8.9.0/unknown/
No need to specifiy an inbox for every node and point in the mailer's config.
AI>>> What I would like to see is a proper binkps protocol. We could
AI>>> drop the CRYPT option (when using binkps) and have a fully
AI>>> secure session, regardless of inbound or outbound directories.
Ol>> I don't understand how this is connected to packet passwords and
Ol>> inbound dirs.
AI> If we had a reliable/secure session we wouldn't need packet passwords
AI> or inbound directories randomly placed around the file system.
I still don't understand how that helps. What exactly do you have in mind?
The problem is the interface between mailer and tosser. Everyone with a session
password can drop anything in my shared "secure" inbound. So now we need a
packet password, because the information about the session is thrown out the
window and isn't communicated to the tosser. We wouldn't need a packet
password, if the tosser did know that the packet was delivered in an
authenticated session with node 7:8/9.
* Origin: kakistocracy (2:280/464.47)
|
