<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Yeah, we can get an SSL certificate from a vendor that the browsers
support, rather than going third party. Until we do, every user in
every browser is going to get a warning and have to override security
settings to add the cert. I know a bunch of people, mostly my coworkers
and security people, that refuse to add third party certs to their
stores so they just won't look at our site.<br>
<br>
On 3/21/09 10:30 AM, Mitch Altman wrote:
<blockquote cite="mid:SNT102-W31B5B5007F8E8A1FB7511DB8940@phx.gbl"
type="cite">
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>A bunch of people have told me about being somewhat freaked
out by the dire warning given them by their web browser saying that
they are under great danger if they proceed to look at our Noisebridge
website.<br>
<br>
<br>
Is there anything that someone can do to fix this problem? Like,
fast? I know there's a lot of philosophical questions about supporting
The Man, and all (and I would love to see a real solution to that), but
how about if we fix it fast and then come up with a better way in the
year we have to discuss it?<br>
<br>
<br>
Keeping our site looking "dangerous" to those who don't understand what
security certificates are about makes us (and perhaps hackers in
general) look pretty bad to the world.<br>
<br>
<br>
Someone I met at ETech (Dylan Tweney, a really cool person, and senior
editor of Wired.com) is doing a story on Noisebridge and other hacker
spaces. When that story goes out, there's gonna be a ton-'o people
checking out our website.<br>
<br>
<br>
Mitch. <br>
</blockquote>
<br>
</body>
</html>