[prev in list] [next in list] [prev in thread] [next in thread]
List: openssl-dev
Subject: Re: [openssl-dev] Missing API features
From: "Salz, Rich" <rsalz () akamai ! com>
Date: 2015-04-20 20:25:08
Message-ID: 1c5ed9e9379a4de184323fa82252e76a () usma1ex-dag1mb2 ! msg ! corp ! akamai ! com
[Download RAW message or body]
What is the information you're looking for? "kx=X25519" or kx="2KRSA" or ... ? I \
picked those because sometimes there's a keysize, and other times it's implicit, for \
example. The internal table is going to need restructuring.
--
Senior Architect, Akamai Technologies
IM: richsalz@jabber.at Twitter: RichSalz
From: Richard Moore [mailto:richmoore44@gmail.com]
Sent: Monday, April 20, 2015 4:22 PM
To: openssl-dev@openssl.org
Subject: Re: [openssl-dev] Missing API features
On 20 April 2015 at 15:33, Salz, Rich <rsalz@akamai.com<mailto:rsalz@akamai.com>> \
wrote:
> Continuing with the problems of making structs opaque, currently the API for \
> querying the information about ciphers is quite weak. Only >SSL_CIPHER_description \
> provides access to data such as the key exchange method, and parsing a string to \
> obtain this information seems daft. We're >missing API for: key exchange, \
> authentication method, encryption algorithm, MAC and the export flag.
(Man, outlook makes it hard to NOT top-post. Sigh.)
Since all of those are implied by the cipher spec, could we just have an API to \
return the two-byte cipher identifier? (That would break if TLS 1.3 moves to "a la \
carte" selection, but I doubt that will happen.) Export is gone :) And what's the \
MAC if using an AEAD cipher like AES-GCM?
Just returning the cipher id would mean every app needs to replicate the table that \
openssl already has, and keep it updated. Doesn't seem like a good plan to me. \
According to the current code in openssl the 'MAC' when using AES-GCM is AEAD - not \
ideal perhaps, but what we've got.
> It's also worth noting that SSL_CIPHER_get_version and SSL_CIPHER_description \
> should probably be returning const char * not char *.
Yes, is that a bug to backport or just fix in master, you think?
Changing the return type here should be binary compatible on any sane platform, but \
it might cause source incompatibilities.
Cheers
Rich.
[Attachment #3 (text/html)]
<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 http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:Verdana;
panose-1:2 11 6 4 3 5 4 4 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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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">What \
is the information you’re looking for? “kx=X25519” or \
kx=”2KRSA” or … ? I picked those because sometimes \
there’s a keysize, and other times it’s implicit, for example. The \
internal table is going to need restructuring.<o:p></o:p></span></p> <p \
class="MsoNormal"><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></o:p></span></p>
<p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Senior \
Architect, Akamai Technologies<o:p></o:p></span></p> <p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">IM: \
richsalz@jabber.at Twitter: RichSalz<o:p></o:p></span></p> <p class="MsoNormal"><span \
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<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""> \
Richard Moore [mailto:richmoore44@gmail.com] <br>
<b>Sent:</b> Monday, April 20, 2015 4:22 PM<br>
<b>To:</b> openssl-dev@openssl.org<br>
<b>Subject:</b> Re: [openssl-dev] Missing API features<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span \
style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 20 April 2015 at 15:33, Salz, Rich <<a \
href="mailto:rsalz@akamai.com" target="_blank">rsalz@akamai.com</a>> \
wrote:<o:p></o:p></p> <p class="MsoNormal" \
style="margin-bottom:12.0pt">>Continuing with the problems of making structs \
opaque, currently the API for querying the information about ciphers is quite weak. \
Only >SSL_CIPHER_description provides access to data such as the key exchange \
method, and parsing a string to obtain this information seems daft. We're >missing \
API for: key exchange, authentication method, encryption algorithm, MAC and the \
export flag.<br> <br>
(Man, outlook makes it hard to NOT top-post. Sigh.)<br>
<br>
Since all of those are implied by the cipher spec, could we just have an API to \
return the two-byte cipher identifier? (That would break if TLS 1.3 moves to \
"a la carte" selection, but I doubt that will happen.) Export is gone \
:) And what's the MAC if using an AEAD cipher like AES-GCM?<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span \
style="font-family:"Verdana","sans-serif"">Just returning the \
cipher id would mean every app needs to replicate the table that openssl already has, \
and keep it updated. Doesn't seem like a good plan to me. According to the current \
code in openssl the 'MAC' when using AES-GCM is AEAD - not ideal perhaps, but what \
we've got.<o:p></o:p></span></p> </div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in \
6.0pt;margin-left:4.8pt;margin-right:0in"> <p class="MsoNormal">> It's also worth \
noting that SSL_CIPHER_get_version and SSL_CIPHER_description should probably be \
returning const char * not char *.<br> <br>
Yes, is that a bug to backport or just fix in master, you think?<o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span \
style="font-family:"Verdana","sans-serif"">Changing the return \
type here should be binary compatible on any sane platform, but it might cause source \
incompatibilities.<o:p></o:p></span></p> </div>
<div>
<p class="MsoNormal"><span \
style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span \
style="font-family:"Verdana","sans-serif"">Cheers<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span \
style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span \
style="font-family:"Verdana","sans-serif"">Rich.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span \
style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>
_______________________________________________
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
--===============1590921840743131612==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic