Repository navigation
·
1 commit
to main
since this release
Info: https://github.com/EmptyCode0x86/OffCode-Tor-Chat-E2EE
https://www.dev-offcode.com/TorChatPage.html
VER: 0.1.3
- 19/10/2026
Changes
New: Feed
-
Public Feed: A new, optional Feed tab where people can write short text posts, comment and like. The server owner turns it on in Server Manager (Enable feed). It is off by default. -
Feed is public: Anyone who has the .onion address can read the Feed. Posts are not end-to-end encrypted like chat messages, so don't post secrets. They are still stored encrypted on the server's disk. -
Who can post: Reading needs nothing. To post, comment or like you need a recovery code. It works like an anonymous ID: no account, email or personal data. You can delete your own posts with it. -
Generate code without a room: New visitors can now create a recovery code straight from Profile. You no longer have to create a room first. -
Moderation: The server owner can remove any post from Server Manager (Remove selected post). -
Clean text only: Emojis and hidden or invisible characters are not allowed, which stops tricks that hide or flip text. -
Terms updated: The Terms of Service now say the Feed is public and moderated by the server owner. Server Manager asks you to accept them again on next start.
Security
-
Stricter page security: The chat page now tells the browser exactly what it may load and run, and blocks everything else. This makes it much harder for injected code (XSS) to run. Some of these protections work only in Chromium-based browsers. Tor Browser ignores them, which is expected. -
Extra privacy headers: Pages and server responses are no longer cached, aren't indexed by search engines, and don't trigger extra DNS lookups. -
Codes stay in this tab by default: Recovery codes and room management codes are now forgotten when you close the tab. Turn on Remember on this device in Profile if you want to keep them. Older saved codes are moved safely and you get a notice about it. -
Safer file names: Downloaded file names can no longer use hidden characters to disguise the real file type (for example a fake ".jpg" that is really a program). -
Connection checks: The server only accepts live connections from its own address. If that check blocks something, the chat still works over a slightly slower fallback connection. -
Replay protection: The app now detects and ignores messages that someone records and sends again later, or that carry a fake time. If many are ignored, you see one short summary line instead of a flood of notices. -
Encryption keys kept out of reach: Raw room keys are no longer left in the app's memory where other code could read them, and they are wiped after use. -
Encryption update (protocol v3): Encryption is tied more tightly to each room, sender and message time, and file encryption got the same upgrade. Note: this version is not compatible with older ones. Old rooms and messages are wiped on the first start, and everyone needs the update. -
Matching safety numbers: When someone leaves and rejoins, both people now see the same new safety number, plus a reminder to compare it again. -
Cleaner images: Hidden data such as location and leftover cropped image data is removed from shared images more reliably. -
Honest limits: In open rooms and in password rooms with three or more people, the app can't prove which member sent a message. Treat these rooms with that in mind. -
Startup check screen: Redesigned. The chat only opens on your own computer or a real .onion address, in a browser that supports secure encryption. If it stays blocked in Tor Browser, set the Security Level to Standard or Safer and reload. -
Checked key exchange: Keys received from the other person are checked before use, and broken or fake keys are rejected. -
Strict message format: Each message is bound to its room, its sender and its send time. Messages in unknown or old formats are rejected instead of guessed at. -
Password handling: Room passwords are converted to one standard form, so the same password typed on different devices works the same way. -
Safer file transfer: Files are split into encrypted pieces with fixed size limits (maximum 32 MiB per file). Each piece is checked, and damaged or extra pieces are rejected.
Server Manager
-
Vanguards data in a safe place: Vanguards (extra Tor protection) now keeps its data in your AppData folder. It survives updates and is never included in release packages. -
Generate new address: Works only when Tor and Vanguards are stopped, and the dialog tells you what to stop. Old address keys and Tor's saved state are then securely overwritten. -
Smoother Vanguards start and stop: Vanguards starts as soon as Tor is ready and stops in the right order when Tor is turned off. -
Less log noise: Guests no longer trigger pointless invite errors, and the remaining errors are shown on a single line. -
Reset guard data: New button on the Connection tab. Use it only when Tor and Vanguards are both stopped. It clears Tor's saved entry-point data (a backup is kept too). Tick the box to also clear Vanguards' data. Your .onion address and keys stay the same. If connections keep failing, Server Manager offers this reset once per hour. -
Cancel a stuck Tor start: Turning Tor off, pressing Stop or closing the window while Tor is starting cancels it cleanly. If Tor has not finished starting after 5 minutes, it is cancelled automatically and shows as Stopped. Stop also works while the chat server is starting. -
No leftover background programs: If Server Manager closes unexpectedly, the Tor, Vanguards and chat server processes it started are shut down. Any left over are cleaned up on the next start. Other programs, including Tor Browser, are never touched. -
Clear port warning: If the Tor control port or chat port is already used by another program, Server Manager shows that program's name and process ID before starting anything. -
Tidier Tor log: Shows when your .onion address is published to the Tor network. Routine connection messages are hidden, and a guard failure is reported only once per run. -
New window look: Named "TorChat Server Manager" with the onion icon. Minimum window size is 900 x 600. Settings on the Connection tab are collapsed under an expandable section. -
Windows app: The Windows release is a single "TorChat Server Manager.exe" file. Its settings and data are kept in %AppData%\TorChat_ServerManager_MP. -
Confirmation boxes: Popups wait for your answer without freezing the window. For example, Remove selected post no longer hangs the app. -
Error log: Unexpected errors are saved to crash.log in the data folder. It never contains admin keys, encryption keys or message text. -
Vanguards included: The Windows release comes with its own Python, so you don't need to install Python to use the Vanguards option. -
Safe releases: Release builds are checked so private files (keys, admin data, local settings) are never included.
Platforms
-
macOS: Tor Chat now works on macOS. -
Linux (Ubuntu Desktop): Tor Chat now works on Ubuntu Desktop. -
Ubuntu Server: Not supported yet. Support for Linux / Ubuntu Server is in progress and will be added later.