From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] crypto licensing
Date: Thu, 10 May 2007 19:12:34 -0400 [thread overview]
Message-ID: <9ab217670705101612r365df1abw2be7f99c021d1d30@mail.gmail.com> (raw)
In-Reply-To: <4643A4C2.90009@gmail.com>
2007/5/10, don bailey <don.bailey@gmail.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ok, so, after using google for the past hour and a half I've decided I
> suck at using google. So who here can point me to information on
> algorithm specific licenses? i.e. is the license required by rfc1312
> still necessary for an MD5 implementation? What about DES, AES, RSA, ...?
>
> I'm cryptographically challenge(/response)d. Huhuh.
Not sure what you mean. You can freely use MD5, SHA, DES, DES3,
Rijndael (AES), RSA, and even IDEA now (I believe the patent is gone)
without obtaining licenses from any entities.
--dho
> Don
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGQ6RjyWX0NBMJYAcRAiL9AJ0dvyksmupf41n0xNhhUt0h4rDRPwCfXLjo
> L3el440rpZ8XKSsdzosWaEA=
> =sNwi
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2007-05-10 23:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 23:03 don bailey
2007-05-10 23:12 ` Devon H. O'Dell [this message]
2007-05-10 23:19 ` don bailey
2007-05-10 23:26 ` Devon H. O'Dell
2007-05-10 23:31 ` Lyndon Nerenberg
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=9ab217670705101612r365df1abw2be7f99c021d1d30@mail.gmail.com \
--to=devon.odell@gmail.com \
--cc=9fans@cse.psu.edu \
/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).