tor-onions December 2018

tor-onions@lists.torproject.org

3 participants
4 discussions

Onion v2 HSDir Support (ref: v3 prop224) [was: fishy fingerprint patterns]
by grarpamp 26 Dec '18

26 Dec '18

> relays have a rather distinct signup and fingerprint pattern > usually seen for onion attacks. > ... > a) If you are an .onion operator I'd like to encourage you to switch to onion > services version 3 > ... > so we can start > ... > b) dropping onion version 2 services eventually. These are two separate things not necessarily tied together, thus split for clarity as above. The former a) is up to the onion operator based on their needs. If they have no need for v2, or need v3, they can or should switch to v3, indeed. The latter b) is a feature that some users and operators in and for onionspace explicitly choose and depend on to support common apps, and thus would definitely not like to see yanked out from under them. Better instead to advertise and update the default onion semantics for [new] users to v3, and continue support and backport doable features to v2 until time below... Node operators (tor-relays) would continue offering v2 HSDir support module until such time as the reasons for choosing v2 by those above are supported in v3 or vN. See the threads on this subject on tor-talk, tor-onions, and tickets for more. [CC for inclusion, move there if not relay specific]

1 0

ramdisk based onions sites
by J. S. Evans 19 Dec '18

19 Dec '18

Would there a be a significant security/privacy advantage to running a .onion site in a VM that lives entirely on a ramdisk? The downside obviously would be that anything not backed up would be lost in the case of a reboot. To me the upside is that it would be very difficult to see anything that had been running in the VM if it needs to be dumped in the event of an emergency. I've heard of techniques that can get bits of data from ram that has been turned off, but I don't think that's easy/inexpensive to do. What do you think, group?

2 1

Torify WebDAV ?
by anan 17 Dec '18

17 Dec '18

Hi, I have an onion service with a Nextcloud server. I would like to access its files from a 32-bit computer. Nextcloud desktop client is torifyable, but it is 64-bit. Nextcloud does not privide a 32-bit desktop client. I tried torsocks nautilus so that I could access my files through "Connect to server" using WebDAV, but it says it cannot resolve hostname. Any suggestion on how to access my onioned Nextcloud files from my 32-bit GNU/Linux computer? Thank you!

1 1

Re: [tor-onions] [tor-talk] Tor official list of new .onion addresses?
by grarpamp 04 Dec '18

04 Dec '18

[Typo in onion list address, fixed and resent herein] > The descriptors seem to indicate onion addresses. So if I act a relay, I > seem to be able to get the addresses. Then how? ... Could someone > skilled try to get the lists? :D Yes, many services, researchers, and privates routinely do this. The code exists in some repositories, or you can write your own, it's not hard. Enumeration and listing in and of itself is not a problem, neither good nor bad on its face, a mere fact of the technology in use. It's up to the v2 users to decide if the tech works for them or not, fits their use case or not, and whether or not to use it, not use it, or use something else, or to seek or be provided education on the tech and tradeoffs. For many users, v2 vs v3 simply doesn't matter. For others, you may wish to blog or help them choose v2 vs v3. And in fact, v2 onion services are very useful when combined with OnionCat to yield IPv6 and UDP transport among tor's P2P onions. That's simply not possible with v3's no-IP TCP only onions. So for example, VoIP and other existing and new comms apps, mossh, and Bittorrent freespeech and robust uncensorable distribution channels, are enabled and exist entirely within tor's v2 onion space, somewhat similar to I2P. Search the list and tickets for "onioncat" for other use cases. Just because some poor souls footshoot themselves... which they'll still obviously somehow mangage to do with any tech regardless... isn't sufficient reason to cease support, maintenance, development, backporting, and furtherance of an agnostic technology such as v2 onions. > with OnionCat to yield IPv6 and UDP transport among tor's P2P > That's simply not possible with v3's no-IP TCP only onions. That is to say, it's not possible with code that exists today... the various possible solutions, and others yet to be proposed, that could provide those things with v3 onions, haven't been developed and put into working code yet. As such, it would be an interesting project for anyone or group that wants to do it.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

tor-onions December 2018