https://safecomms.virebent.art/
This application is to be used in the browser in one tab, in the other tab a chat application.
With your interlocutor starts a session, exchange your session-id, which is not a public key but serves to synchronize your sessions so that you are decryptable.
Encrypt the message in the tab with nofuture and send it via the chat application in the other tab.
The keys are generated on our server, they are protected by local access (even root) and remote through memguard.
At the end of the session, everything is deleted forever.
At this url there is a readme in Italian and English https://safecomms.virebent.art/leggimi.html
Gabx
Sent by https://yamnweb.virebent.art/
yamn+tor web interface
In article <20250529.071534.c067196e@dirge.harmsk.com>
Gabx <Use-Author-Supplied-Address-Header@[127.1]> wrote:
https://safecomms.virebent.art/
This application is to be used in the browser in one tab, in the other tab a chat application.
With your interlocutor starts a session, exchange your session-id, which is not a public key but serves to synchronize your sessions so that you are decryptable.
Encrypt the message in the tab with nofuture and send it via the chat application in the other tab.
The keys are generated on our server, they are protected by local access (even root) and remote through memguard.
At the end of the session, everything is deleted forever.
At this url there is a readme in Italian and English https://safecomms.virebent.art/leggimi.html
Gabx
Sent by https://yamnweb.virebent.art/
yamn+tor web interface
Great, but why does it require the To: field if I'm sending to a
newsgroup?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 491 |
Nodes: | 16 (2 / 14) |
Uptime: | 142:49:01 |
Calls: | 9,694 |
Calls today: | 4 |
Files: | 13,728 |
Messages: | 6,178,353 |