Linux Security - Securing Nginx

In this video series, we will be taking a look at how to set up, secure, and audit Linux servers. This video will explain the process of securing Nginx.

SUPPORT US:

SOCIAL NETWORKS:

WHERE YOU CAN FIND US ONLINE:

LISTEN TO THE CYBERTALK PODCAST:

We hope you enjoyed the video and found value in the content. We value your feedback. If you have any questions or suggestions feel free to post them in the comments section or contact us directly via our social platforms.

Thanks for watching!
Благодарю за просмотр!
Kiitos katsomisesta
Danke fürs Zuschauen!
感谢您观看
Merci d'avoir regardé
Obrigado por assistir
دیکھنے کے لیے شکریہ
देखने के लिए धन्यवाद
Grazie per la visione
Gracias por ver
شكرا للمشاهدة

#Linux#Security#Cybersecurity

[HackerSploit]

Timestamps:

0:00 Introduction to the series
2:14 Video starts

[limpep]

you can test your config without restarting, using sudo nginx -t

[TheRealKuif]

Hey, I enjoyed the video. I think it would be good to add three pieces of information though. 1) Since you are not using https, your httpauth, and thus your username and password, are going to be sent in plaintext over your network connection. 2) Always add a non-root user with a different password than root, disable root login and enable certificate-only logins 3) If you feel removing banners is going to help your be more sure, then definitely go all the way and disable standard status pages. If the attacker has no information at all, he/she might first try, say, Apache exploits and wast some time and energy trying that, before it has a chance to try any relevant exploits.

[MrDaddyv]

You have one of the most concise and thorough catalogues on YouTube. Thank you.

[mathiasensimon]

I look up to professional like this man, more than I look up to celebrities. I love seeing people who just know what the fuck they are talking about

[FahadAli-otkn]

Hey you always making awesome content i am very thankful to you

[pupkinsen]

The argument for the location directive is the URI of said location. In this case it probably should have been "/", not "/var/www/html". That's why the access rules demonstration did not work. Also the auth_basic example is backwards. If you apply auth_basic to the whole server section it works in every location by default. You add auth_basic off; to the locations where you don't want auth.

[itwebadmin]

BACK AGAIN with another hacking tutorial! I remember watching the proxychain tut a few years back when I was just getting into Linux...done moved into development now... He wasn't showing his face back then...

[rahulkumarsingh]

Thanks for making these awesome videos😘😘😘

[miker]

Thanks for making this series. Lots of great information. One thing I noticed though. You don't need sudo if you are root

[spicyF]

I came here looking to learn something meaningful, instead your tutorial felt like something being regurgitated form your own cyber-security training..the mail settings in the config file were already commented, what does removing them achieve. Hiding the server version is 101 and thats more precautionary than preventative..to what benefit does applying a htpassword to my web directory serve..Great hope my visitors have telepathy to know it..like I said it just feels like your disseminating what youve been taught in theory with no real world application..and what is applicable most people already know

[zaskmartinas]

How to my hide my All information in cyber war, ,,, plz

[ripon]

Great video. I am newby, i have some question. If I put auth_basic for the default Nginx server it's asking me for the password. Can I put the same thing for the project inside the file in the same way for the hacker?

[mosesmbadi]

Linode denied my registration. I raised the issue and I haven't received any feedback. I wonder why they invest in all this marketing when their customer service is wack.

[stormand]

21 minutes and I keep waiting for the "securing" part -- is that adding htaccess, and disabling server token? You could have talked about this in 1 minute. Your video is about basic installation. Even at 10 minute mark you are barely starting.... just configuring a listen port and then docroot. You should change the title to "installation basic configuration of nginx"

[TheFarazahmed]

Hello, Can you please provide the installation and configure file in docx file

[AlexCernat]

Too much bullshit in this video, although some good info. But:
- root should (even "must", as best practice) specified in server block
- location means url, not doc root path location
- reload is enough (and it's cleaner for production servers), afaik use restart only when modifying listen parameters (simple reload didn't worked), not 100% sure when changing tls keys/certificates
- use configuration parameters as "up" as they can be (i.e.: if possible, prefer configuration in server block, or even up, not in location block)

[pratiksawant]

<h1> It was really helpful </h1>

[Meleeman]

njinx. lol thats how it should be pronounced

[NotBeHaris]

please provide a platform where we ask question. I also try to contact you on insta twitter everywhere but no reply. please.

#Pakistan