In the same way a self-signed certificate doesn't need to be signed by an official root of trust to be useful for authentication, a self-signed Personal CA doesn't need to be signed or cross-signed by another CA to be trusted by a server.
Assume you created a self-signed personal certificate and you use that to sign your emails.
What if I make a self-signed cert claiming to be you, and create an email address nmelo@gmail.com.
How would someone know which one to trust if there wasn't a third party to verify youre the real nmelo? Websites do this with trusted CA roots on their browsers.
Going back further, business do it with services like Dun & Bradstreet.
But personal?
What am I missing?
Now extend that to a personal certificate authority. As long as the server is able to trust that the Root Certificate, and any Intermediates certs in that CA are controlled by the user, they should be able to trust certificates signed by that CA to authenticate that person.
> the fact that a person controls the private key associated with the certificate should be enough
Going back to my example, of you and I both claiming to be the same person with our certificates, us both having a private key doesn't solve this problem. Who authenticates who is the real person? Or is that not the point of certificates?
> if they have enough confidence that the private key is being securely stored by the user
Or... is it that a self-signed cert just proves who owns the private key, and I'm putting to much into what a cert is supposed to be?
> and any Intermediates certs in that CA are controlled by the user,
ah, ok, so I can act as my own CA because I have the private key for the root of trust.