Hi Matt,
On Sat, Apr 24, 2010 at 09:50:19AM +0100, Matt Holgate wrote:
Apologies in advance if these are stupid questions...
1) With previous VPS providers, I've found that I've had to symlink
/dev/random to /dev/urandom to avoid an issue where SSL/TLS smtp
connections would hang for a long time waiting for sufficient entropy to
setup the secure connection.
I've been looking into this after a couple of people mentioned that
they sometimes didn't have enough entropy.
I've bought an entropy key (
http://www.entropykey.co.uk/) and am
planning to hook it up to the entropy-gathering daemon. People who
are interested would then be able to run their own egd that talks to
mine in order to obtain more entropy.
This isn't a very high priority at the moment. I accidentally had
the ekey plugged in to a machine that doesn't have USB enabled in
the BIOS, so I need to visit the datacentre to sort that out, and I
don't plan to do that until I have a new server ready to install in
a couple of weeks. But I am working on it.
I've started graphing available entropy to see what difference it
will make, if any.
Typical VMs:
http://tools.bitfolk.com/cacti/graph_1847.html
http://tools.bitfolk.com/cacti/graph_1863.html
http://tools.bitfolk.com/cacti/graph_1900.html
I'll see how/if the ekey improves things.
[yes I am aware of all the wacky ideas of putting webcams in front
of lava lamps or in dark boxes, letting sound cards listen to static
etc etc.]
Is this something I need to do at Bitfolk too?
Unless you get entropy from somewhere else, the lack of real
hardware devices means a lack of entropy which means things which
require a lot of entropy like setting up SSL connections under GNU
TLS may be slow. If you can't get enough entropy then yes, forcing
things to use /dev/urandom when they really wanted /dev/random might
be your only option.
2) I've setup postfix (with TLS), and a
self-signed certificate. This is
fine for my purposes, but I wondered if there was a risk that other relay
hosts would be unable to deliver email to my box if they weren't able to
validate the certificate? If so, is there a way of forcing other relays to
use non-secure connections, while retaining the ability to do
authenticated SMTP over TLS?
As far as I'm aware, you get the choice of whether to verify the
other end's certificate but you don't get to tell the other end not
to verify yours.
I don't think many people verify certificates for SMTP, not between
themselves and third parties anyway.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting