• 11 Posts
  • 91 Comments
Joined 6 months ago
cake
Cake day: September 9th, 2024

help-circle




  • I would like an already hardened environment from boot. That includes the kernel hardening and browser hardening that Tor has.

    I get what you’re saying, a live USB does 80% of that with a bit more work, but I would still like to find a solution to this out there.

    If there isn’t one, I’m ready to accept that and come up with my own solution.


  • Do you need it to be amnesiac? The very thing that defines Tails*.

    Yes. A persistent storage feature would be nice but isn’t a requirement.

    What’s wrong with Tor? Is your threat model so paranoid that you (somehow) don’t even trust Tor? Or, are you not in favor of its (relatively) low bandwidth? Or, is privacy and/or security not even a thing you seek after to begin with? Or, at least not beyond what your average distro provides already*.

    The reason I don’t want to use Tor is because I will only connect to plain web websites where I don’t care if they know my IP. I also find that CloudFlare and other services can block Tor which sometimes causes issues with my work.

    What do you intend to do with it? Daily drive it? If so, do you need persistence?

    I mainly plan on isolating certain browser-based work I’m doing with other work on my computer. As I said before, persistence would be nice but is not necessary.

    What does “Tails without Tor reliance” provide/offer you beyond a LiveUSB from any other distro? Or, rather, what do you hope it will provide/offer you?

    I hope it would offer me a highly hardened environment to do work in, without the requirement to set it up every time on other liveusb OSes.

    To put this all together, I want an amnesiac live USB hardened(browser, kernel) environment that does not use Tor.

















  • yes, the host is 192.168.86.73 and it has that dnat rule.

    And from the guest

    Assuming you meant from the host, I am sshing directly to 192.168.101.4 instead of to 192.168.86.73:2222.

    The third paragraph doesn’t make sense to me. I am using port 22 on my host(192.168.86.73) for it’s own ssh.

    tcpdump returns this when I ssh to port 2222:

    20:32:29.957942 IP (tos 0x10, ttl 64, id 28091, offset 0, flags [DF], proto TCP (6), length 60)
        192.168.86.23.53434 > 192.168.86.73.2222: Flags [S], cksum 0x5d75 (correct), seq 1900319834, win 64240, options [mss 1460,sackOK,TS val 3627223725 ecr 0,nop,wscale 7], length 0