491
you are viewing a single comment's thread
view the rest of the comments
[-] r00ty@kbin.life 3 points 4 months ago

What if I told you, businesses routinely do this to their own machines in order to make a deliberate MitM attack to log what their employees do?

In this case, it'd be a really targetted attack to break into their locally hosted server, to steal the CA key, and also install a forced VPN/reroute in order to service up MitM attacks or similar. And to what end? Maybe if you're a billionaire, I'd suggest not doing this. Otherwise, I'd wonder why you'd (as in the average user) be the target of someone that would need to spend a lot of time and money doing the reconnaissance needed to break in to do anything bad.

[-] Findmysec@infosec.pub 2 points 4 months ago* (last edited 4 months ago)

Ah, you mean they put the cert in a transparent proxy which logs all traffic? Neat idea, I should try it at home

[-] r00ty@kbin.life 1 points 4 months ago

They (the service that provides both web protection and logging) installs their own root certificate. Then creates certs for sites on demand, and it will route web traffic through their own proxy, yes.

It's why I don't do anything personal at all on the work laptop. I know they have logs of everything everyone does.

[-] BestBouclettes@jlai.lu 1 points 4 months ago

I'm talking about home hosting and private keys. Not businesses with people whose full time job is to make sure everything runs fine.
I'm a nobody and I regularly have people/bots testing my router. I'm not monitoring my whole setup yet and if someone gets in I would probably not notice until it's too late.
So hosting my own CA is a hassle and a security risk I'm not willing to put work into.

[-] Findmysec@infosec.pub 1 points 4 months ago

Yeah that's your situation. Some people are fine with it

this post was submitted on 08 Aug 2024
491 points (100.0% liked)

Selfhosted

40767 readers
1524 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS