Transport Layer Security (TLS) - Computerphile 

Try that in real life

@Peter Lustig We're not gonna feed you here, buddy.

@@AWES0MEDEFENDER it was actually the first one that got so much hype lol

Poor Alice and Bob, now they can't communicate with each other.

@@realshaoran4514 Oh they still can, if they yell really really loud in their room just like my actual neighbors. The only problem is my neighbors knows nothing about TLS.

i dont mean to be so offtopic but does anybody know a tool to log back into an Instagram account?? I stupidly forgot the login password. I would love any tips you can give me

@Iker Alfonso instablaster :)

This is a very engaging way of teaching.

that's the trait of the smartest and impassioned teachers. They're able to get your attention with the toughest topics.

Great Idea!

It started as an alternative (replacement) to gif and as such it had actual frames (12 frames at 12fps would be 1s in length) which were loaded progressively. This means that once actionscript was introduced you could execute the code (show preloaders; play sounds, animations, ..) before the app was fully loaded(!) - that's one of the things i loved about flash and still miss in today's tech. Instead of hundreds of requests that we do today, there were only a few in flash - webassembly might change that.

I think Microsoft announced that they have permanently removed flash with the latest version of Win10/

@@RichardBuckerCodes Their built-in version, anyway, that I believe was used for Edge. You can still install it yourself, if you want to for some reason. Google will be removing Flash from Chrome in December.

It was deprecated because browsers started to support video natively with HTML5. Steve Jobs answers this brilliantly on a All Things Digital interview done some years ago.

🤣 LOL ah fun times

Wireless networks work the same way though

The modern replacement for a hub would be a switch really, we still had routers back then and they serve a different purpose to a hub/switch.

@@GamingBlake2002 Yes but the data is all encrypted so "the right tools" includes getting the encryption key.

@@vinny142 But the application data may not necessarily be encrypted, and the encryption done by the router can be reversed, since you're also connected to the network and therefore have the key.

Same thing for tutorials about anything relating to technology though - JavaScript, html, databases, RF engineering, photolithography, power infrastructure, just to name a few

@@signalworks You could even say something similar when you learn anything. You are using something to learn how to use that thing For example, you use math to learn how math works

@@h-0058 I think there's a slight difference between the use of the word "use" - building on basics to learn deeper concepts is one thing, but having the knowledge delivered to you by application of the knowledge itself is another.

@@havetacitblue Hi, yep - it's just amazing how things have progressed. I still love IT and all it's weirdness. GEEKY BOYS RULE!

@@RARPoodlefaker I’ve been burned out multiple times since 1980. TLS and security in general have given me a new lease on life...Buggy though it all may be.

So you’re to blame!

I suspect 2 or more videos after this, one or 2 going deeper into basically everything up to TLS1.2 and then a third which talks about all the new TLS1.3 stuff.

Bumping this comment because if I remember correctly the older versions of TLS have been deprecated nowadays

Only 1.3 should be used at this point,,,

It's a teacher thing

Ilp start adding alright instead of punctuation in my text

It’s a Limey thing...or sniffing a la Billy Idol.

honnest, hold a entire OSI model on a 20minutes format video isnt reallistic, 4-5videos maybe

@@playmaker4053 only talking about doing an overview. Wasn't suggesting going into detail about each protocol or anything. Anyone that knows the model well could easily talk about it for hours, but that doesn't mean you can't give a 20-minute overview to anyone that doesn't know it. For each layer, here's the name, its overall purpose is this, here is a list of a few of the protocols at this layer. Even this approach might be helpful to newcomers and would only take a few minutes to list, leaving plenty of room to go into more detail where they want and leave room for padding with banter. 🤣

No pen spins today, but I just noticed his very strange common P.

Da POUND, POUNDin it

Yes Mike's camera is on auto white balance and the sun kept coming out changing the brightness & colour temperature - hth -Sean

LOL, actually true

I'm pretty sure you need them. otherwise Man in the middle attacks are possible.

you don't need certificates, you can use pre-shared symmetric keys, then you use PSK key exchange or you can use raw keys, then you need to have some other way to know if you're getting the right key from the server or not

Certificates are a container for keys that are authenticated through a process called signing. They can be self-signed (usable but considered very dodgy) or they can be held by a certificates server (certificate authority, or CA) which is guaranteed to be an "Honest Ed" source, aka a _Root of Trust_ . Your browser holds a list of CA's to authenticate that the peer (eg. web server) is who it says it is. This is my brief explanation of *a* certificate, it's a bit more complicated then that. also I am not guaranteeing that it's all in-line with actual TLS operations; I am basing the explanation on a similar system, CurveCP using the Curve25519 elliptical encryption. I believe it's close. Cheers,

I believe that TLS requires a certificate as a single thing to transfer that includes both a key and proof that this is the right key. It doesn't require the standard PKI with the CAs like LetsEncrypt abd Verisign, though; the server can present any certificate that chains back to a certificate that the client trusts, and the client could have gotten that certificate in a variety of ways. For example, a chat client can contain the certificate that's expected to have signed the server certificate for the server the client will connect to.

Different configurations both require and don't require certificates. Older algorithms use public/private keypair to encrypt the transfer of the symmetrical keys that encrypt the data and so require one. Modern algorithms use Diffie-Hellman (and ECDHE) to agree a shared key without reference to the public key and so only use the certificate for authentication. Older protocol versions allowed a pre-shared key variants of the algorithms; these are not available in modern versions. Bottom line; yes certificates are now required, however, they only have to be publicly notarised if you want the public to connect to your server.

@Stay EZ My Friends Thanks Buddy

@Stay EZ My Friends thanks! didn't know about that. Something new! 😃👍

If you create or use a protocol that does what the layers under TLS do (TCP, IP, ETH) then yes, it'll work as a layer above that protocol. You can probably even reuse existing TLS implementations.

TLS is built on top of TCP/IP so it is probably not interchangeable to other protocols as is. the other protocols would require to be similar to TCP to work. But the biggest question is why would you want TLS in other protocols. specially USBs. USBs require a physical connection, so, you should know what you are connecting. Also, TLS relies on certificates, which would make it hard for low level devices to carry around it's private certificate around

@Stay EZ My Friends Which part exactly?

@@superjugy yeah I didn't mean actual TLS as-is into the other ones. The reason someone would want authentication even for short physical connections remains the same. If I am replacing a battery pack in my car or color cartridge in my printer, I would be curious to know if those add-ons are authentic or not. Just an example.