Love the lectures! I think my favorite part is that you explain a subject and then immediately go into a demo that I can try at home. It's been a blast watching these videos and messing around with the demos on my computer
I am currently doing Stanford cs 142 web application and just finished project 6 yesterday. this class will be my online class. and thank you for posting these good resource.
Truly made of all precious metals. If the foundation is strong, you can never (G0lang) wrong. Fundamentals are solid, our mindsets rewarded. Keep hunting for bugs 🐛 and sharing our hugs.
2:07 - Client makes a request - DNS server sends IP address for a specific domain 10:10 - hardcode DNS for testing 11:45 - how https can help us 17:39 - HTTPS - the isp would not be able to prove the certificate - hence it could not be done to an HTTPS site 19:53 dns over https 35:06 - proxy - when you want a single server to outside world - that powered by multiple servers 47:32 - Protocol stack 59:08 - Twitter example
Hi Feross Aboukhadijeh !, Nice Lectures, Thanks for All your Hard Work and Motivation. I understand you were using a stationary microphone, I humbly advise you to use a Headset Mic. All your future presentations and courses will be on Point in regards to Audio. Just a piece of humble advice. Thank You for the Material and Good Luck, Hope to meet you someday. ka1ku from Puerto Rico, Peace! Hack the World !!!
does anyone else think he sounds and talks like elon musk? or elon musk sounds like sir Feros Aboukhadijeh !!! Good work ! Thank you for making it available for everyone out there...real good work !
Hi Feross.. Excellent Information. I am little stuck in the end of cookie demo. I created html and server js file but when I start node server.js It's throwing error... "internal/modules/cjs/loader.js:818 throw err; Error: Cannot find module 'express' " Even after installing express through npm.
I got a question, you mentioned HTTP is stateless - yet when we have a header like "Connection: keep-alive", we're instructing the server to keep that unique connection alive, thus isn't that similar to maintaining a session/state?
Hi, @SecDive it look like HTTPS/2 doesn't suport Connection fields. " HTTP/2 does not use the Connection header field to indicate connection-specific header fields; in this protocol, connection- specific metadata is conveyed by other means. An endpoint MUST NOT generate an HTTP/2 message containing connection-specific header fields; any message containing connection-specific header fields MUST be treated as malformed" datatracker.ietf.org/doc/html/rfc7540#section-8.1.2.2
@@leandrodaluz5538 Thank you for that. I was just curious about how those headers have been working all this time, before HTTPS/2, since HTTP is stateless, so what's the significance of those connection-specific headers?
Well, I don't know nodejs, (should I really master it as a pentester?) like I am able to read the code and understand it, but can't code it very well, like as a developer.
Really amazing you just posted this on TH-cam. Ivy League education really is available to those looking for it. Very much appreciated.
Love the lectures! I think my favorite part is that you explain a subject and then immediately go into a demo that I can try at home. It's been a blast watching these videos and messing around with the demos on my computer
Came for Security, Learnt how web works - 10/10 amazing content!
That was my secret goal in teaching this course!
I am currently doing Stanford cs 142 web application and just finished project 6 yesterday. this class will be my online class. and thank you for posting these good resource.
Thank you so much Feross! This entire series is gold!
Truly made of all precious metals. If the foundation is strong, you can never (G0lang) wrong. Fundamentals are solid, our mindsets rewarded. Keep hunting for bugs 🐛 and sharing our hugs.
Feross good job man! You are really good at explaining cookies, http and sessions. I've been learning something new everyday thank you :)
2:07 - Client makes a request - DNS server sends IP address for a specific domain
10:10 - hardcode DNS for testing
11:45 - how https can help us
17:39 - HTTPS - the isp would not be able to prove the certificate - hence it could not be done to an HTTPS site
19:53 dns over https
35:06 - proxy - when you want a single server to outside world - that powered by multiple servers
47:32 - Protocol stack
59:08 - Twitter example
So much insights in such short video! Thank you!
Hi Feross Aboukhadijeh !, Nice Lectures, Thanks for All your Hard Work and Motivation. I understand you were using a stationary microphone, I humbly advise you to use a Headset Mic. All your future presentations and courses will be on Point in regards to Audio. Just a piece of humble advice. Thank You for the Material and Good Luck, Hope to meet you someday.
ka1ku from Puerto Rico, Peace! Hack the World !!!
@@Ferossity Great Job Jedi Master, the Force is Strong Within You.
Amazing Lectures, learned a lot thanks for uploading this...This playlist is just incredible!
does anyone else think he sounds and talks like elon musk?
or elon musk sounds like sir Feros Aboukhadijeh !!!
Good work ! Thank you for making it available for everyone out there...real good work !
Amazing course! Thank u for sharing it with us!
Awesome lectures. Can you please upload the slides on course website ☺️
i suggest String.trimStart instead of slice to shape the request string.
Thank you, this is really great!
Hi Feross.. Excellent Information.
I am little stuck in the end of cookie demo.
I created html and server js file but when I start node server.js
It's throwing error...
"internal/modules/cjs/loader.js:818
throw err;
Error: Cannot find module 'express'
"
Even after installing express through npm.
Awesome, thank you sir!
Thank you very much!
really nice
it is possible for non Stanford student to do assignments and check later for good solutions?
Thanks
For the cool live demo at the end of this course, any guide or modules I can refer to to build something similar with Python?
how can I create an account at lean bank? :D
I got a question, you mentioned HTTP is stateless - yet when we have a header like "Connection: keep-alive", we're instructing the server to keep that unique connection alive, thus isn't that similar to maintaining a session/state?
Hi, @SecDive it look like HTTPS/2 doesn't suport Connection fields.
" HTTP/2 does not use the Connection header field to indicate
connection-specific header fields; in this protocol, connection-
specific metadata is conveyed by other means. An endpoint MUST NOT
generate an HTTP/2 message containing connection-specific header
fields; any message containing connection-specific header fields MUST
be treated as malformed" datatracker.ietf.org/doc/html/rfc7540#section-8.1.2.2
@@leandrodaluz5538 Thank you for that. I was just curious about how those headers have been working all this time, before HTTPS/2, since HTTP is stateless, so what's the significance of those connection-specific headers?
Does the node.js example not work for anyone else?
Thx Man!
Great Series.
Does anyone know where can we access the lecture slides/presentations?
I should add a link to the current year website: cs253.stanford.edu
Well, I don't know nodejs, (should I really master it as a pentester?) like I am able to read the code and understand it, but can't code it very well, like as a developer.
I just saw the assignment 0 and course description, it solves my resources problem but the question still bugs me. Thanks in advance if you reply, lol
Some things are left out.
audio volume goes up and down