Prev: why does PKCS#1 use the LCM instead of Euler's totient function?
Next: Asymmetric key length recommendations
From: Maaartin on 17 Apr 2010 19:58
On Apr 18, 1:15 am, MK1024 <megank1...(a)hotmail.com> wrote:
> but I now think those laws are there for a reason

No they're not. With all the papers publicly available worldwide, do
you think you could stop anybody from implementing it? With everybody
in the western countries having access to so many programs, do you
think you could stop anybody from getting it? A single spy in any
western country could have smuggled it out anytime during the last
years.
See also http://cr.yp.to/export.html
DJB also pointed that putting restriction on strong ciphers export
makes no sense as long other cryptographic primitives are not
restricted.

> something bad with my code, I would expect to get into trouble.

Despite the law being a total bullshit, this may be true.
From: starwars on 18 Apr 2010 10:01
> > What would happen if I posted come code samples here or on a non
> > Australian code sharing website?

Use Mixmaster and you can avoid most problems unless your work is good
enough to upset major three letter beaureaux. The locals won't be able to
trace you and they won't get help from the big boys.

From: Mok-Kong Shen on 19 Apr 2010 04:18
MK1024 wrote:

> What would happen if I posted come code samples here or on a non
> Australian code sharing website?

It seems that even in US the export regulations aren't exercised with
the same energy by the authorities now as several decades ago. (That's
maybe there are other problems there that have higher priorities, e.g.
wars.) If you want to be absolutely safe, post in an internet cafe with
a pseudonym.

M. K. Shen
From: Tom St Denis on 19 Apr 2010 07:06
On Apr 19, 4:18 am, Mok-Kong Shen <mok-kong.s...(a)t-online.de> wrote:
> MK1024 wrote:
> > What would happen if I posted come code samples here or on a non
> > Australian code sharing website?
>
> It seems that even in US the export regulations aren't exercised with
> the same energy by the authorities now as several decades ago. (That's
> maybe there are other problems there that have higher priorities, e.g.
> wars.) If you want to be absolutely safe, post in an internet cafe with
> a pseudonym.
>
> M. K. Shen

Usually that's because that's the law. But why let facts get in the
way.

The USA [like Canada] has very clear exceptions for open source
software. That's why they don't "go after" most people who distribute
crypto software openly. I suspect Australia is similar in this
context though I can't say for sure (our resident Aussie can, Greg
what's the word?).

If you're doing anything proprietary or otherwise closed source you
best get an export license.

Tom
From: unruh on 19 Apr 2010 11:49
On 2010-04-19, Tom St Denis <tom(a)iahu.ca> wrote:
> On Apr 19, 4:18?am, Mok-Kong Shen <mok-kong.s...(a)t-online.de> wrote:
>> MK1024 wrote:
>> > What would happen if I posted come code samples here or on a non
>> > Australian code sharing website?
>>
>> It seems that even in US the export regulations aren't exercised with
>> the same energy by the authorities now as several decades ago. (That's
>> maybe there are other problems there that have higher priorities, e.g.
>> wars.) If you want to be absolutely safe, post in an internet cafe with
>> a pseudonym.
>>
>> M. K. Shen
>
> Usually that's because that's the law. But why let facts get in the
> way.
>
> The USA [like Canada] has very clear exceptions for open source
> software. That's why they don't "go after" most people who distribute
> crypto software openly. I suspect Australia is similar in this
> context though I can't say for sure (our resident Aussie can, Greg
> what's the word?).

Actually, the US never did impliment the software exemption that Canada
and most of the rest of the world did, when they made the laws to backup
the agreement. Australia did. But you need to make sure you comply with
the wording of the law. It generally says that if the product is
commonly available over the counter within the country with no
requirement for any manufacturer's help after purchase, then it is free
for export. Thus you have to establish availability within the country
first (and posting on a web site available both inside and outside the
country makes it dubious, since the export occured concurrent with the
availability inside the country, not afterwards-- ie you really need to
talk with a lawyer.)

The US never implimented that part, although they have a separate piece
of law which says something like that if a piece of software is open
source and is not too strong, it does not need a license to export, but
needs notification of the gov't that export is taking place.


>
> If you're doing anything proprietary or otherwise closed source you
> best get an export license.
>
> Tom
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: why does PKCS#1 use the LCM instead of Euler's totient function?
Next: Asymmetric key length recommendations