XDSL, or more properly, xDSL, is a generic term for Digital Subscriber Line technology. It includes ADSL and SDSL, and all the other DSL variants.
I suspect you probably have something called DSL Lite, a splitter-less variant of ADSL that's being pushed for lower cost.
Like many people have pointed out already, it's the carrier, not the last mile technology, that is the current bottleneck. It shouldn't really matter if you go with cable or dsl.
Sounds like a job for IPSec, with opportunistic encryption.
1. Mail server agnostic Heck, it doesn't care what you're running over it, be it email, web traffic, or telnet sessions. There are implementations available for many operating systems, too.
2. Falls back to cleartest if encryption isn't supported at the other end If an encryption key isn't found in the DNS entry for the target host, it falls back to plaintext. Normally it won't warn you about this (since it's not widely deployed, most connections are going to go unencrypted)
3. Uses existing algorithms[...] IPSec is an existing protocol, with several mostly-interoperable implementations available.
Note that IPSec is transport-level encryption, not session-level. It protects traffic between two hosts, but not necessarily between two users.
For more information on IPSec, and the FreeS/WAN Linux implementation, see www.freeswan.org
Slashdot Mirror
XDSL, or more properly, xDSL, is a generic term for Digital Subscriber Line technology. It includes ADSL and SDSL, and all the other DSL variants.
I suspect you probably have something called DSL Lite, a splitter-less variant of ADSL that's being pushed for lower cost.
Like many people have pointed out already, it's the carrier, not the last mile technology, that is the current bottleneck. It shouldn't really matter if you go with cable or dsl.
Sounds like a job for IPSec, with opportunistic encryption.
1. Mail server agnostic
Heck, it doesn't care what you're running over it, be it email, web traffic, or telnet sessions. There are implementations available for many operating systems, too.
2. Falls back to cleartest if encryption isn't supported at the other end
If an encryption key isn't found in the DNS entry for the target host, it falls back to plaintext. Normally it won't warn you about this (since it's not widely deployed, most connections are going to go unencrypted)
3. Uses existing algorithms[...]
IPSec is an existing protocol, with several mostly-interoperable implementations available.
Note that IPSec is transport-level encryption, not session-level. It protects traffic between two hosts, but not necessarily between two users.
For more information on IPSec, and the FreeS/WAN Linux implementation, see www.freeswan.org