decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Bad Cert for a DIFFERENT Site | 178 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Fake certificates
Authored by: JimDiGriz on Sunday, August 19 2012 @ 11:24 PM EDT
"I believe there is some king of subtle attack happening
with fake certs in the same vein as Stuxnet."

Technically the certificates used by Stuxnet weren't fake, just stolen.

JdG

[ Reply to This | Parent | # ]

Bad Cert for a DIFFERENT Site
Authored by: Anonymous on Monday, August 20 2012 @ 02:57 AM EDT
A couple or three years ago I was getting SSL warnings on a banking site for
some other site. At one point I was seriously wondering if the banking website
had been compromised.

Any number of phone calls and a few emails later it became obvious to me what
had happened. I use a separate account for on-line banking. In response to one
of the CA compromises (I have forgotten details) I had disabled one or more CAs
for that account. The CAs needed for my bank were still enabled. But although
they denied it at first, it turns out the bank had links in their web page to
one of doubleclicks cousins (in a loose sense). I didn't recognize the name
(which I have now forgotten) of the third party site when it threw the SSL
error. It turned out that this third party website was using a CA which I had
disabled, hence the error.

I was none to happy about a trusted site (my bank) pulling in 3rd party websites
after I had authenticated but it was easy enough to use Privoxy to block them
from doing so, so I didn't worry about it.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )