Subj : Re: BBSing on the TOR Darknet To : The Godfather From : paulie420 Date : Mon Jun 12 2023 22:12:39 TG> Ah sweet, very nice, installing torsocks now and will test it out when I TG> finally have time tomorrow night. What all is/was involved in getting20 TG> setup with a darknet address? Not super hard; and all the info was from MeaTLoTioN, as always - lol, ... I think I have a .txt file around here somewhere: ----- TQW now has a tor address: tfrsgnjhf4lywcl34qrcwiqvybuq46lhs5pltzkwlsghziumcsbfeoyd.onion you can use this for both telnet and ssh on the usual ports =) if you run linux, and don't yet have any idea how to use tor to connect, quickand dirty guide is as follows: sudo apt update && sudo apt install tor torsocks telnet tfrsgnjhf4lywcl34qrcwiqvybuq46lhs5pltzkwlsghziumcsbfeoyd.onion if you wanna use syncterm, you can use torsocks syncterm which will load syncterm and send all traffic through your new tor proxy Note: none of your non tor addresses will work while using the tor proxy(obviously) so just make a new address entry for the tor version and just use that Note2: bear in mind, due to the way TOR works, expect the connection to be slower than you normally experience. Have fun, and catch y'all in tgt if not before. -----on the bbs host machine, I just installed the tor app via sudo apt install tor then edited the /etc/tor/torrc file expose the ports for the bbs I want, i.e.telnet and ssh, then restart the tor service sudo service tor stop && sudo service tor start (restart didn't seem to reload the config (nice one systemd:P)) your onion address is found in /var/lib/tor/other_hidden_service/hostname file in the torrc file, look for HiddenServicePort section, then just uncomment/addlines like this; HiddenServicePort 23 127.0.0.1:23 127.0.0.1 is the localhost address, which is where the tor proxy is, so it wouldn't log anything other than that, and to be honest, would probably be better not to log a nice touch I figured out though, is you could expose say port 23, but have it use 127.0.0.1:2323 as the actual port it exposes, so you could add another telnet server in mystic just for tor, and anyone using that it would show up as the tor telnet service in the logs ---setting a new mystic ssh/telnet to log TOR connections: -----so I expose 23 and 45022 over tor, and they redirect locally to 2323 (telnet) and 2222 (ssh) I have bound those ports in the mis cfg to 127.0.0.1 only also, just so no one else can use them from other locations and in my torrc file HiddenServicePort 23 127.0.0.1:2323 HiddenServicePort 45022 127.0.0.1:2222 I also added 127.* to the /mystic/data/allowlist.txt file so that it doesn't ban 127.0.0.0 ----- Easy peasy. |07p|15AULIE|1142|07o |08......... --- Mystic BBS v1.12 A48 (Linux/64) * Origin: 2o fOr beeRS bbS >> 20ForBeers.com:1337 (700:100/71) .