Hello all :) I made this BBS for fun and thought you all would enjoy it. It's not perfect, but it's been a fun exercise!
see it: https://asciinema.org/a/Emg6SWrXMV6cehfQxrw1GRu75
try it:
ssh -p 2223 shhhbb.com
host it:
https://github.com/donuts-are-good/shhhbb/releases/latestwhy?
Every year I challenge myself in some new way, this year it is to push one project per week. You might recognize my static site generator [0] or my releaser for go [1] from previous posts as one of these weekly projects. If you want to join me in doing this, it's been a blast and I highly recommend it! Maybe we can chat on the bbs about it :)
[0] - bearclaw tiny static generator - https://github.com/donuts-are-good/bearclaw
[1] - release.sh release builder for go - https://github.com/donuts-are-good/bearclaw
need:
I'd love a few co-conspirators, or even some new friends for the bbs software or the bbs itself. A lofty nice-to-have goal is meeting a few other similarly motivated people to conspire with on a weekly basis. If that's you, drop me a line!
goals:
I have about half of an admin interface endpoint pushed up, which I'd like to finish. I realized mid-commit that I'd lacked some other material in a previous commit, and in pushing it up, I ended up pushing half the admin feature. Stay tuned for that.
I'd also like to implement a feature where I surrender the socket to a new process so I can upgrade the binary without dropping all of the connected users. I'm not sure on the feasibility of this, but all the words fit together, so it'll be tried.
The server could collect SSH public keys and use GitHub to resolve them to GitHub users to deanonymize users.
To protect yourself against this kind of problems:
1. Put this block at the end of ~/.ssh/config:
2. Use a separate private SSH key for each organization you connect to. You must create a config entry to tell OpenSSH to use it. Ex: Disclaimer: I'm the author of https://github.com/dolmen/github-keygen