From: "Herman Oosthuysen" <Herman@WirelessNetworksInc.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Linux crypto?
Date: Fri, 24 May 2002 12:45:08 -0600 [thread overview]
Message-ID: <000701c20353$215ff1a0$0100007f@localdomain.wni.com.wirelessnetworksinc.com> (raw)
In-Reply-To: <E17BK0J-00073M-00@the-village.bc.nu>
Hmm, here is a brief policy statement on crypto in Canada. I know that this
in not the US, but Canadian and US policies follow each other closely in
military matters, due to various mutual defence agreements. From this, it
is clear that most legal issues regarding the use/development of crypto has
been dropped in North America. This makes sense, since it is far easier to
gather intelligence by other means than by decrypting computer data.
Instead of worrying about US law, you should now worry about
French/Chinese/Russian law instead...
---
SUMMARY OF CANADA'S CRYPTOGRAPHY POLICY
BACKGROUNDER
The Government is implementing a cryptography policy that:
encourages the growth of electronic commerce;
allows Canadian producers to export their products globally within the
framework of international arrangements; and
contains measures to maintain the capability of law enforcement agencies to
ensure public safety.
Support for Electronic Commerce
Canadians are free to develop, import and use whatever cryptography products
they wish.
The Government will not implement mandatory key recovery requirements or
licensing regimes.
The Government encourages industry to establish responsible practices, such
as key recovery techniques for stored data.
The Government will act as a model user of cryptography through the
practices of the Government of Canada Public Key Infrastructure (GOC PKI).
The Government encourages and supports industry-led accreditation of private
sector certification authorities.
Export / International Agreements
Canada will continue to implement cryptography export controls in keeping
with the framework of the international Wassenaar Arrangement.
Canada will take into consideration the export practices of other countries
and the availability of comparable products when rendering export permit
decisions.
The export permit application process will be made more transparent and
procedures will be streamlined to ensure the least regulatory intervention
necessary.
Public Safety
The Government proposes amendments to the Criminal Code and other statutes
as necessary to:
criminalize the wrongful disclosure of keys;
deter the use of encryption in the commission of a crime;
deter the use of cryptography to conceal evidence;
apply existing interception, search and seizure and assistance procedures to
cryptographic situations and circumstances.
---
Cheers,
--
Herman Oosthuysen
Herman@WirelessNetworksInc.com
Suite 300, #3016, 5th Ave NE,
Calgary, Alberta, T2A 6K4, Canada
Phone: (403) 569-5687, Fax: (403) 235-3965
----- Original Message -----
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Thomas 'Dent' Mirlacher <dent@cosy.sbg.ac.at>
Cc: David S. Miller <davem@redhat.com>; <alan@lxorguk.ukuu.org.uk>;
<tori@ringstrom.mine.nu>; <imipak@yahoo.com>; <linux-kernel@vger.kernel.org>
Sent: Friday, May 24, 2002 12:41 PM
Subject: Re: Linux crypto?
> > > They won't let me (or any other US citizen) make any edits to any of
> > > the ipsec sources if it were to be added to the main tree. That's
> > > unacceptable because it means that effectively I cannot maintain the
> > > networking.
> >
> > well the _big_ thing the freeswan people are afraid of, is exactly the
> > crypto laws in the us.
>
> They refuse to have a US citizen working on it. Which is reasonable given
> the historu of US law, but until the US finishes outlawing computers in
> a couple of years that is a problem.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-05-24 18:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 18:03 Myrddin Ambrosius
2002-05-22 18:38 ` Alan Cox
2002-05-23 8:45 ` Trond Myklebust
2002-05-23 21:46 ` Tobias Ringstrom
2002-05-24 14:58 ` Alan Cox
2002-05-24 17:32 ` Thomas 'Dent' Mirlacher
2002-05-24 17:21 ` David S. Miller
2002-05-24 17:42 ` Thomas 'Dent' Mirlacher
2002-05-24 17:31 ` David S. Miller
2002-05-24 17:57 ` Thomas 'Dent' Mirlacher
2002-05-24 19:18 ` Myrddin Ambrosius
2002-05-25 4:01 ` Henrique de Moraes Holschuh
2002-05-24 18:41 ` Alan Cox
2002-05-24 18:30 ` Thomas 'Dent' Mirlacher
2002-05-24 18:55 ` Alan Cox
2002-05-24 18:50 ` Sandy Harris
2002-05-29 0:24 ` Petro
2002-05-24 20:17 ` Myrddin Ambrosius
2002-05-24 21:25 ` Thomas 'Dent' Mirlacher
2002-05-24 18:45 ` Herman Oosthuysen [this message]
2002-05-24 21:49 ` Xavier Bestel
2002-05-24 21:43 ` David S. Miller
2002-05-26 10:06 ` Jakob Østergaard
2002-06-18 15:06 ` Drivers, Hardware, and their relationship to Bagels Myrddin Ambrosius
2002-06-18 15:01 ` Zwane Mwaikambo
2002-06-18 15:26 ` Richard B. Johnson
2002-06-18 18:35 ` Myrddin Ambrosius
2002-06-18 19:13 ` Richard B. Johnson
2002-06-19 2:11 ` Stevie O
2002-06-18 16:01 ` Xavier Bestel
2002-06-18 18:23 ` Myrddin Ambrosius
2002-05-28 18:28 Linux crypto? James Yonan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000701c20353$215ff1a0$0100007f@localdomain.wni.com.wirelessnetworksinc.com' \
--to=herman@wirelessnetworksinc.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®