Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 275  |
|  Oli to Alan Ianson  |
|  Pssword ord ord case insensitive or not?  |
|  22 Apr 20 22:34:47  |
 REPLY: 1:153/757 5ea0a6e5 MSGID: 2:280/464.47@fidonet 5ea0ad18 PID: GED+LNX 1.1.5-b20180707 CHRS: UTF-8 4 TZUTC: 0200 TID: CrashMail II/Linux 1.7 22 Apr 20 13:10, you wrote to me: AI> Hello Oli, Ol>> I wonder why we still use packet passwords. Why not create a Ol>> inbound filebox for every node/point that calls and rely on the Ol>> session password? Is there any (open source) mailer or tosser Ol>> that support inbound fileboxes? AI> I use binkd and it does support in and out fileboxes. I have only ever AI> used an outbound filebox for one node and that does what I need it to AI> do. I have never used an inbound filebox so I'm not sure how that AI> would work in practice or if it would fill any real need. I'm not sure AI> my tosser knows how to use an inbound filebox for a link. But you have to define the filebox for every node in advance. I thougt it would be nice to create a filebox for every incoming connection automatically. Argus is very flexible (search for filebox): http://www.artur.pl/hack/ritlabs.ii.pl/argus/hlp/eng/index.html AI> What I would like to see is a proper binkps protocol. We could drop AI> the CRYPT option (when using binkps) and have a fully secure session, AI> regardless of inbound or outbound directories. I don't understand how this is connected to packet passwords and inbound dirs. * Origin: kakistocracy (2:280/464.47) SEEN-BY: 1/123 18/200 90/1 103/705 120/340 601 154/10 203/0 221/0 SEEN-BY: 226/30 227/114 229/426 1014 240/5832 249/206 317 280/464 SEEN-BY: 280/5003 288/100 292/854 8125 310/31 317/3 322/757 342/200 SEEN-BY: 396/45 423/120 633/280 712/848 770/1 PATH: 280/464 229/426 |
[ << oldest | < older | list | newer > | newest >> ]