On Mon, May 24, 2010 at 18:14, mouss <[email protected]> wrote: > As far as I know, it was never standardised.
Good enough reason for me to not use it. >> I get mine from IANA and 465 is assigned differently. > > what OS do you run? if smtps != 465 on your system, then the default > master.cf doesn't work for you, which means you have an odd system (and > not the opposite)... Several. The current project is on Ubuntu 9.10. I may move it to Slackware 13.1. Nothing odd about these or any others I have used. I do update and upgrade where practical. I'm finding that with Ubuntu that's not always so, beyond what they pre-package. But for the /etc/services file, that's never been a problem to regularly get the official one from IANA, which I have been doing for a couple decades. > wrapper mode SSL != STARTTLS. the former means the SSL/TLS negociation > happens before anything else. This provides more "confidentiality" (with > https, a sniffer doesn't know where you're trying to go), but it also > creates problems (for example, you currently need one IP per https > server [until the extensions to workaround this are widely implemented]). Even with STARTTLS (or STLS, or A STARTTLS, or whatever is used for some protocol), you still need one IP per hostname identified certificate, unless you have some means to select the host in advance that is safe to do (not sure if that is possible). > STARTTLS is enough, if you want control at app level. if you don't, then > use IPSec. There is no need to invent useless protocols (the more > protocols we have, the more opportunity for incompatibility, bugs, > vulnearbilities, ... etc). It is hard for firewall level controls to force encryption, unless it is known that a given port always does. So from that perspective, wrapper mode TLS/SSL is easier, when using standard ports for that. You (in the role of firewall admin) can, for example, allow port 443 and disallow port 80 to ensure everyone is using encryption. In the case of ports using STARTTLS or the like, you need to do sniff into the TCP stream layer and see if STARTTLS is really being done (or be the server admin and force it there).
