Secbrowser is deprecated so this line should be deleted:
kicksecure-xfce: Same as kicksecure-cli but installs the XFCE graphical desktop environment and default applications such as SecBrowser ™ (A Security-hardened, Non-anonymous Browser).
I saw as well this place in the forum:
So which you see my post fits to go as a comment under you can shift my post to.
Whonix ™ is produced independently of, with no guarantee from, The Tor® Project.
“with no guarantee from” seems superfluous. Logically, if Whonix is produced independently, then The Tor Project would never provide any kind of guarantee.
For simplicity, why not change it to:
Whonix ™ is produced independently of The Tor® Project.
(The logo on that page also reminds me that no update/notice was given regarding contributors who provided possible new logos. Some kind of news announcement should be provided about that issue because it closed in January or thereabouts i.e. if not going to update the logo, why not etc.)
Whonix ™ is produced independently of, with no guarantee from, The Tor® Project.
“with no guarantee from” seems superfluous. Logically, if Whonix is produced independently, then The Tor Project would never provide any kind of guarantee.
For simplicity, why not change it to:
Whonix ™ is produced independently of The Tor® Project.
That text is a courtesy to TPO. Using exactly as requested.
The Tor Project encourages developers to use the name Tor in ways that
do not confuse the public about the source of anonymity software and
services. If you are building open-source non-commercial software or
services that incorporate or work with The Tor Project’s code, you may
use the name “Tor” in an accurate description of your work. We ask you
to include a link to the official Tor website https://www.torproject.org/ so users can verify the original source of
Tor for themselves, and a note indicating that your project is not
sponsored by The Tor Project. For example, “This product is produced
independently from the Tor® anonymity software and carries no guarantee
from The Tor Project about quality, suitability or anything else.”
(The logo on that page also reminds me that no update/notice was given regarding contributors who provided possible new logos. Some kind of news announcement should be provided about that issue because it closed in January or thereabouts i.e. if not going to update the logo, why not etc.)
Technically the term memory is correct and should be clear in the context it is being used there. However, if it’s confusing and someone has a suggestion to improve it feel free.
However we cannot write “the amount of harddisk you would like to add”. That seems wrong.
Nothing just read it again now i dunno why my brain saw it as secbrowser not secure browsers. (maybe my brain saw sec then eye jumped to the kicksecure then showed the best reading is secbrowser thus i posted that post…)
Download the Whonix ™ Signing Key for VirtualBox, Source Code and APT Repository worthwhile having full output of gpg --keyid-format long --import --import-options show-only --with-fingerprint patrick.asc? I don’t think it’s useful having users ask about minor changes such as new uids (e-mail addresses) or newer expiration dates. One thing more to keep updated in the wiki, which if forgotten, generates support requests.
I’ve noticed some documentation which I believe to be misleading and would like to report it here. It is not particularly significant but all errors in documentation are frustrating to those trying to better understand the software.
/wiki/Tunnels/Connecting_to_a_VPN_before_Tor
Under section “Separate VPN-Gateway” bullet point 3:
When a failed closed configuration is used and the VPN connection breaks down, all traffic originating from Whonix-Gateway ™ (commonly called sys-whonix) would only be forced through Tor. This is what you want if you are reading this documentation chapter. User → Tor → Internet
I believe this is misleading as a fail-closed mechanism prevents any traffic from exiting via the VPN-gateway in the case that the VPN connection is dropped. What is actually being described in the documentation is a fail-open mechanism. For somebody reading the documentation that has the strict requirement that Tor traffic never exit their system without being tunneled through VPN, this could falsely make them believe that this configuration is not for them.
Sorry if I have not reported this correctly. I would also like to know if I’ve got something wrong, but I do not believe that is the case.
`