<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">

<head>

<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:Wingdings;
        panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle23
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle24
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
 /* List Definitions */
 @list l0
        {mso-list-id:241185815;
        mso-list-template-ids:780405914;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1
        {mso-list-id:450561522;
        mso-list-template-ids:1943965626;}
@list l1:level1
        {mso-level-number-format:bullet;
        mso-level-text:\F0B7;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1:level2
        {mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level3
        {mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level4
        {mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level5
        {mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level6
        {mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level7
        {mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level8
        {mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level9
        {mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2
        {mso-list-id:1651056073;
        mso-list-type:hybrid;
        mso-list-template-ids:-651121980 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level2
        {mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level3
        {mso-level-tab-stop:1.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level4
        {mso-level-tab-stop:2.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level5
        {mso-level-tab-stop:2.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level6
        {mso-level-tab-stop:3.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level7
        {mso-level-tab-stop:3.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level8
        {mso-level-tab-stop:4.0in;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l2:level9
        {mso-level-tab-stop:4.5in;
        mso-level-number-position:left;
        text-indent:-.25in;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple>

<div class=WordSection1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>&gt; </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>For example, why would  Hotmail, Gmail, etc implement
transport-level encryption (SMTP over TLS) which would increase CPU utilization
of their infrastructure that would neither be visible to the user, the user
would not pay for it, nor would it drive any additional advertising revenue.
Altruisms are nice, but the marketplace is primarily driven by the ability to
pay&#8230;<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>By the same token, Google is realizing the email based transport
encryption is critical to the success of their company. Perhaps it had
something to do with so many gmail accounts getting compromised at coffee
shops. </span><span style='font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>
SMTP/TLS is now standard when you set up Gmail for thick clients. And Gmail has
an option that forces all GMAIL communication to over HTTPS, AND Google has a
reasonable rating at SSLLabs for HTTPS configuration. It&#8217;s a step in the right
direction. You can even go this route </span><a
href="https://addons.mozilla.org/en-US/firefox/addon/592/">https://addons.mozilla.org/en-US/firefox/addon/592/</a>
<span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>if
you want real enterprise grade email security via gmail.</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>- Jim<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
owasp-leaders-bounces@lists.owasp.org
[mailto:owasp-leaders-bounces@lists.owasp.org] <b>On Behalf Of </b>James
McGovern<br>
<b>Sent:</b> Saturday, October 16, 2010 2:19 AM<br>
<b>To:</b> owasp-leaders@lists.owasp.orged<br>
<b>Subject:</b> Re: [Owasp-leaders] Is it ok to share the PGP Keys and keep
thePassPhrase private?<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>May I ask a few &#8220;refining&#8221; questions of Dinis?<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Is the requirement to externalize the private key used in
encryption/decryption operations so that it is NOT embedded within the
application? If so, since I saw that O2 was mentioned which hints that you are
probably using C# which probably hints that you are running MS Windows (will
ignore Mono for now) that you could have a Passphrase unlock either the Windows
keystore that stores the private key or a custom implementation of your own
keystore.<o:p></o:p></span></p>

<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l2 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>To make passphrase strength more strong would require adding
some &#8220;salt&#8221;. Again, if you are using C# and Windows, there is the ability to
hide the value used by going after things that are local to the machine such as
a MAC address, GUID or arbitrary value in the registry. I think the key to this
discussion may be less about the &#8220;encryption&#8221; and more about &#8220;digest&#8221; (???)
Your passphrase is less likely to be compromised if the salt varies based on
installation.<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>As far as email encryption having gone nowhere, it is important
to understand both successes/failures in this space. First and foremost, I can
say that there was a loudmouth Architect (and Hartford OWASP chapter leader)
who evangelized the need for every insurance agent/carrier to install SSL
certificates (could be self-signed or VeriSign) so that the industry-at-large could
comply with Mass (the state) regulations. Carriers who have enterprise-class
products such as Exchange, IronPort, etc were able to implement this very
easily and cheaply. <o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The challenge of email encryption is fast becoming more of a
&#8220;consumer&#8221; problem. For example, why would Hotmail, Gmail, etc implement
transport-level encryption (SMTP over TLS) which would increase CPU utilization
of their infrastructure that would neither be visible to the user, the user
would not pay for it, nor would it drive any additional advertising revenue.
Altruisms are nice, but the marketplace is primarily driven by the ability to
pay&#8230;<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:gray'>James McGovern<br>
</span></b><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:gray'>Insurance SBU <o:p></o:p></span></p>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:gray'>Virtusa </span></b><b><span style='font-size:10.0pt;font-family:
"Calibri","sans-serif";color:#7F7F7F'>Corporation</span></b><b><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:gray'><o:p></o:p></span></b></p>

<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:gray'>100 Northfield Drive, Suite 305 | Windsor, CT | 06095<o:p></o:p></span></p>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#7F7F7F'>Phone:&nbsp; </span></b><span style='font-size:10.0pt;
font-family:"Calibri","sans-serif";color:gray'>860 688 9900</span><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#7F7F7F'> <b>Ext:&nbsp;
</b></span><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:gray'>1037</span><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:#7F7F7F'> | <b>Facsimile:&nbsp; </b></span><span style='font-size:10.0pt;
font-family:"Calibri","sans-serif";color:gray'>860 688 2890</span><span
style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#7F7F7F'>
&nbsp;</span><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";
color:gray'><o:p></o:p></span></p>

<p class=MsoNormal><a href="http://www.virtusa.com/"><span style='font-size:
10.0pt;font-family:"Calibri","sans-serif";color:#7F7F7F;text-decoration:none'><img
border=0 width=81 height=21 id="Picture_x0020_52"
src="cid:image001.jpg@01CB6DED.1619FDF0"
alt="cid:image011.jpg@01CB08A4.F95CFA30"></span></a><span style='font-size:
10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><a
href="http://www.virtusa.com/blog/"><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#1F497D;text-decoration:none'><img border=0
width=22 height=22 id="Picture_x0020_53"
src="cid:image002.gif@01CB6DED.1619FDF0"
alt="cid:image012.gif@01CB08A4.F95CFA30"></span></a><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><a
href="https://twitter.com/VirtusaCorp" target="_blank"><span style='text-decoration:
none'><img border=0 width=22 height=22 id="Picture_x0020_54"
src="cid:image003.gif@01CB6DED.1619FDF0"
alt="cid:image004.gif@01CB08A4.F95CFA30"></span></a><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><a
href="http://www.linkedin.com/companies/virtusa" target="_blank"><span
style='text-decoration:none'><img border=0 width=22 height=22
id="Picture_x0020_55" src="cid:image004.gif@01CB6DED.1619FDF0"
alt="cid:image005.gif@01CB08A4.F95CFA30"></span></a><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>&nbsp;</span><a
href="http://www.facebook.com/VirtusaCorp" target="_blank"><span
style='text-decoration:none'><img border=0 width=22 height=22
id="Picture_x0020_56" src="cid:image005.gif@01CB6DED.1619FDF0"
alt="cid:image006.gif@01CB08A4.F95CFA30"></span></a><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
owasp-leaders-bounces@lists.owasp.org
[mailto:owasp-leaders-bounces@lists.owasp.org] <b>On Behalf Of </b>Matthew
Chalmers<br>
<b>Sent:</b> Friday, October 15, 2010 3:56 PM<br>
<b>To:</b> owasp-leaders@lists.owasp.org<br>
<b>Subject:</b> Re: [Owasp-leaders] Is it ok to share the PGP Keys and keep
thePassPhrase private?<o:p></o:p></span></p>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<div>

<div>

<p class=MsoNormal>Let's make the assumption that Dinis has a business
requirement to use the proposed (compromised) design. We live in the real
world, not a perfect world where we can always pick perfect solutions. ID-based
encryption relies on a trusted third party, which is not part of Dinis's
design, but I don't like the looks of this &quot;O2&quot; tool (which I've
never heard of) because it shows passphrases in the clear and has a checkbox
for &quot;store in config file&quot; which scares me. But that's besides the
point.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<p class=MsoNormal>Dinis basically wants to be able to inform his customer how
secure the proposed design will be (i.e. how long should a private key with a
passphrase of a given length/composition be expected to survive unprotected).
That is, how much compromise is involved.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<p class=MsoNormal>Unfortunately we aren't told how the private key will be
exported and &quot;published&quot; (and I don't really have time to fully
analyze the O2 tool). I believe PGP's default is to export in PKCS#12 using
PKCS#5 password-based encryption. You can see details of how the key is derived
from the password and what algorithms are used here:&nbsp;<a
href="http://www.ietf.org/rfc/rfc2898.txt" target="_blank">http://www.ietf.org/rfc/rfc2898.txt</a>.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<p class=MsoNormal>Suffice it to say, there are a lot of ways an application
can screw up implementing PKCS &quot;standards&quot; due to all the options and
versions. in the link above it says DES or RC2 are used with 64-bit keys. You
can look up on NIST's website how long single DES (I'm not sure if they've
published info on RC2) is expected to last--it isn't very long at all. It's
basically compromised the moment you use it.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<p class=MsoNormal>So if I have all my facts and assumptions straight, it
almost doesn't matter how long your passphrase is if the private key is
published in PKCS#12 because it's encrypted using a weak algorithm which is
faster to break than an exhaustive password brute-force attempt.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<p class=MsoNormal>Let's assume I'm incorrect and your tool (O2 or some version
of PGP) will export in a format that has a strongly encrypted private key. Now
you're talking about brute forcing the password.&nbsp;See&nbsp;<a
href="http://en.wikipedia.org/wiki/Password_strength#Entropy.2C_or_bit_strength"
target="_blank">http://en.wikipedia.org/wiki/Password_strength#Entropy.2C_or_bit_strength</a>&nbsp;for
some info on&nbsp;bits of entropy for given password lengths and
compositions--assuming they are randomly generated. Let's assume for the sake
of argument that the table is correct, and you use a truly randomly generated
passphrase. In order to have longevity on the order of years, you should try to
use a 128-bit equivalent passphrase. According to the table that would be 20
printable ASCII characters (x21 to 0x7E). There's almost no chance a human will
be able to memorize it, however, so your security goes down in other ways right
there because the passphrase may be compromised without brute forcing it.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<p class=MsoNormal>There are so many assumptions being made here, and by all
members of this discussion including Dinis, it's ridiculous. Encryption is very
hard to get right and very easy to get wrong, and having &quot;more encryption
out there&quot; doesn't do anybody any good. If you're talking about making
encryption more accessible to the laymen, you need to make tools that are
easier to use but publicly vetted by experts, then you have to get market
penetration--which is something no tool has done yet. Even with the marketing
power of Symantec PGP has gone nowhere. Even with S/MIME being an open standard
for email, encrypted email has gone nowhere. Sad but true.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<p class=MsoNormal>So after all this, Dinis still doesn't have any hard data to
support how long a private key protected by a passphrase will last if not locked
down as intended. And even if someone could point to, or perform, research on
how long it takes a given CPU to brute force the passphrase of a private key in
a given piece of interactive software or an exported format, we'd still have to
threat map it because we don't know if Dinis is up against foreign governments
or 13-year-olds with lots of free time. This is a pervasive problem with risk
analysis--when it's objective, it's so easy anybody could do it, but when it's
subjective (which it usually is), it's so hard anybody might as well do it. So
it comes down to educated guesses, which we can't even make without very, very
precise constraints around the problem, which Dinis hasn't provided (e.g., what
implementation of PGP? What version thereof? What key export method? What types
of characters are drawn from to make the passphrase? How is it generated--by
human or by RNG? How, exactly, will the key be &quot;published&quot;? What/who
are the threats and their sophistication? What other business requirements are there
that limit our solution?)<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=MsoNormal>On Thu, Oct 14, 2010 at 1:26 PM, James McGovern &lt;<a
href="mailto:JMcGovern@virtusa.com" target="_blank">JMcGovern@virtusa.com</a>&gt;
wrote:<o:p></o:p></p>

<div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>If you are married to the scheme of
sharing keys but not necessarily the approach (e.g. PGP), then maybe there is
an opportunity for you to noodle usage of the Identity Based Encryption work
out of Stanford (with patterns from Voltage). The idea is that a key doesn&#8217;t
have to be something based on complex algorithms such as factoring of large
prime numbers but could be something as simple as using an email address.&nbsp;
Google for &#8216;identity based encryption&#8217; for more information.</span><o:p></o:p></p>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt;color:gray'>James McGovern<br>
</span></b><span style='font-size:10.0pt;color:gray'>Insurance SBU </span><o:p></o:p></p>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt;color:gray'>Virtusa </span></b><b><span
style='font-size:10.0pt;color:#7F7F7F'>Corporation</span></b><o:p></o:p></p>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;color:gray'>100 Northfield Drive, Suite 305 | Windsor,
CT | 06095</span><o:p></o:p></p>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt;color:#7F7F7F'>Phone:&nbsp; </span></b><span
style='font-size:10.0pt;color:gray'>860 688 9900</span><span style='font-size:
10.0pt;color:#7F7F7F'> <b>Ext:&nbsp; </b></span><span style='font-size:10.0pt;
color:gray'>1037</span><span style='font-size:10.0pt;color:#7F7F7F'> | <b>Facsimile:&nbsp;
</b></span><span style='font-size:10.0pt;color:gray'>860 688 2890</span><span
style='font-size:10.0pt;color:#7F7F7F'> &nbsp;</span><o:p></o:p></p>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><a
href="http://www.virtusa.com/" target="_blank"><b><span style='font-size:10.0pt;
color:#7F7F7F;text-decoration:none'>Error! Filename not specified.</span></b></a><span
style='font-size:10.0pt;color:#1F497D'>&nbsp;</span><a
href="http://www.virtusa.com/blog/" target="_blank"><b><span style='font-size:
11.0pt;color:#1F497D;text-decoration:none'>Error! Filename not specified.</span></b></a><span
style='font-size:11.0pt;color:#1F497D'> </span><a
href="https://twitter.com/VirtusaCorp" target="_blank"><b><span
style='text-decoration:none'>Error! Filename not specified.</span></b></a><span
style='font-size:11.0pt;color:#1F497D'>&nbsp;</span><a
href="http://www.linkedin.com/companies/virtusa" target="_blank"><b><span
style='text-decoration:none'>Error! Filename not specified.</span></b></a><span
style='font-size:11.0pt;color:#1F497D'>&nbsp;</span><a
href="http://www.facebook.com/VirtusaCorp" target="_blank"><b><span
style='text-decoration:none'>Error! Filename not specified.</span></b></a><o:p></o:p></p>

</div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>&nbsp;</span><o:p></o:p></p>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> <a
href="mailto:owasp-leaders-bounces@lists.owasp.org" target="_blank">owasp-leaders-bounces@lists.owasp.org</a>
[mailto:<a href="mailto:owasp-leaders-bounces@lists.owasp.org" target="_blank">owasp-leaders-bounces@lists.owasp.org</a>]
<b>On Behalf Of </b>Carlos Serrão<br>
<b>Sent:</b> Thursday, October 14, 2010 11:35 AM<br>
<b>To:</b> <a href="mailto:owasp-leaders@lists.owasp.org" target="_blank">owasp-leaders@lists.owasp.org</a><br>
<b>Subject:</b> Re: [Owasp-leaders] Is it ok to share the PGP Keys and keep
thePassPhrase private?</span><o:p></o:p></p>

</div>

</div>

<div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Dinis,<o:p></o:p></p>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I'm
not a crypto expert, but on any public-key based crypto system, the private key
is supposed to be always private - even if the private key is protected by a
passphrase.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>It's
like using a strong security measure and then use a weaker one to protect the
system. It doesn't make any sense.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>You
have clever ways to subvert the passphrase without using a brute force attack:<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>-
dictionary attacks<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>-
social engineering<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>-
shoulder surfing<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>-
others.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>So,
in my opinion this is a bad idea.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Best
regards.<o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p>

<div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On
2010/10/14, at 10:38, dinis cruz wrote:<o:p></o:p></p>

</div>

<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p>

<p>Here is a question to the Crypto experts (which I'm not).<o:p></o:p></p>

<p>From a security point of view, is it ok if I publish both Public and Private
PGP Keys but keep the PassPhrase secret?<o:p></o:p></p>

<p>My assumption is that: <b>&quot;as long as the PassPhrase is strong enough,
it would be not practical to brute force it (even if the attacker knows the
Private Key)&quot;</b>. In fact, should the question be: <b>&quot;How big does
the PassPhrase be in 2010/2011 time frame for it to be secure?&quot;</b><o:p></o:p></p>

<p>&nbsp;To see this in practice check out the latest script/tool that I just
added to the <a href="http://o2platform.com/wiki/Download" target="_blank">OWASP
O2 Platform</a> which dramatically simplifies the process of using PGP
(creating keys, encrypting/decrypting text and encrypting/decrypting files):<o:p></o:p></p>

<ul type=disc>
 <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l1 level1 lfo5'>blog post: <a
     href="http://diniscruz.blogspot.com/2010/10/tool-using-openpgp-to-encrypt-or.html"
     target="_blank">http://diniscruz.blogspot.com/2010/10/tool-using-openpgp-to-encrypt-or.html</a>
     <o:p></o:p></li>
 <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l1 level1 lfo5'>Wiki page <a
     href="http://www.o2platform.com/wiki/O2_Script/Tool_-_Using_OpenPgp_to_Encrypt_or_Decrypt.h2"
     target="_blank">http://www.o2platform.com/wiki/O2_Script/Tool_-_Using_OpenPgp_to_Encrypt_or_Decrypt.h2</a>
     <o:p></o:p></li>
 <li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
     mso-list:l1 level1 lfo5'>YouTube Video <a
     href="http://www.youtube.com/watch?v=_Cd8AfZyWMs" target="_blank">http://www.youtube.com/watch?v=_Cd8AfZyWMs</a>
     <o:p></o:p></li>
</ul>

<p>As you can see, this O2 tool will really enable this workflow (sending the
both Public and Private Keys to the client in a non-encrypted zip and then
sending the PassPhrase in an offline/out-of-band method), so I'm really trying
to figure out if this is a good idea :)<o:p></o:p></p>

<p>Finally, for the really hard-core crypto guys, can you take a look at how I
implemented the BouncyCastle Crypto APIs to make sure I did it correctly: <a
href="http://code.google.com/p/o2platform/source/browse/trunk/O2_Scripts/APIs/OpenPgp/API_OpenPgp.cs"
target="_blank">http://code.google.com/p/o2platform/source/browse/trunk/O2_Scripts/APIs/OpenPgp/API_OpenPgp.cs</a><o:p></o:p></p>

<p>Thanks <o:p></o:p></p>

<p>Dinis Cruz<o:p></o:p></p>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>_______________________________________________<br>
OWASP-Leaders mailing list<br>
<a href="mailto:OWASP-Leaders@lists.owasp.org" target="_blank">OWASP-Leaders@lists.owasp.org</a><br>
<a href="https://lists.owasp.org/mailman/listinfo/owasp-leaders" target="_blank">https://lists.owasp.org/mailman/listinfo/owasp-leaders</a><o:p></o:p></p>

</div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p>

<div>

<div>

<div>

<div>

<div>

<div>

<div>

<div>

<div>

<div>

<div>

<div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:13.5pt;color:black'>--</span><o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.5pt;color:black'>Carlos Serrão</span><o:p></o:p></p>

</div>

<div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:9.0pt;color:black'>ISCTE-IUL/ISTA/DCTI
|&nbsp;ADETTI-IUL/NetMuST | PT.OWASP</span><o:p></o:p></p>

</div>

</div>

</div>

</div>

</div>

</div>

</div>

</div>

</div>

</div>

</div>

</div>

</div>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p></o:p></p>

</div>

</div>

</div>

</div>

</div>

<table class=MsoNormalTable border=0 cellpadding=0>
 <tr>
  <td style='background:white;padding:.75pt .75pt .75pt .75pt'><pre><span
  style='color:black'>Virtusa was recently ranked and featured in 2010 Global Services 100, IAOP's 2010 Global Outsourcing 100 sub-list, 2009 Deloitte Technology Fast 500 and 2009 Dataquest-IDC Best Employers Survey among others.<o:p></o:p></span></pre><pre><span
  style='color:black'><o:p>&nbsp;</o:p></span></pre><pre><span
  style='color:black'>---------------------------------------------------------------------------------------------<o:p></o:p></span></pre><pre><span
  style='color:black'><o:p>&nbsp;</o:p></span></pre><pre><span
  style='color:black'>This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is intended for the addressee only. Any unauthorized disclosure, use, dissemination, copying, or distribution of this message or any of its attachments or the information contained in this e-mail, or the taking of any action based on it, is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail and delete this message.<o:p></o:p></span></pre><pre><span
  style='color:black'><o:p>&nbsp;</o:p></span></pre><pre><span
  style='color:black'>---------------------------------------------------------------------------------------------<o:p></o:p></span></pre></td>
 </tr>
</table>

<p class=MsoNormal style='margin-bottom:12.0pt'><br>
_______________________________________________<br>
OWASP-Leaders mailing list<br>
<a href="mailto:OWASP-Leaders@lists.owasp.org" target="_blank">OWASP-Leaders@lists.owasp.org</a><br>
<a href="https://lists.owasp.org/mailman/listinfo/owasp-leaders" target="_blank">https://lists.owasp.org/mailman/listinfo/owasp-leaders</a><o:p></o:p></p>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

</div>

<table class=MsoNormalTable border=0 cellpadding=0>
 <tr>
  <td style='background:white;padding:.75pt .75pt .75pt .75pt'><pre><span
  style='color:black'>Virtusa was recently ranked and featured in 2010 Global Services 100, IAOP's 2010 Global Outsourcing 100 sub-list, 2009 Deloitte Technology Fast 500 and 2009 Dataquest-IDC Best Employers Survey among others.<o:p></o:p></span></pre><pre><span
  style='color:black'><o:p>&nbsp;</o:p></span></pre><pre><span
  style='color:black'>---------------------------------------------------------------------------------------------<o:p></o:p></span></pre><pre><span
  style='color:black'><o:p>&nbsp;</o:p></span></pre><pre><span
  style='color:black'>This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is intended for the addressee only. Any unauthorized disclosure, use, dissemination, copying, or distribution of this message or any of its attachments or the information contained in this e-mail, or the taking of any action based on it, is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail and delete this message.<o:p></o:p></span></pre><pre><span
  style='color:black'><o:p>&nbsp;</o:p></span></pre><pre><span
  style='color:black'>---------------------------------------------------------------------------------------------<o:p></o:p></span></pre></td>
 </tr>
</table>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>