Hi g00r00
In the default Mystic install for the BinkP server settings, do you think you >could change the 'Allow Unsecure' switch to be Yes instead of No ?
I ask as there's been some discussion in a Fido Test echo in the last 24 >hours about this setting leading to Mystic BBS being unable to be contacted >by other unknown BBS wishing to send netmail to them.
Mark Lewis was making the following arguments for allowing unsecured >connections by default and why the current 'No' setting is not such a good >idea..
[snip]
now think about this...
1. some NC, RC or ZC is trying to get hold of you... there's no existing >connection between you... how are they supossed to drop off mail?
2. you are wanting to join a network so you try to netmail the *C of the >net/region/zone you would be in... that *C is running mystic and has this >setting ON... how are you supposed to drop off your new node application?
3. there's a election of some sort... your *C is trying to solicit input for >the vote they will cast... they send netmail to those folks in their area... >they cannot deliver to mystic nodes with this setting turned on and there's no >known route to them...
can you see how this is a bad option?? random people connecting is what FTN >networks are all about... folks whine and cry about routed netmail... if it >works, they're crying because someone in the path might read it... ok, so they >try connecting directly but the destination has this setting ON so they cannot >drop off their very important and private netmail... there's no way to get >hold of the destination to set up a connection... protectionism is one thing...
this setting is quite another because it breaks the "all nodes can connect to >all other nodes" design of the network... if there's a node contacting yours >system and causing you problems, password out that one node but don't block >everyone by default...
[snip]
Of course he's talking in terms of a Fidonet perspective but I tend to agree >with most of his arguments. Can you ponder and if you find yourself in general >agreement with the above thinking, consider making a change to that default >setting?
Thanks for considering this.
Best, Paul
--- Mystic BBS v1.12 A37 2017/12/07 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
In the default Mystic install for the BinkP server settings, do you
think you could change the 'Allow Unsecure' switch to be Yes instead of
No ?
Of course he's talking in terms of a Fidonet perspective but I tend to agree with most of his arguments. Can you ponder and if you find
yourself in general agreement with the above thinking, consider making a change to that default setting?
I chatted with him too, but tend to agree it should be yes default. Is it defaulted to yes, though. Someone said it was.
Please pass the message along or forward this one, whatever works. :)
I'll update the tosser to default to toss unsecure packets too.
I'll update the tosser to default to toss unsecure packets too.
Not sure how much of this you want to do. Tossing unsecure netmail, yes. Echomail, probably not.
g00r00 wrote to Avon on 12-09-17 17:28 <=-
In the default Mystic install for the BinkP server settings, do you
think you could change the 'Allow Unsecure' switch to be Yes instead of
No ?
Of course he's talking in terms of a Fidonet perspective but I tend to agree with most of his arguments. Can you ponder and if you find
yourself in general agreement with the above thinking, consider making a change to that default setting?
I also agree with both you and Mark. It was an oversight on my part
with the new server configuration and defaults. I will have it fixed starting with the next pre-alpha and all releases moving forward.
I'll update the tosser to default to toss unsecure packets too.
In the default Mystic install for the BinkP server settings, do you
think you could change the 'Allow Unsecure' switch to be Yes instead of
No ?
Of course he's talking in terms of a Fidonet perspective but I tend to
agree with most of his arguments. Can you ponder and if you find
yourself in general agreement with the above thinking, consider making a
change to that default setting?
I also agree with both you and Mark. It was an oversight on my part with the new server configuration and defaults. I will have it fixed starting with the next pre-alpha and all releases moving forward.
I'll update the tosser to default to toss unsecure packets too.
Please pass the message along or forward this one, whatever works. :)
On this option though I think it would be better if the default was to
not accept and toss unsecured echomail packets/bundles. Or at the very least accept but flag as unsecured or bad packets/bundles.
On this option though I think it would be better if the default was to
not accept and toss unsecured echomail packets/bundles. Or at the very least accept but flag as unsecured or bad packets/bundles.
Static wrote to Jeff Smith <=-
IIRC my old Fidonet setup had a pretty bog standard Frontdoor configuration and what it did with unsecure packets was toss the
netmail as normal but any echomail got tossed into a badmail directory where I could either delete it or retoss it with bad2pkt later.
What Mystic currently does with unsecure packets if you accept them is toss the netmail and silently delete the echomail whether you want it
to or not, which is a little naughty.
I'll update the tosser to default to toss unsecure packets too.
Not sure how much of this you want to do. Tossing unsecure netmail, yes. Echomail, probably not.
Mmmmm... not too sure tossing unsecure echomail pkts is a good idea... IMO..
Mystic will never toss unsecure echomail. Enabling unsecure means Netmail.
Mystic will never toss unsecure echomail. Enabling unsecure means Netmail.
g00r00 wrote to Bill McGarrity on 12-11-17 12:53 <=-
Mmmmm... not too sure tossing unsecure echomail pkts is a good idea... IMO..
Mystic's tosser does not toss unsecure echomail under any occasion, the unsecure setting is whether or not to process those PKTs for Netmail. Echomail is skipped and logged.
g00r00 wrote to Accession <=-
Mystic will never toss unsecure echomail. Enabling unsecure means Netmail.
Mystic will never toss unsecure echomail. Enabling unsecure means Netmail.
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 162:55:32 |
| Calls: | 2,076 |
| Calls today: | 2 |
| Files: | 11,137 |
| Messages: | 947,126 |