Skip to main content

PyCon 2011: Interview with Geremy Condra

by Brian Curtin

Putting together two talks for a conference like PyCon is certainly no easy task, nor is it easy to pile on a lightning talk and the organization of a Birds of a Feather (BoF) session or two. That’s Geremy Condra’s plan for March 11 through March 13 at PyCon.

The security researcher from the University of Washington heads to Atlanta for a second time, looking forward to an even better conference compared to last year’s blast. “My favorite part is definitely the degree of accessibility the conference offers - between the lightning talks, poster sessions, BoF sessions, etc.,” he says.

Although the PyCon talk schedule may have you believe the day is over by dinner time, that’s only half of it. As Geremy mentions, “PyCon's enormous strength is in its ability to connect diverse parts of the Python community.” One of the ways this happens is through the many Open Space and BoF sessions in the evening. Add to that all of the thrown together hallway events, ad hoc sprints, games, and much more, and it quickly becomes a 24-hour gathering.

During the day you’ll have a chance to hear Geremy’s take on TUF, a library for secure software updates in Python. Asked what common security issues developers are facing, Geremy answers, “Most devs make their security mistakes when they try to figure out who the adversary is - misplacing trust, assuming that adversaries are weaker (or just differently capable) than they actually are, that sort of thing. This seems to happen a lot with client side code, especially when it comes to downloading files.” Rollback and mix-and-match attacks like this are some of the topics of this talk, including a demonstration of the vulnerability followed by what TUF can do to protect against it.

“The other big issue is with trusting untrustworthy code,” he claims. “Thinking that
urllib will automatically check certs for you, that your cryptographic routines are secure because you can't figure out what they do,” are some of these issues. Fortunately, these are more easily fixed than others, and also make up a lot of what he plans to speak about at PyCon.

His second talk, Through the Side Channel: Timing and Implementation Attacks in Python dives into some of the great things about Python that can also introduce security risks. Part of the talk is to raise awareness using some Python projects that are in wide use. Additionally, he plans to educate attendees on the methods of defense, leaving them with a better sense of what’s out there and giving them a better chance at spotting and correcting the flaws that leave one’s project open.

I had a chance to ask Geremy about some of his work and his use of Python, and found that almost everything he does uses it. “I build simulations using Fabric, display data using Matplotlib, use Sage to model problems, and of course implement solutions in Python where possible,” he says, also mentioning occasional Haskell use.

Additionally, he’s the creator of several open tools that he uses on the job. The Graphine library, an easy to use graph library for Python 3, is one of his projects. He’s also responsible for EVPy, a set of bindings for OpenSSL’s EVP interface, supporting both Python 2 and 3.

We look forward to the security knowledge Geremy brings to this year’s conference, along with his upcoming book titled “Cryptography and Network Security with Python 3.” If you haven’t bought your tickets yet, get them before all 1,500 are sold out!

Comments

Popular posts from this blog

Hatchery Program Returns for 2019

PyCon is known around the world as the Python community’s premier event, attracting people from 39 countries. Outside of the main track of talks, PyCon is home to a growing number of events such as Young Coders, the Education Summit, Language Summit, Poster Session, and most recently the PyCon Charlas. The conference strives to be globally representative by promoting diversity and inclusion through these additional events and outreach programs. Our community works to approach these goals year on year. While we regularly receive requests to add events to PyCon, we have not had an established process for accepting and evaluating the community’s suggestions. By introducing the PyCon Hatchery Program in 2018, we took an initial step to introduce a long term process for evolving PyCon. What is our goal?We want to support our community and enable them to add events to PyCon that are important to our community. The long-term goals of this program are to support and grow sustainable programs th…

Pycon 2019 Call for Proposals is Open!

The time is upon us again! PyCon 2019’s Call for Proposals has officially opened for talks, tutorials, posters, education summit presentations, as well as the hatchery program PyCon Charlas. PyCon is made by you, so we need you to share what you’re working on, how you’re working on it, what you’ve learned, what you’re learning, and so much more.

Please make note of important deadlines for submissions:
Tutorial proposals are due November 26, 2018.Talk, Charlas, Poster, and Education Summit proposals are due January 3, 2019.
Who should write a proposal? Everyone! If you’re reading this post, you should write a proposal. PyCon is about uniting and building the Python community, and we won’t advance as an open community if we’re not open with each other about what we’ve learned throughout our time in it. It isn’t about being the smartest one in the room, so we don’t just pick all of the expert talks. It’s about helping everyone move together. “A rising tide lifts all boats,” if you will.

We…

PyCon 2018 Code of Conduct Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. For 2018 the Code of Conduct underwent an extensive overhaul, our procedures for reporting and responding to incidents were improved, and our on-site methods were improved. You can read more about the updates for 2018 here. Cumulatively these changes were meant to improve the safety, welcoming nature, and overall inclusivity of PyCon. Based on initial responses, feedback, and incidents reported this year we feel that we made progress on those goals. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents. With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon…