Just back from an excellent (5th) edition of the Freedom to Connect Conference.
I want to tell you about another event next week our CTO will be speaking at descibed below, but first I owe a quick comment about F2C, as the Producer graciously gave us the podium to speak about the OSDV Project, which led to 3 hours of excellent conversation at an evening reception.
I must say, I love this gathering of Netheads. Some of the smartest people involved with the formative of years of packet switching networks and what we know today as the (commercial) Internet. And David Isenberg, Conference Producer, Bell Labs Alumni, and author of the Rise of the Stupid Network (which you ought to read if you haven’t) brings together thought leaders on all sides of the issues of the Internet and its future. The event is also supported by some important organizations relevant to the Internet and its use in this age of digital democracy including the Mozilla Foundation, Google, the Sunlight Foundation, the Berkman Center for Internet & Society, and OneWebDay to name a few. But others underwrite the event of equal note including NATOA, BT and Verizon, illustrating that even the Telcos see value in this NetHead gathering.
OK, back to the point of this post: an event that our CTO is speaking at next Tuesday.
OSDV CTO to Deliver Talk on e-Voting Security 08.April at Stanford
Next Tuesday afternoon (08.April), OSDV CTO John Sebes will lead a conversation at the regular Stanford Security Seminar hosted by the Security Lab about e-voting security, an often misunderstood issue.
Considerable attention has been paid to security flaws in current
electronic voting systems, begging the question, what does
"secure" mean for voting systems? John will lead a discussion on this
question from the viewpoints of:
– A blank slate — that is, new systems rather than security
retrofits of existing systems; and
– The fundamental process requirements — such that trust in voting
systems supports public confidence in election results.
If you’re around Stanford next Tue at 4:30PM (contact the CS Department for exact location and see this map), drop in as its open to the public (you might let the coordinator at the Security Lab know you’re coming for headcount purposes).