You'll most likely (as long as Java is working correctly for you) get a certificate warning the next time you update your client. This is because I decided to create a new code certificate, so as long as the fingerprint checks out, you don't need to worry about it being cr4xx0red [though I'm guessing most people just click OK past it anyway ;)].
The reason I'm updating the certificate, in case anyone is wonder, is because I found that I have the private key for the current certificate in the Git repository for the client, which would be kind of bad if we decide to release the source code for the client (which is quite likely that we'll do).
The new certificate's MD5 fingerprint is 72:43:C7:71:FD:E4:FD:7B:0C:0E:91:22:77:A4:3B:2B.
-
loftar
- Posts: 9096
- Joined: Fri Apr 03, 2009 7:05 am
- Location: Your character database
Administrivia: New certificate
"Object-oriented design is the roman numerals of computing." -- Rob Pike
-
theTrav
- Posts: 3464
- Joined: Fri May 29, 2009 11:25 pm
Re: Administrivia: New certificate
so what's the URL for that git repo again? 
-
Jimmymi
- Posts: 1
- Joined: Sat Aug 08, 2009 9:55 pm
Re: Administrivia: New certificate
how do i change it?
