Download files using YMODEM using your web browser and the HTML5 applet.
Download files using ZMODEM with a compatible client like SyncTERM.
Compatible over Telnet and SSH connections.
Have your file sent to my secure server to download using a standard browser.
Telnet is similar to the client-server arrangement that was common with the dial-up modem-based BBS system. Telnet is text-based and allows the end user to directly interface with the BBS using their Telnet client. Most modern Telnet clients also support ANSI color schemes. Telnet is an unencrypted plain-text protocol that can be used to connect to Archaic Binary BBS. It’s the best supported connection method but is not secure by any means.
Secure Shell (SSH) is a cryptographic network protocol for operating network services securely over an unsecured network. The best known example application is for remote login to computer systems by users.
SSH was designed as a replacement for Telnet and for unsecured remote shell protocols such as the Berkeley rlogin, rsh, and rexec protocols. Those protocols send information, notably passwords, in plaintext, rendering them susceptible to interception and disclosure using packet analysis. The encryption used by SSH is intended to provide confidentiality and integrity of data over an unsecured network, such as the Internet.
I highly recommend using SyncTERM and SSH to connect to Archaic Binary BBS. I use it to test everything on the BBS.
When you setup SyncTERM and add Archaic Binary into your address book, choose the SSH protocol and then change the following options for the best experience. SSH Username can be anything for now just use “archaic” and then for SSH Password it can be anything as well, use “binary” for now. Then I highly recommend you choose to hide the status bar as it might mess with the amount of rows the BBS expects.
WS = WebSockets
WSS = WebSockets Secured (SSL)
WebSocket is a computer communications protocol, providing full-duplex communication channels over a single TCP connection. The WebSocket protocol was standardized by the IETF as RFC 6455 in 2011, and the WebSocket API in Web IDL is being standardized by the W3C.
WebSocket is designed to be implemented in web browsers and web servers, but it can be used by any client or server application. The WebSocket Protocol is an independent TCP-based protocol. Its only relationship to HTTP is that its handshake is interpreted by HTTP servers as an Upgrade request. The WebSocket protocol enables interaction between a browser and a web server with lower overheads, facilitating real-time data transfer from and to the server. This is made possible by providing a standardized way for the server to send content to the browser without being solicited by the client, and allowing for messages to be passed back and forth while keeping the connection open. In this way, a two-way (bi-directional) ongoing conversation can take place between a browser and the server. The communications are done over TCP.
The WebSocket protocol is currently supported in most major browsers including Google Chrome, Microsoft Edge, Internet Explorer, Firefox, Safari and Opera. WebSocket also requires web applications on the server to support it.
If you do not or cannot load a telnet client like SyncTERM or mTelnet on your system to access Archaic Binary you can also get to the BBS using the website. Please note that using the official website (https://www.archaicbinary.net) to access the BBS will give you an encrypted connection. Accessing Archaic Binary using a 3rd party website or relay system will provide you with an un-encrypted connection.
Most commonly used WS (un-encrypted) sessions will come over from the fTelnet Relay system. This is a great piece of software and allows more people to access BBSes and might give unaware users access to the BBS it should be known that the traffic is not encrypted and does possibly flow through 3rd party people other then your ISP (and any ISPs between you and I).
Tor is free software for enabling anonymous communication. The name is derived from an acronym for the original software project name “The Onion Router”. Tor directs Internet traffic through a free, worldwide, volunteer network consisting of more than seven thousand relays to conceal a user’s location and usage from anyone conducting network surveillance or traffic analysis. Using Tor makes it more difficult for Internet activity to be traced back to the user: this includes “visits to Web sites, online posts, instant messages, and other communication forms”. Tor’s use is intended to protect the personal privacy of users, as well as their freedom and ability to conduct confidential communication by keeping their Internet activities from being monitored.
Onion routing is implemented by encryption in the application layer of a communication protocol stack, nested like the layers of an onion. Tor encrypts the data, including the next node destination IP address, multiple times and sends it through a virtual circuit comprising successive, randomly selected Tor relays. Each relay decrypts a layer of encryption to reveal only the next relay in the circuit in order to pass the remaining encrypted data on to it. The final relay decrypts the innermost layer of encryption and sends the original data to its destination without revealing, or even knowing, the source IP address. Because the routing of the communication is partly concealed at every hop in the Tor circuit, this method eliminates any single point at which the communicating peers can be determined through network surveillance that relies upon knowing its source and destination.
TOR connectivity is available for Archaic Binary BBS users. It just consists of the WebSockets browser canvas (applet) and communicates over the Onion Network. Our TOR address is: http://nrzinzk43rx5v4mg.onion. Note that you will probably get a drop down saying the site is using a canvas and it’s a possible security issue. HTML5 uses a canvas to do the connection, and it cannot be helped.