This commit removes the WWW: lines of moved-over URLs from these Remove WWW entries moved into port MakefilesĬommit b7f05445c00f has added WWW entries to port Makefiles based on accessibility/at-spi2-core: bump consumers of removed ports atk and at-spi2-atk accessibility/atk and accessibility/at-spi2-atk have been merged into To be registered only for a given application (!52). * Add atspi_event_listener_register_with_app, to allow an event listener * Add a text value to AtspiValue, so that a value can expose a textualĭescription, as in the new Atk value API. ![]() * Properly escape the AT-SPI bus address fixes warnings about the address * at-spi2-atk: Expose the accessible hierarchy via dbus introspection. * Now requires meson 0.56.2 and glib 2.67.4. * Atk and at-spi2-atk are now merged into this project. * Various code clean-ups and test improvements. * Add an "announcement" event/signal to allow objects to send * Mark bus service as belonging to the session slice. * Bind the AT-SPI bus to the graphical session. * xml: Add some missing DeviceEventController methods. * Document the Accessible, Action, and Cache dbus interfaces. * Send device event controller events using the same signature as other Once the persistence feature is released in Tor stable (expected in December), we can remove the logic that ignores-or-hides persistence mode.Accessibility/at-spi2-core: update to 2.46.0 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 You may also subscribe to our mailing list here, and join our public Keybase team here. You can set up your development environment to build OnionShare yourself by following these instructions. Check this wiki page for more information. OnionShare may also be available in your Linux distribution's package manager. You can download OnionShare for Windows and macOS from the OnionShare website.įor macOS you can also use Homebrew: brew cask install onionshareįor Ubuntu-like Linux distributions, you can use this PPA: sudo add-apt-repository ppa:micahflee/ppa To learn how OnionShare works, what its security properties are, and how to use it, check out the wiki. So long as you share the unguessable web address in a secure way (like pasting it in an encrypted messaging app), no one but you and the person you're sharing with can access the files. Unlike services like email, Google Drive, DropBox, WeTransfer, or nearly any other way people typically send files to each other, when you use OnionShare you don't give any companies access to the files that you're sharing. It doesn't require setting up a separate server, using a third party file-sharing service, or even logging into an account. ![]() It works by starting a web server directly on your computer and making it accessible as an unguessable Tor web address that others can load in Tor Browser to download files from you, or upload files to you. OnionShare is an open source tool for securely and anonymously sending and receiving files using Tor onion services.
0 Comments
Leave a Reply. |