When setting up a second SSL Apache virtual host, you may be frustrated when your browser can't connect and tells you something like

Safari can't establish a secure connection to the server "servername"


In your ssl_request_log you see baffling entries like this:

"\x16\x03\x01" 240
"\x16\x03" 240


This is because you have forgotten to enable SSL for your virtual host with the following:

SSLEngine on


You'll probably need some other SSL-based directives in there, too.

Reference:

You've spent hours getting your encryption keys in order. You've successfully got a granting key and a crypt key from your pubcookie server. Your Apache ssl.conf is finely honed and your external SSL tests are flawless.

Yet your users can't log in. They're not being redirected to the central login server. Instead, they see messages like

I wanted to run Darwin Streaming Server on Red Hat Enterprise Linux 6.

I made binary RPMs for 64-bit RHEL6 using these instructions. My changes:

• fixed the symlink at /var/dss/modules to point to the correct directory
• worked around the fact that DarwinStreamingServer -x does not exit when run
• changed config path so that login to the Web Admin is possible

To install on RHEL6 (or CentOS 6, I presume):

I've been using the EnGenius ECB9500 wireless access point quite a bit. It has a lot going for it: small in size, power-over-ethernet, low cost.

One thing that has been a thorn in my side is that up til now, SNMP monitoring has been difficult because the built-in firewall rejects packets that are not from the same subnet that the IP of the WAP is on. Naturally my monitoring lives in the server room which is on a different subnet.

The firmware changelog notes that this was fixed in 2.3.0: