#Mumble certificate expired mac os x
#Mumble certificate expired code

Sometimes, if you're lucky, you can use the same username on more than one site. You have a different username on every site you visit. I'm sure I'm the only Radia Perlman on Earth. I was thinking, really, what do you think the identity problem is? What do you think blockchain is, whatever? I'll talk about that. What does a browser need to know in order to authenticate a website? Will blockchain solve the identity problem? Because I've heard that's what inspired this talk, really, was someone was saying, just use blockchain and you'll solve the identity problem. There's a lot of dimensions to it, like, what is your name? How do you prove you own that name? How do I know your name? How do you make human authentication convenient? If you talk about, I'm working in the identity space, they think they know what it means. Most people think they know what it means. This talk will explain all the various pieces, or a lot of them, and the various challenges with them. It's like, there are so many pieces of it. I hate buzzwords, because people think that they're conveying information when they say I do identity. That way you can easily export it, import new certificates, etc.Perlman: I'm going to talk about identity, which is a buzzword. If you want to get at your certificate, you're strongly recommended to use the tools available in the certificate wizard (and not fiddle with the settings plist file).

#Mumble certificate expired code

I'm currently working on implementing identity management in our iOS client, so it's possible that some of that code can be reused in the desktop client to accelerate the keychain integration. There's an open feature request on the subject, if you want to add anything to it.

#Mumble certificate expired mac os x

There is also the possibility to use an email certificate (or other personal certificate) from a trusted certificate authority.Ĭurrently, on all platforms, the certificates + private keys are stored in the settings file (on Mac OS X this is a plist in ~/Library/Preferences/.plist), and unfortunately *not* in the keychain (yet!).

So that's the one you really want to back up somewhere, but keep it for yourself and secure.Ī self-signed client certificate can be generated by yourself through the certificate wizard (Configure -> Certificate Wizard), or Mumble can automatically generate a generic one for you (name: 'Mumble User'). The private key is only for yourself which is used on encode, encrypt etc things, and to create the public key again.

The public key is the one you identify with to others, so the one that is sent to the mumble server to identify yourself (and other users who may add you as a friend etc). You created one for mumble, probably on first launch in the wizard.Īs described there, the certificate has 2 keys. The other thing is the client certificate. Thus you are sure, if you are sending login-credentials for example, to that server it's not being sent to a fake or new one, one you didn't say you trust when accepting the cert. That way you are sure you are connecting to that one server through that address (after all an address/ip/domain may point to a different server in the future, when the old provider died and the ip is reassigned or sth, or someone wants to fake it.). (%APPDATA%/Mumble/mumble.sqlite or sth)Įvery time you reconnect to the server your client (mumble) checks that the server you are connecting to still provides the same certificate. The certificate is then saved in your mumble clients sqlite database. Then the server tells you, this is me with this certificate, and you accept it. The server certificates are used for the secure SSL (as in HTTPS) connection to the server, where the server identifies itself with just that certificate. Mumble uses 2 kinds of certificates: Server-certificates and client-certificates.