From: Wes Hardaker <wes@hardakers.net>
Subject: Re: Crypto problems again
Date: Mon, 02 Feb 2004 15:07:35 -0800 [thread overview]
Message-ID: <sdisiphyh4.fsf@wes.hardakers.net> (raw)
In-Reply-To: <ilu7jz5wbvr.fsf@latte.josefsson.org> (Simon Josefsson's message of "Mon, 02 Feb 2004 19:54:16 +0100")
>>>>> On Mon, 02 Feb 2004 19:54:16 +0100, Simon Josefsson <jas@extundo.com> said:
Simon> What's the definition of crypto code?
<IANL>
I think that also depends on the era of the regulation being
considered. A number of years ago, it included wrappers or even
comments like "put encryption calls here". Now, however, I believe at
least with the U.S. that it actually means implementation of the
actual cryptography algorithm itself. I'd ask RMS what he actually
means by it since he probably cares.
</IANL>
--
"In the bathtub of history the truth is harder to hold than the soap,
and much more difficult to find." -- Terry Pratchett
next prev parent reply other threads:[~2004-02-02 23:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 18:02 Lars Magne Ingebrigtsen
2004-02-02 18:54 ` Simon Josefsson
2004-02-02 23:07 ` Wes Hardaker [this message]
2004-02-03 9:12 ` Lars Magne Ingebrigtsen
2004-02-05 17:25 ` Lars Magne Ingebrigtsen
2004-02-05 17:45 ` Wes Hardaker
2004-02-05 20:09 ` Ted Zlatanov
2004-02-05 20:53 ` Simon Josefsson
2004-02-05 21:37 ` Wes Hardaker
2004-02-06 0:53 ` Jesper Harder
2004-02-05 21:29 ` Josh Huber
2004-02-05 21:38 ` Wes Hardaker
2004-02-05 22:36 ` Simon Josefsson
2004-02-05 23:09 ` Wes Hardaker
2004-02-02 19:49 ` crypto in netrc.el and gnus-encrypt.el (was: Crypto problems again) Ted Zlatanov
2004-02-02 23:05 ` Crypto problems again Wes Hardaker
2004-02-05 21:22 ` Jesper Harder
2004-02-05 21:39 ` Wes Hardaker
2004-02-05 22:18 ` Jesper Harder
2004-02-05 23:11 ` Wes Hardaker
2004-02-06 0:24 ` Jesper Harder
2004-02-06 1:47 ` Jesper Harder
2004-02-06 15:42 ` Wes Hardaker
2004-02-06 23:58 ` Jesper Harder
2004-02-09 21:03 ` Ted Zlatanov
2004-02-13 10:17 ` Kai Grossjohann
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=sdisiphyh4.fsf@wes.hardakers.net \
--to=wes@hardakers.net \
/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;
as well as URLs for NNTP newsgroup(s).