*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
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.
I have my web server set up with several virtual hosts as well as the default web site. I'd like to make it possible so that when users go to a certain virtual address that the site is thrown up "SSLified". I don't want the other virtual hosts secured nor the default web site.
I created my certificate and signed it myself and started Apache with the -DSSL switch so that it is using it.
What needs to be put into the virtual host configuration to support this, and if users hit the address on port 80, will it automatically start an SSL session and go over :443?
You're kidding. And in the event that it's a publicly addressed server, you deal with throwing in a new IP for each secured virtual host? All right.
Given then that I have only one virtual host I want to secure, and I have port 80 on my router NAT'ted in through to this server's port 80, feasibly I can NAT port 443 on the router into an alias I set up on this host on port 443 and still be OK, no?