Hmm.. ZeroNet various websites always results in this error: “Content.JSON Download Failed”. JS allowed on 127.0.0.1 and can see a number of peers so not sure what the problem is. Maybe like I2P you have to let it run for a long time beforehand?
Logs also show for various website attempts: “ContentDb not initialized, load files from filesystem…”
Have you succeeded in Qubes-Whonix @Patrick. Does about:config need some more tweaking perhaps? The home page works okay.
PS @madaidan Don’t waste all your talents & time on those reddit trolls. It’s like screaming into the void.
Spend more time over here doing your great development work!
Maybe like I2P you have to let it run for a long time beforehand?
Dunno. Conceivable.
Logs also show for various website attempts: “ContentDb not initialized, load files from filesystem…”
Have you succeeded in Qubes-Whonix @Patrick. Does about:config need some more tweaking perhaps? The home page works okay.
Last time I tested no such changes were required. I’ve tested very
little actual ZeroNet websites. Official links only. That worked for me
at that time.
Whonix on USB search term has very poor results on search engines. No wiki page is suggested Related information System Configuration and Access is really hard to find.
Because it shows that others managed to implement these features and it’s realistic to re-implement in Kicksecure - without adding any privacy issues or user freedom restrictions. It’s to tease and encourage other developers to catch up implementing some of the iPhone/Android security features in Linux (desktop) distributions too. If it gets added to Kicksecure that’s great, but if others focus on other Open Source Linux distributions that’s a net benefit too.
And if you’re wondering why it lists some disadvantages of iPhone/Android are listed, that’s to show in how many ways others are messing up. Tor create awareness of these issues (precondition for fix) and to not mess up in similar ways in future. Illustrating project goals, values, awareness.
Concept of Open/Free/Libre Software is great. However, since the inception of the 4 original essential software freedoms, other issues came up sometimes called tivoization, malicious feature, antifeature, tyrant software, treacherous computing or DRM (digital restrictions management). Also data portability, open databases, open source hardware, first mover effects, network effects, and more.
We have enough walls of texts. Some like tables, some don’t. In this case I found a table to be looking good.
A clear credit is given up front to the author: “The description of this procedure draws heavily upon the following guide: The Complete Guide to Secure Communications with the One Time Pad Cipher [archive]; all credits go to the author.”
A clear credit is given up front to the author: “The description of this procedure draws heavily upon the following guide: The Complete Guide to Secure Communications with the One Time Pad Cipher [archive]; all credits go to the author.”
To be on safe side, could you please make the authorship more explicit
by naming author and organization (or organization and author as
applicable)?
Most of it relies on Mixmaster (dead) or Nymservers (largely reliant on Mixmaster).
All that leaves is two sections re: reading newsgroups with NNTP clients (whatever that is, not familiar with it) and accessing NNTP servers anonymously for discussion groups (if that is even possible).
Overall, a lot cause - not worth editing to bring it up to scratch unless you have different views.
Mixmaster / remailer was actually for that context “just a bonus”.
Crossed out the mixmaster/remailer parts just now. Rest seems good enough.
It can be part of advanced documentation or even esoteric documentation as popularity of these things is low and declining.
I wasn’t sure Usenet discussion groups is nowadays completely dead, just full of spam bots which are forgotten be turned off, and just forgotten to be declared completely dead. Search results are dominated by commercial usenet providers (used for file sharing). But no, Usenet is still active. Found this list of some non-spam discussions: https://narkive.com (Usenet is not a website / web protocol. But there are a few gateways to preview contents of Usenet without having to use a news reader.) Usenet might also be interesting as an archive, research, history, whatnot as it had peak popularity in the 1990’s or so.
Could create a wiki template with an info (or warning) box which states that the content of that page is of a lower quality, and whatnot.
1. Our Qubes-Whonix documentation also has this problem:
Fix references to “ProxyVM” in docs
In 4.0, the term “ProxyVM” has been deprecated. (See here, linking to here.)
However, it is still used many times in the docs.
$ cd qubes-doc
$ grep -ir ProxyVM . | wc -l
49
The docs should be revised to reflect the more flexible architecture: instead of a whole category of vms (a qube is a ProxyVM), the new property describes an action a qube might do (provide networking).
I think we’ll want to take each instance on a case-by-case basis. In some of these cases, we might want to allow the term “proxy VM” (or something similar) to refer colloquially to the notion of a VM which provides network service to another (that is, a VM with property provides network).
2. As per @nurmagoz recommendation, I gather you’d agree the FTP page should instead focus on SFTP i.e. secure file transfer via SSH.
Looks safer (less port/firewall opening etc.), later protocol, less installation and so on.
SFTP (SSH File Transfer Protocol) is a secure file transfer protocol. It runs over the SSH protocol. It supports the full security and authentication functionality of SSH.
SFTP has pretty much replaced legacy FTP as a file transfer protocol, and is quickly replacing FTP/S. It provides all the functionality offered by these protocols, but more securely and more reliably, with easier configuration. There is basically no reason to use the legacy protocols any more.
SFTP also protects against password sniffing and man-in-the-middle attacks. It protects the integrity of the data using encryption and cryptographic hash functions, and autenticates both the server and the user.
That would be interesting to have. But since no users showed interest in this subject and since not very or not at all specific to Whonix, I don’t think I’ll document it. Contributions welcome. Among the fascinating stuff: rsync / ssh / sshfs / sftp over clearnet / over Tor / over onion
Plaintext FTP is still slightly interesting. Original reason for documenting plaintext FTP was some user asking about it years ago. Some public servers used to allow only download over plain FTP. Dunno if there are still any. Very unpopular subject. I don’t recall anyone asking about FTP for years. Therefore this can be burried in advanced or even esoteric documentation. I don’t really want to delete it entirely because if someone asks for it in a year I won’t recall it and not find it in any archive either. Hope that’s reasonable.
“Operation not permitted” re: Step 2 when using apt-key command
Openjdk-7-jre-headless is in stretch, v8 is in Sid (wants to remove essential Whonix packages if you try to install it), v11 is in Buster and works (see: Debian -- Error)
Basically, unsafe install instructions work i.e. substituting openjdk-11-jre-headless:
Then making the Tor Browser about:config changes noted on that wiki page. Unsafe working instructions are better than non-functional ones, right?
But this begs the question as to why bother running a server on port 8090 when you can just use the decentralized search function straight via a portal anyhow i.e. here? →
Main ToC should be working instructions that are useful, not pipedreams that might be ready a decade later (since GNUnet has been in development for two decades plus already)
So we should probably shift it to the Advanced Documentation page. If you agree, I’ll move it there.
3. For all the wiki pages on the main Documentation page that don’t have a thumbnail right now (logo etc.), how about I add the associated Libre page image as a thumbnail for each (top right-hand side), so they look “pretty” instead of just starting off with ugly, plain text.
4. The language page system section (not Tor Browser) seems focused on KDE? Outdated, non-functional?
