Defend this shit, trying http brings you here too,google and YouTube do this too

This is next level brainlet

>Defend this shit
ok
SSL certificates expire, therefore your clock has to be correct.
>http brings you here too,google and YouTube do this too.
Based website redirecting you to https like it should

Fuckin proprietary time with capitalism clocks

no this proves duckduckgo = botnet just like jewgle. they are tracking your dates

HTTPS add a dramatic amount of overhead. For example, Nginx with SSL termination required 6 cores and la was on 5.5x to serve 200 concurrent connections while it was fine with serving 200 HTTP connections with just one core.
Also there's no need to add additional layer for simple devices and there are scenarios where SSL cyphers support is outdated and therefore it's better to have at least some data than nothing at all, at the expense of security.

you fucking idiot
it's not the fucking website it's your fucking browser
it checks the time and if the time is wrong it throws that page

why should it even care about time you God forsaken retards

...

Attached: 8a2af66f-40ad-46a0-bc7c-4564404604f5..jpg (225x225, 10K)

I wonder who's behind this (((explanation)))

me

>your system Time has to be correct to search anime titties

why in the christ would you not set your clock to the correct time
how many tons of tin foil are on your head

>your system time has to be wrong

No, it has to be right for HTTPS certs to work.

Here you go retard tools.ietf.org/html/rfc5280#page-22

Do you think duckduckgo is going to single you out and track you down because your using the CORRECT date?

What is your fucking thought process? Do you think you're going to stand out less when your one of the few with an incorrect date?

Attached: raphi_btfo.gif (500x281, 1.63M)

- AES-NI
- ChaCha20-Poly1305
- QUIC

Attached: kWPzPIv.jpg (400x400, 35K)

Question:

Can a site only allow access to a set (non-current) time? Like only allow connections with systems set to June 2006 or something.

If even JS can get it, what would prevent it?

Attached: ss (2019-02-14 at 20.41.59).png (228x102, 3K)

Yeah I'm sure they're going to track you more easily when you use the current date.

Just make the certificate only valid for a particular time window that much match the system time? I don't know much about SSL certificates so apologies.

>they're tracking the current date
holy shit stop the presses

Hi OP here
i forgot to mention that im a GIANT faggot who loves sucking cock and drinking cum

>Just make the certificate only valid for a particular time window that much match the system time
Well that's how they work
never tried it so I dunno
In theory, the browser COULD ignore that the certificate expired, but usually they don't

100000000/10 troll

Attached: 64K MERE MORTALS CANNOT EXPERIENCE THIS HD.png (3360x1200, 954K)

What the fuck does it need your date for? What the absolute fuck? What if the server system time is 1999?

it seems like a decent pleb filter to require users to know how to set system time (or at least trick the browser) to allow access to, say, a technical forum.

Technically you could generate a certificate with any valid from/valid to dates (so long as to is after from), but CAs would likely decline to sign it so you'd additionally need to add it as a trusted certificate on any machine connecting or have users click past a different error.

Not sure if you're being a retard on purpose or not, either way here is an explanation on why you're dumb
youtube.com/watch?v=ylfyezRhA5s

you'd have to get the user's time, then modify the cert on the fly just for that specific user
not feasible unless you are your own CA or you want the user to see the https invalid cert warning
also unless you have a custom webserver you'd have to install the newly generated cert for every user
best case scenario, 1 user can make a request every 5 seconds, and that's assuming you can come up with some transparent https -> http downgrade while keeping user state (so you don't end up generating a new cert when a user refreshes your webpage)
in theory you could have a cert with a valid from date really far back, but some browsers may not allow that, and that's just terrible practice in general
the easier solution is just to not require https. want to use https? fine, fix your system time.

The real botnet is that secondary registry google is trying to run in tandem with the CA. forgot it's actual name, but you avoid "problems" if you register your internal network information to them when creating your certificate.