« More Thoughts on EFF's Filesharing Plan |
Main
| First Broadcatching App Available! (And Related News) »
March 12, 2004
Ricin Patent Removed from PTO Database?
Posted by Ernest Miller
Security expert Bruce Schneier has written to blogger and Mercury News technology columnist Dan Gillmor about a patent that seems to be missing from the online US database ('Dangerous' Patent Removed from Database?). He quotes Schneier:
In October 1962, the U.S. Patent Office granted patent 3,060,165 regarding the use of ricin as a biological weapon. Published patents are, of course, publicly available. That's the point.
All US patents are available from the USPTO website: "full-text since 1976, full-page images since 1790." However, for some reason, this particular patent is no longer in the database:
Clicking on "Images" only produces a "Patent not found" image.
The patent is still available in foreign databases, so it seems like a rather futile exercise if the removal was due to concerns about knowledge of WMDs.
This hiding of public information is just the sort of thing we need to fight against. If the bad guys can get a copy of the patent without any trouble, how is this helping?
You can read the three-page patent here: Ricin Patent [PDF].
I wonder if the missing patent has anything to do with a sensationalistic investigative report from NY television station WABC in February of last year that chided the Patent Office for making the patent available (Investigators: Anyone Can Get The Recipe For A Bio-Terror Weapon More Deadly Than Cyanide):
The day before the Secretary of State warned the world about the threat of terrorist ricin attack, I was undercover at the nation's US Patent Office. There, a simple word search on its public computer yielded meticulously detailed instructions on how to make the purest, deadliest form of the poison.
Yeah, like terrorists are going to go to the US Patent Office to do research on biological weapons.
The concern is so great that Ricin will get into the wrong hands the FBI has issued an alert to all law enforcement agencies. Yet just a few miles from the bureau headquarters in the nation's capitol, the US Patent Office allows anyone to get a copy of the Ricin recipe for just 25 cents a page.
Ooookaaay. This is a threat vector we should be worried about because? Anyway, all this sensationalism leads to bogus calls for "increased security."
New York's senior senator says in the interest of national security, the US Army patent needs to be removed from the public domain immediately.
Senator Charles Schumer, New York (D): "For the FBI to be putting out an alert against Ricin and then for the Commerce Department to have this on their computer so anybody can walk in and figure out how to make it, makes the average citizen scratch their head and think, 'What the heck is going on down there in Washington?'
Rest assured Senator, the lack of the patent in the US database means that terrorists will never be able to figure out how to make ricin because even web-savvy bloggers can't get the information very easily .... ooops. Never mind.
Comments (3)
+ TrackBacks (0) | Category: Civil Liberties | Patent
- RELATED ENTRIES
- Kitchen Academy - Course II - Day 23
- Kitchen Academy - Course II - Day 22
- Kitchen Academy - Course II - Day 21
- Kitchen Academy - The Hollywood Cookbook and Guest Chef Michael Montilla - March 18th
- Kitchen Academy - Course II - Day 20
- Kitchen Academy - Course II - Day 19
- Kitchen Academy - Course II - Day 18
- Salsa Verde
1. Rumor on March 12, 2004 06:42 PM writes...
Interesting. When I scroll down past the first page of the patent document (the flowchart) I get a "file does not exist" message and blank screen in my browser. However, the pdf still exists in full format in my local cache. Even when I browser the file from my HDD, the error message comes up, but I can still view whole file. Has someone tampered with the document?
Permalink to Comment2. Ernest Miller on March 12, 2004 07:19 PM writes...
It appears fine in my version of Adobe Reader ... anyone else have any idea why Rumor might be getting this problem?
Permalink to Comment3. Karl-Friedrich Lenz on March 13, 2004 10:58 AM writes...
I had exactly the same thing happen.
Maybe this is some half-baked measure that your hosting company has implemented without informing you.
Permalink to Comment