[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: VPN bakeoff in October & export licensing.
> I thought the US has relaxed the export stuff to allow DES56-bit now - since
> that's the extent of what we'll be testing, maybe we don't have a problem?
Maybe. I hadn't heard about that change (although I might not have, since
our project has no further interest in DES56 except to laugh at it), and I
would suggest double-checking. I also suggest checking for footnotes like
"but you still have to fill out form 12345 for each item exported". It
only takes one slip to get your code contaminated.
> In any case, it is VERY unlikely we'll be fixing core crypto code - it will
> be fixes to L2TP and IPSEC signally code if anything...
It doesn't *have* to be the core crypto code; remember that "enabling
technology" is export-controlled too, and the bureaucrats have often taken
a broad view of what that encompasses. I'm sure anything labelled IPSEC
would count.
I think much depends on just how unquestionably clean you want your code
to be. If you want to be really sure, don't touch it at all from the US.
Henry Spencer
henry@spsystems.net
(henry@zoo.toronto.edu)
References: