This profile is from a federated server and may be incomplete. View on remote instance

Fal , to KDE in question about gitlab merge request (invent.kde.org)
@Fal@yiffit.net avatar

Your first way was the right way, rebasing

Fal , to Sysadmin in You have a organizational identity right?
@Fal@yiffit.net avatar

Oh. I’m absolutely including a private CA as part of self signed cert. That’s probably my misuse of the term

Fal , to Sysadmin in You have a organizational identity right?
@Fal@yiffit.net avatar

you are unable to protect against MitM and other forgery attacks

Uhh, using a self signed cert doesn’t mean you just accept any old cert… Not every cert is designed for serving content to a browser. You do SSL mutual auth between services using self signed certs

Fal , to Sysadmin in You have a organizational identity right?
@Fal@yiffit.net avatar

Basically with self signed certs, you control the ENTIRE trust chain. When you use existing CAs, any bad actor in any of those CAs can generate certs that you would end up trusting. So it’s less secure because you have to trust a lot more people.

Fal , to Sysadmin in You have a organizational identity right?
@Fal@yiffit.net avatar

but they fix a lot more problems than they cause

I didn’t say anything that disagrees with this. CAs are nice and convenient. They do this by expanding the chain of trust to a lot more people, hence making them less secure.

Sure if you can’t securely manage your cert, that’s a problem. But that doesn’t mean let’s less secure

Fal , to Sysadmin in You have a organizational identity right?
@Fal@yiffit.net avatar

They’re more secure than CA certs

Fal , to Sysadmin in You have a organizational identity right?
@Fal@yiffit.net avatar

Self signed certs are more secure. You don’t have to trust the whole CA chain

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • All magazines