Expired SSL cert or just me

Printable View

10-20-2014, 10:58
asmo

Expired SSL cert or just me

From a couple of different machines I show that the sites SSL cert is expired. Is this really the case?
10-20-2014, 11:00
00tec

Same here.
10-20-2014, 11:02
hghclsswhitetrsh

Will you explain to a dummy like me what that means exactly? I googled some stuff but not a while lot of sense was made.
10-20-2014, 11:06
drift_g35

Quote:

Originally Posted by hghclsswhitetrsh

Will you explain to a dummy like me what that means exactly? I googled some stuff but not a while lot of sense was made.

An SSL certificate is basically a cryptography layer between you and a website that confirms you are actually communicating with the website you think you are. It was to help prevent someone losing sensitive information when entering it into a website that was possibly hacked by someone trying to get that information.

This is the best "Simple" explanation I can give.
10-20-2014, 11:09
hghclsswhitetrsh

Roger. Makes sense. I won't use my SSN for a password anymore.
10-20-2014, 11:21
HoneyBadger

Yep, I'm getting it too.
10-20-2014, 11:55
mcantar18c

I'm on tapatalk, not seeing any notifications.
10-20-2014, 12:06
davsel

Started getting it a few minutes ago.
[panic]
10-20-2014, 12:10
Irving

Someone just bought a Tavor with my bank card.
10-20-2014, 12:11
sellersm

Yup, same here. Chrome keeps "warning" me...
10-20-2014, 12:12
StagLefty

Yup-Chrome keeps warning me.
10-20-2014, 13:50
DeadElephant

Damn ObamaCare!
10-20-2014, 14:30
cfortune

Cert just expired at 10:00 something AM today and trot is right, no difference in the security of the site prior to 10:00.

When you do a renewal, make sure to have your certificate authority do a SHA-256 certificate. Chrome and local cert stores for Microsoft (I think anyway, haven't looked too much into this) will start throwing certificate errors sometime in November. That's what Google has ball parked for their release which will enforce this. I just got done replacing all our certificates at work because of this.

Also, SSL v3 has a vulnerability right now and TLS without v3 fallback should be configured.
10-20-2014, 17:16
J

Yeah. Will have it replaced tonight.

It will be forward compatible
10-20-2014, 17:34
J

AAAANNNNNDDDDD.... Fixed.
10-20-2014, 17:36
hghclsswhitetrsh

Sweet I will change my password back to my SSN.

Seriously though, thanks J.
10-20-2014, 18:05
cfortune

Thanks J!
10-20-2014, 18:15
J

And SSLv3 disabled now too. Not that I worry about it as much here, we are providing basic privacy security for posters, not protecting financial or ultra-sensitive information. Had already done that on all of my eCommerce sites/clients.
10-20-2014, 22:20
HoneyBadger

Quote:

Originally Posted by DeadElephant

Damn ObamaCare!

I vote for this as the best post in the thread!
10-21-2014, 11:20
Guahan671

[Coffee]got that yesterday and figured it would go away, so here I am back on... good thing I came here first, was gonna post something like this... oh well, Good Day All.
10-21-2014, 11:29
cfortune

Quote:

Originally Posted by J

And SSLv3 disabled now too. Not that I worry about it as much here, we are providing basic privacy security for posters, not protecting financial or ultra-sensitive information. Had already done that on all of my eCommerce sites/clients.

Yeah, I neglected to add "not that it matters much for this site".
10-23-2014, 09:21
DeusExMachina

Quote:

Originally Posted by cfortune

Cert just expired at 10:00 something AM today and trot is right, no difference in the security of the site prior to 10:00.

When you do a renewal, make sure to have your certificate authority do a SHA-256 certificate. Chrome and local cert stores for Microsoft (I think anyway, haven't looked too much into this) will start throwing certificate errors sometime in November. That's what Google has ball parked for their release which will enforce this. I just got done replacing all our certificates at work because of this.

Also, SSL v3 has a vulnerability right now and TLS without v3 fallback should be configured.

This is good advice. The new certificate is unfortunately SHA1 still. Edit: Nevermind, was looking at the thumbprint.