Phil Zimmerman and PGP

    Date27 Nov 2001
    CategoryCryptography
    3766
    Posted ByAnthony Pell
    InfoSecurityMag talks with the creator of PGP and the motivations behind creating it. "Zimmermann says he was confident that the first release of PGP domestically would be safe from legal restrictions, albeit not unnoticed.. . . InfoSecurityMag talks with the creator of PGP and the motivations behind creating it. "Zimmermann says he was confident that the first release of PGP domestically would be safe from legal restrictions, albeit not unnoticed.

    "I knew it would attract the attention of the government, and they wouldn't like what I did." He certainly didn't think it would result in a criminal investigation.

    Though unworried about PGP 1.0, Zimmermann knew that he very likely stepped over the line with PGP 2.0, released in September 1992. "I was quite worried," he said. "I felt sure I was going to prison because of that."

    Zimmermann says his role in the development of PGP 2.0 was "more clearly violations of the Arms Export Control Act, which forbade technical assistance in the development of encryption software overseas."

    You are not authorised to post comments.

    LinuxSecurity Poll

    Do you reuse passwords across multiple accounts?

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 2 answer(s).
    /component/communitypolls/?task=poll.vote
    13
    radio
    [{"id":"55","title":"Yes","votes":"0","type":"x","order":"1","pct":0,"resources":[]},{"id":"56","title":"No","votes":"0","type":"x","order":"2","pct":0,"resources":[]}]["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"]["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"]350
    bottom200

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.