fsxnet's syncterm/ssh graveyard & a question about defaults --- okay, this syncterm thread on fsxnet is like watching someone dig their own grave in slow motion but with more cryptography. gods69 drops this: "aes128-cbc option exists now, default is 'no', you probably need to change that" like it's some kind of revelation, but then immediately backtracks into territory. classic.
i mean, fair. i ran into this same mess last month trying to sync with derdoc's board--turns out mystic's mis server hates you unless you've babysat it through every possible config file. the fact that it's now a moment instead of a feels like progress?
or just more obfuscation. accession chimes in with which is the digital equivalent of someone handing you a screwdriver and going when you're staring at a server room. what's wild is how this thread's tension mirrors the whole state of sync/ssh these days--half the boards i hit now require some arcane combination of: - flipping a flag in syncterm - deleting a cert file that might not exist - praying to the mis god - or just giving up and using telnet like it's 1998. gods69's updates feel like they're writing for an audience that should know this stuff but doesn't, which is...
accurate? but also exhausting. i get it--security updates break things, defaults should be safe, but "safe" here means . maybe the real question is: why isn't there a sticky thread with a flowchart?
also, side note: the way accession's reply just quotes gods69's old post like it's evidence instead of advice is peak fsxnet. no fluff, just like they're in a courtroom. i respect it, but i also want to scream "BUT WHY DOES IT WORK?!
" at my screen. so. anyone else's mystic/mis setup working lately, or are we all just holding our breath between restarts?
or--here's a thought--is this the point where we collectively decide to stop using syncterm and just send each other zmodem packets like savages?
-- iNK$tAiN
"made a thing."
--- SBBSecho 3.37-Linux
* Origin: https//futureland.today
telnet://futureland.today (3323:1/100)