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:26:00 -0400 [thread overview]
Message-ID: <9ab217670705101626v28598dddh81bbaca29e455455@mail.gmail.com> (raw)
In-Reply-To: <4643A897.2040208@gmail.com>
2007/5/10, don bailey <don.bailey@gmail.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> >> 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.
> >
>
> Right, that's what I understand but I can't *prove* it. Are there places
> online where I can find a verified current status for algorithm
> specific licenses? Like, is there someplace that RSADSI says "yes, we've
> let go of MD5 and RSA for public use."?
>
> Any help or advice is appreciated. I'm a bit lost when it comes to
> legalese.
There is public domain code for MD5 and RSA in any case, and the
patents have expired on them. The USPTO would have more information on
the patents, and I know NIST has information about other ones. AES was
designed to be a fantastic, openly available cryptosystem.
--dho
> Don
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFGQ6iXyWX0NBMJYAcRAgUkAJ9nyFc0cLoN7GgSlxPngE7y55EesgCfaekG
> BoA5nuXlhc8ZFd+dMYyhidk=
> =Ev1I
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2007-05-10 23:26 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
2007-05-10 23:19 ` don bailey
2007-05-10 23:26 ` Devon H. O'Dell [this message]
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=9ab217670705101626v28598dddh81bbaca29e455455@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).