|
|||||||||||
|
Re: [Users] Announce: FreeS/WAN Project Ending
From: Paul Wouters <paul(at)xtdnet.nl>
Date: Tue Mar 09 2004 - 11:01:45 EST
> If you want to put a system like OE in place and have it widely used,
We have made it simpler, though not faultless yet. If the last bugs are ironed out, there is no configuration of the user neccessary, apart from having a valid hostname and key in the forward dns. > really common. (When I mentioned this difficulty a long time ago on
Access to the reverse is only needed for OE on servers, not for clients connecting to it. Also, with the widepsread use of NAT required us to also store the key in some forward zone. > system more successful (IE, trivial to use). Throw in dynamic IP
host -t key vaio.xtdnet.nl. (or use a txt record) > 1) PGP. pgp has key servers to help connect 2 otherwise
We have written the hooks for dhclient to push the TXT/KEY record from your machine into a forward zone you can control. Though I don't think any of the free dns zones accept dynamic updates might I might be wrong or should start one myself :P > 2) SSH. ssh exchanges the public keys in the first connection, asking
But this only works because nerds use ssh. If your Director of European Sales uses somethign like this to connect to the corporate VPN, do you think this is still such a good idea? Do you think he might click "no" when the key claims to have changed because his neighbour laptop is being a man in the middle? Also, for ssh this is used in a scenario where you connect to a few trusted ssh servers. OE is meant to connect to everyone and their grandmother, and you would be hitting "yes i don't care the key changed' every 5 minutes. > OE is a good technology with good goals. But to say that you're
Why also includes the inability of IETF to come up with decent standards within a decade (KEY record, DNSSEC, secure DHCP), Microsoft's goal of moving everything into their (or Larry's) LDAP, Verisign/NetSol/ICANN politics instead of deploying on technical merits, ISC's arcane slow development of ISC dhcp in the last two years and the ISC "conformance" of the bind software to not release until the all the AD and the RFC Editor hav died of old age :P Why also included the "no US code" politics, dropped by Openswan. Sorry for ranting :) Paul FreeS/WAN Users mailing list users@lists.freeswan.org https://mj2.freeswan.org/cgi-bin/mj_wwwusr Received on Tue Mar 9 11:19:16 2004 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 13:02:11 EDT |
||||||||||
|
|||||||||||