 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
17 messages in net.sourceforge.lists.courier-users[courier-users] Re: couriertls, rfc10...| From | Sent On | Attachments |
|---|---|---|
| Jon Nelson | Nov 25, 2003 7:52 am | |
| Andrew Newton | Nov 25, 2003 11:42 am | |
| Jon Nelson | Nov 25, 2003 12:09 pm | |
| Jon Nelson | Nov 25, 2003 12:10 pm | |
| Andrew Newton | Nov 25, 2003 12:51 pm | |
| Sam Varshavchik | Nov 25, 2003 5:48 pm | |
| Jon Nelson | Nov 25, 2003 6:15 pm | |
| Roger B.A. Klorese | Nov 25, 2003 6:21 pm | |
| Sam Varshavchik | Nov 25, 2003 6:29 pm | |
| Jon Nelson | Nov 25, 2003 6:55 pm | |
| Jon Nelson | Nov 25, 2003 7:00 pm | |
| Phillip Hutchings | Nov 25, 2003 7:43 pm | |
| Troy Benjegerdes | Nov 25, 2003 10:09 pm | |
| Sam Varshavchik | Nov 26, 2003 4:14 am | |
| Jon Nelson | Nov 26, 2003 7:10 am | |
| Sam Varshavchik | Nov 26, 2003 5:25 pm | |
| Julian Mehnle | Nov 27, 2003 2:51 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [courier-users] Re: couriertls, rfc1035, and /etc/hosts | Actions... |
|---|---|---|
| From: | Sam Varshavchik (mrs...@courier-mta.com) | |
| Date: | Nov 26, 2003 5:25:01 pm | |
| List: | net.sourceforge.lists.courier-users | |
Jon Nelson writes:
On Wed, 26 Nov 2003, Sam Varshavchik wrote:
Jon Nelson writes:
Well, 'localhost', for one, won't ever work properly.
And the consequences of that are�
It's not just localhost but anything and everything in /etc/hosts that is not otherwise reflected by DNS.
Again: and the consequences of that are?
You still haven't explained what the problem is, here.
The only impact of couriertls not consulting the hosts file is that the TCPREMOTEHOST and TCPLOCALHOST environment variables will not be set. Now, what exactly is the problem that's caused by that, in your case?
I thought that was the job of couriertcpd?
Ok, I misread what you wrote.
The problem is that a useful program, couriertls, and by useful I mean useful to a user to construct (de)-SSL/TLSify I/O streams, doesn't behave like one would expect it to. Beyond that, how many people here have expected a certain kind of behavior out of courier by altering the /etc/hosts file only to eventually learn that it is not (ever) consulted? How many people here have struggled only to learn that
Yes, I can see how couriertls might be useful in that context. Initially, I added the client options to couriertls purely for my own convenience, when I needed to debug SSL/TLS grok-age from a server.
And, I made a mistake of documenting those options.
That'll teach me a lesson: next time I do something useful, I'm not going to document it :-)
What's so hard about consulting /etc/hosts? It's expected behavior.
There's still the IPv6 issue. The traditional resolver API does not support IPv6.
There is a newer API that supports IPv6, defined by RFC 2553; but I don't know how widely it is implemented in various systems; or whether it checks the host files (it should, but I had no reason to bother to check). Linux had it since the 2.4 kernel series (and, BTW, I wrote the Linux man pages); however I don't think it's in Debian stable, which is still at 2.2. I don't know which of the BSDs have implemented it either. It's an unknown factor.
It wouldn't be too difficult to have couriertls use this, but I don't know how many systems will break.