I'm at the Tor meeting now so I'll talk to people about this while I'm here. I think it might be a good idea to include OnionShare in Tor Project's account because they already have a dedicated army of translators that would be excellent to use as a resource. Transifex is a centralized localization platform, and Tor Project uses it to localize Tor Browser, Tails, and other similar software. I'd rather not run our own servers of course. and I know SecureDrop just set up their own server. We can then import the translations into OnionShare as a step in the release process. I think we should use a web-based localization framework such as Weblate or Transifex, so we can upload English-language locales and have people translate them into other languages, and others review their translations. Once the persistence feature is released in Tor stable (expected in December), we can remove the logic that ignores-or-hides persistence mode. The v3 onion works for both share and receiver mode. This is necessary to interact with Stem with v3 keys, but even more significantly, it paves the way for saving that v3 private key to json once persistence is possible, and it paves the way for a 'dead man's switch' feature (reverse shutdown-timer: a start-up timer that allows the user to communicate a future onionshare URL yet to be published), which I will send a PR for later down the track. Note the onionkey.py, which pre-generates private keys for both v3 and v2 now. Otherwise it contains the logic from my previous prop224 branch. json file, or command line flags), they are silently ignored (resulting in a non-persistent onion with no stealth) debs.ĭeliberately hides the 'persistent URL' and 'stealth' features in the settings dialog (since we know those don't work properly with v3 onions)Įven if somehow persistent or stealth mode is enabled (think: previously-saved. Not sure how that will fly for Debian/Ubuntu. Or, more generally, introduces that dependency. However, there's no deb or rpm for it, so it introduces the need to pip install at least one package on those platforms (for the first time) if building/testing from source. Requires the (testing) user to pip install pysha3 if they don't have it already (I encountered an issue on Debian 9 whereby, if the version of Python is too low, the logic that uses hashlib doesn't quite work ( hashlib.sha3_256), but pysha3 does. I'm deliberately basing this on the receiver-mode-gui branch because it has so many other breaking changes that it's not worth branching off of develop branch anymore.įavours v3 onions if the Tor version is new enough
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |