>Apache 2.0 has general programming hooks that are sufficient for adding
>crypto.
And so does the UNIX shell:
tar cf - . | ssh -C foo 'tar xvf -'
Dunno how far they tried to control this even under the old regs.
Phil
Joe Francis wrote:
>
> Given this:
>
> "``Open cryptographic interface''. A mechanism which is designed to
> allow a customer or other party to insert cryptographic functionality
> without the intervention, help or assistance of the manufacturer or its
> agents, e.g., manufacturer's signing
Given this:
"``Open cryptographic interface''. A mechanism which is designed to
allow a customer or other party to insert cryptographic functionality
without the intervention, help or assistance of the manufacturer or its
agents, e.g., manufacturer's signing of cryptographic code or
propr
> Apparently they have been published now. I waited for the day of
> publication, not the second, which I hope is sufficient.
I found them on the Federal Register site, in the "Documents Published
Today" page. They are published. Here's their URL:
http://frwebgate.access.gpo.gov/cgi-bin/getd
On Fri, Jan 14, 2000 at 11:54:21AM -0500, Jeffrey Altman wrote:
> You can't do this yet. The rules have been announced but they are not
> yet in effect. The rules do not go into effect until they are
> published in the Federal Register.
>
> [Although rumor has it that they're being published wi
> On Thu, Jan 13, 2000 at 10:28:52AM +, Ben Laurie wrote:
> > Perhaps the easy answer is for someone to attempt such an export with
> > email notification and see what BXA say about it!
>
> I'm willing to give it a try. I sent an email to BXA and got no reply.
> The rules do not say I need p
On Thu, Jan 13, 2000 at 10:28:52AM +, Ben Laurie wrote:
> Perhaps the easy answer is for someone to attempt such an export with
> email notification and see what BXA say about it!
I'm willing to give it a try. I sent an email to BXA and got no reply.
The rules do not say I need permission, j
Phil Karn wrote:
> What still confuses me are the circumstances that let you just send
> an email pointer to BXA, and which ones require a review of some
> sort before you can export.
Well, the press release says:
> Global Exports of Unrestricted Encryption Source Code
>
> Encryption source cod
I am very interested in how these regulations would affect the development
of open source software, for instance:
Can USA residents now contribute to projects such as OpenBSD and FreeS/WAN?
Can the international crypto extensions be folded into the general Linux
kernel?
Can software now be writ
Okay, I've read the latest version of the regs. As usual, they're long and
confusing, with exceptions to the exceptions to the exceptions. But
several things seem to stand out.
1. You can export pretty much anything to anyone but a foreign
government or to the seven pariah countries (Libya, Iraq,
From: David Sobel <[EMAIL PROTECTED]>
Subject: BXA release URL
John -
It's at:
http://204.193.246.62/public.nsf/docs/60D6B47456BB389F852568640078B6C0
Also, I've put up the HTML of the regs. CDT has them up and
they appear to be "public" at this point (the National Journal
was saying earlier t
11 matches
Mail list logo
