On 5/19/07, Reiner Jung <[EMAIL PROTECTED]> wrote:
At the moment the OpenBSD core system is not controlled by the EAR so long
you don't download it
from a US server.
As a private person it is not a problem, but when a company want use
OpenBSD and there is US crypto
in, the thing will become ver
On Sun, 20 May 2007, dreamwvr wrote:
> > --
> > Mark Reitblatt
> >
> The entire world is not the US. The entire world AND the US is addressed
> by OpenBSD.
Mr Reitblatt should be advised that there are some of us in the USA
that are quite pleased with and in fact grateful for a reliable,
free a
On Sat, May 19, 2007 at 07:04:19PM -0500, Mark Reitblatt wrote:
> On 5/19/07, Theo de Raadt <[EMAIL PROTECTED]> wrote:
> >> > Can you quote a specific US law that says so?
> >>
> >> There is no need. US Law defers the specific details to regulatory
> >> agencies. The ruling in Junger v. Daley confe
thus Mark Reitblatt spake:
On 5/19/07, Chris Bennett <[EMAIL PROTECTED]> wrote:
Theo de Raadt wrote:
>
> Yeah, right. Those of us looking from the outside do not have such
> simplistic views of the US, sorry.
>
> But our viewpoint is not purely about OpenBSD as open source. We
> make our code
Mark Reitblatt wrote:
(Sorry, forgot to reply-to-all)
On 5/19/07, Reiner Jung <[EMAIL PROTECTED]> wrote:
Hi,
the export regulations from the US government are very strict when
there is
any crypto code
developed in the US. Developed in the US is = developed from a developer
when he stay in
th
On 5/19/07, Darren Spruell <[EMAIL PROTECTED]> wrote:
And having to "check in" with the beaurocratic mommies and daddies
whenever you patch said crypto code doesn't seem exactly free from
restrictions to at least me.
what are you talking about?
On 5/19/07, Chris Bennett <[EMAIL PROTECTED]> wrote:
How does current US law/policy affect someone traveling with OpenBSD? Is
having OpenBSD on my laptop a problem? Does downloading in the US from a
server outside the US solve travel problems? Is carrying OpenBSD on cd's
also a problem? I will so
On 5/19/07, Mark Reitblatt <[EMAIL PROTECTED]> wrote:
On 5/19/07, Theo de Raadt <[EMAIL PROTECTED]> wrote:
> > > Can you quote a specific US law that says so?
> >
> > There is no need. US Law defers the specific details to regulatory
> > agencies. The ruling in Junger v. Daley conferred protected
On 5/19/07, Chris Bennett <[EMAIL PROTECTED]> wrote:
Theo de Raadt wrote:
>
> Yeah, right. Those of us looking from the outside do not have such
> simplistic views of the US, sorry.
>
> But our viewpoint is not purely about OpenBSD as open source. We
> make our code available for people to use
> Your unreasoned paranoia/ignorance is hardly a useful excuse.
If you want to be insulting, why don't you start your own project
where you can set your own stupid rules.
You came here with an agenda, and you will leave here with your agenda
completelyignored. You are wrong. Noone cares about a
On 5/19/07, Theo de Raadt <[EMAIL PROTECTED]> wrote:
> > Can you quote a specific US law that says so?
>
> There is no need. US Law defers the specific details to regulatory
> agencies. The ruling in Junger v. Daley conferred protected speech
> status upon source code. That means no restrictions
Theo de Raadt wrote:
Yeah, right. Those of us looking from the outside do not have such
simplistic views of the US, sorry.
But our viewpoint is not purely about OpenBSD as open source. We
make our code available for people to use in a commercial setting,
so we must meet a higher standard.
As
> On 5/19/07, Theo de Raadt <[EMAIL PROTECTED]> wrote:
> > > After reviewing OpenBSD's current policies on US contributions of
> > > cryptography, and current US law, I'd like a clarification. Current US
> > > law (c.f. the short guide
> > > http://www.bis.doc.gov/encryption/lechart1.htm) allows th
Hi,
the export regulations from the US government are very strict when there is
any crypto code
developed in the US. Developed in the US is = developed from a developer
when he stay in
the US, when he work for a US company (also abroad), when he have a
green-card or when he is
US citizen and wri
On 5/19/07, Theo de Raadt <[EMAIL PROTECTED]> wrote:
> After reviewing OpenBSD's current policies on US contributions of
> cryptography, and current US law, I'd like a clarification. Current US
> law (c.f. the short guide
> http://www.bis.doc.gov/encryption/lechart1.htm) allows the unlicensed
> e
> After reviewing OpenBSD's current policies on US contributions of
> cryptography, and current US law, I'd like a clarification. Current US
> law (c.f. the short guide
> http://www.bis.doc.gov/encryption/lechart1.htm) allows the unlicensed
> export/reexport of open source encryption source code. T
After reviewing OpenBSD's current policies on US contributions of
cryptography, and current US law, I'd like a clarification. Current US
law (c.f. the short guide
http://www.bis.doc.gov/encryption/lechart1.htm) allows the unlicensed
export/reexport of open source encryption source code. The only
r
17 matches
Mail list logo
