Was: What do you guys think about this? Is: Olaf, are you there?

[email protected]
Newsgroups gmane.comp.encryption.cipe
Message-ID <[email protected]>
People,

I saw the post at /. 2 days ago.
Not having a single line from Olaf about this thread HERE is driving me
crazy. Does anybody has a more personnel contact with him to tell me if he
is - at least - informed about what's going on at /. and here?

TIA,

RSalles



> <rant>
>
> Well, that's exactly the kind of thing that is irking me. This guy IS a
> respected and knowledgeable cryptography expert but he is of the apparent
> opinion that we are not capable of figuring out our own needs and
> obtaining/developing the solutions for them.
>
> I'm especially  perturbed because I spent time writing the Win32 port
> AFTER
> eschewing PPTP, IPSec and a host of others in favour of CIPE, knowing
> fully
> well that if an intermediate router decided to capture the entire stream,
> it
> was possible to perform a replay attack. I'm particularly insulted because
> I
> spent most of a year implementing a protocol that, in his 15 minutes, he,
> along with the Slashdot crowd, has decided should just be scrapped and
> abandoned. What, exactly has he written to fill our need ?
>
> Only one Slashdot poster (a professional, it appeared) was able to
> articulate
> that the "solutions" that Peter Gutmann proposed would prevent non TCP
> protocols from utilising the VPN properly. The alternatives suggested have
> the same problems that they had when I first looked at them.
>
> </rant>
>
############# cut ##############




--
Message sent by the [email protected] mailing list.
Unsubscribe: mail [email protected], "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.