Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
before i read this article i configure http.conf file to listen on both 80 and 443 ports and with that configuration i could contact to my website without further configuration.i didn't even define a virtual host.how is that possible ? is this normal ?
no idea what you even mean without seeing your config. Seeing as you don't mention creating your own cert are you just listening for plain text connections on 443? Not exactly useful. You don't *NEED* a virtual host to do SSL.
i said i didn't create certificates.just add port 443 to listen directive.but yet i can make ssl connection to the website.why is that ?
i used to try this on debian, but on debian you have to create certificates.i was wondering why it's not applied on centos!?!?!?
I presume there are default self signed on ones them, not really "interesting" TBH, just a self signed certificate that will be referenced in the ssl.conf file.
That's right. Presumably, CentOS handles the situation the same way as their upstream (RHEL). There are likely self-signed certs in place. Check /etc/httpd/conf.d/ssl.conf for their file locations.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.