They'd have to login over something secure (e.g. I actually added key support to enigma but I don't think I ever got around to exposing it to users. Not sure if that's exactly the way to put it, "anonymous," but was wondering how one might handle an SSH-only BBS, particuarly new account creation.įWIW ENiGMA 1/2 also takes the same approach as others - you can define usernames such as "new" that kick off the NUA process.Īs far as passwords being less secure, it's basically just that they are shorter and in general not random unlike a key. On Tuesday, March 16th Alpha was heard saying. * Origin: The Drunken Gamer BBS (21:4/158.1) My internal IP address, unless I found a way to pass this info? Also, botsĪnyone think about doing this, or are they doing this? One potential down side is, all logins will look like they are coming from Might be easier just to allow Telnet new users, but thenįorce login over SSH and change PW on first login. I know, sounds like a lot of work for something that isn't a big problemįor most people. My idea is simple as this: I'd run a custom SSH server, accept a UN/PWĪuth with a generic UN and any PW. I'm 100% positive that smarter people have already been down that road. I'm sure many people are like, who cares? It's a BBS.
SYNCTERM FORUMS PASSWORD
Users creating their intial BBS account with a password in clear text-I'm finally realizing-is a pretty bad idea, LOL. TheĪdvantage being, from day 1, the process is more secure. Would tunnel the user to the telnet login for UN and PW login.
SYNCTERM FORUMS SOFTWARE
Like Syncterm supports BBSs that have 'generic' or anonymous connection usernames over SSH (like "user"), but then essentially the BBS software I saw someone post a git issue for Syncterm today (Deuce?) that seemed
Wondering how one might handle an SSH-only BBS, particuarly new account creation. Not sure if that's exactly the way to put it, "anonymous," but was