![]() ![]() Since onion services are end-to-end encrypted anyway, there aren't many benefits to it either, especially once v3 onion services are supported and the onion service crypto is stronger.īut if you can explain the use-case more for options to encrypt the file I'd be into considering it again. So there are some big usability issues with adding a layer of encryption on shares. There are more than 25 alternatives to OnionShare for a variety of platforms, including Mac, Windows, Linux, Online / Web-based and Android. An attacker that is able to learn the OnionShare URL will also be able to download and decrypt the data. OnionShare is described as Web servers are started locally on your computer and made accessible to other people as Tor onion services and is a popular app in the file sharing category. But also, if you use symmetric encryption, you're going to have to communicate the passphrase somehow, and if you communicate the passphrase in the same way you communicate the OnionShare URL, then it kind of defeats the purpose. Symmetric encryption would be simple enough - it would just ask for a passphrase when you start sharing, but the receiver will need to also have the right software to decrypt this on their end, and at the moment the receiver only uses Tor Browser. First: symmetric or public key encryption? The main standard for public key encrypt is OpenPGP, and adding support for this into OnionShare would include a lot of extra code, including key management and stuff, and I'm not sure it makes sense since there are other tools specifically for doing this. I've also considered adding encryption, but this opens up a lot of questions. Im excited to announce that OnionShare 2.4 is now out and the major change in this version is that weve completely gotten rid of passwords Private OnionShare services are now protected using private keys (aka client authentication) on the Tor layer instead of instead of basic authentication on the HTTP layer. What would be the benefit of adding different types of archives? The reason OnionShare uses zip for archives is because there's unzipping software built-in and pre-installed in Windows, macOS, and major Linux distros. #663, when implemented, will simple not zip up the file if you're sending a single file, but will zip up multiple files still. If you're sending multiple files, they need to somehow bundled into a single download. ![]() It's only feasible to not have an archive at all when you're sending a single file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |