Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Nada. If I nmap my localhost I see pop3s running on port 995. However both Thunderbird and OE say they cannot connect. Is there a another step I'm missing? I'm a complete newbie when it comes to SSL so please bear with me.
One thing... You may want to be sure the permissions on the certificate is read only by the owner and no other permissions.... I think the owner and group should be root/root. I know that was a problem for me. Once I got the perms correct, it started working fine.
Hold on a minute... I just realized something... I have a seperate supervise for my secure stuff. I copied /var/qmail/supervise/qmail-pop3d and made /var/qmail/supervise/qmail-pop3ds for the secure version. The run file we created in that earlier post goes under there. This way, I still have normal pop3 running on port 110 so it doesn't interfere with the one running on 995.
I also have /var/log/qmail/qmail-pop3ds directory so it logs to there. That also means I have /var/qmail/supervise/qmail-pop3ds/log/run file that is identical in permission and content as the normal qmail-pop3d. That way, I have seperate logging for the secure version too.