From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] crypto licensing
Date: Thu, 10 May 2007 16:31:43 -0700 [thread overview]
Message-ID: <20070510162441.H83614@orthanc.ca> (raw)
In-Reply-To: <4643A897.2040208@gmail.com>
> 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."?
RSA was restricted by patent, since expired. The top item when I Google
"rsa patent" is a CNN story about RSA corp releasing the patent.
Similarly, a Google search on "cryptography idea patent" returns a first
hit on Wikipedia that lists the US patent number (5,214,703) along with a
note that the patents expire in the 2010-11 time-frame.
You get the idea ... You need to track down the relevant patent numbers,
then see when they expire(d).
--lyndon
I think 3B2 code deserves its own place in hell. Poring over the
ESS#5 code, someone found that there were lots of strcmp(p, "f(")
== 0 checks (I may have gotten the exact string wrong but it's
close). It took us a while to figure out why. Apparently, location
0 on the 3b had the 3 bytes 'f' '(' '\0', someone noticed that when
programs blew up they were pointing to "f(", and the worlds most
amazing kludge for detecting nil pointers was born.
-- Dave Presotto
prev parent reply other threads:[~2007-05-10 23:31 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
2007-05-10 23:31 ` Lyndon Nerenberg [this message]
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=20070510162441.H83614@orthanc.ca \
--to=lyndon@orthanc.ca \
--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).