Re: SHA256 fingerprints

--047d7bdca67ea4ddbd0507d29eee
Content-Type: text/plain; charset=UTF-8

Yes, that approach seems sane, though it would be interesting to see what
others think about it.

I will be sending you a link to my github irssi repo, because (and sorry
for that) I've been more busy than expected this week. It should contain
the commits so you can at least start comparing my code to yours. I'm not a
C genius, and I love constructive feedback, so don't hesitate to point out
what sucks and what's good about my version of the patch.

On Tue, Nov 11, 2014 at 2:04 PM, <[email protected]> wrote:

> On Mon, Nov 10, 2014 at 02:37:19PM -0500, Guillaume Parent wrote:
> >    Hi,
> >    Yes, my client is a patch over 0.8.16-rc1 if I recall correctly. I am
> >    busy tonight but can possibly share the patch when I'm home.
>
> >    I think it's an annoying balance between having a generic name for the
> >    option if the irssi dev team wants to use a different hash in the
> >    future vs. the clarity of the existing option. I had an attempt where
> I
> >    used the length of the fingerprint even though that's pretty
> >    inaccurate. It worked during my testing but I didnt evolve it beyond
> >    that. Maybe something like how you specify password hashes?
>
> Good idea. Maybe something like
>
> ssl_fingerprint="sha256:DE:AD:BE:EF:..."
>
> Irssi passes first token to EVP_get_digestbyname so user can switch to
> new type of hash as soon as it is available in Libre^WOpenSSL.
>
>

--047d7bdca67ea4ddbd0507d29eee
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Yes, that approach seems sane, though it would be int=
eresting to see what others think about it.<br><br></div>I will be sending =
you a link to my github irssi repo, because (and sorry for that) I&#39;ve b=
een more busy than expected this week. It should contain the commits so you=
 can at least start comparing my code to yours. I&#39;m not a C genius, and=
 I love constructive feedback, so don&#39;t hesitate to point out what suck=
s and what&#39;s good about my version of the patch.<br></div><div class=3D=
"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Nov 11, 2014 at 2:04 P=
M,  <span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]" target=3D=
"_blank">[email protected]</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><span class=3D"">On Mon, Nov 10, 2014 at 02:37:19PM -0500, Guill=
aume Parent wrote:<br>
&gt;=C2=A0 =C2=A0 Hi,<br>
&gt;=C2=A0 =C2=A0 Yes, my client is a patch over 0.8.16-rc1 if I recall cor=
rectly. I am<br>
&gt;=C2=A0 =C2=A0 busy tonight but can possibly share the patch when I&#39;=
m home.<br>
<br>
&gt;=C2=A0 =C2=A0 I think it&#39;s an annoying balance between having a gen=
eric name for the<br>
&gt;=C2=A0 =C2=A0 option if the irssi dev team wants to use a different has=
h in the<br>
&gt;=C2=A0 =C2=A0 future vs. the clarity of the existing option. I had an a=
ttempt where I<br>
&gt;=C2=A0 =C2=A0 used the length of the fingerprint even though that&#39;s=
 pretty<br>
&gt;=C2=A0 =C2=A0 inaccurate. It worked during my testing but I didnt evolv=
e it beyond<br>
&gt;=C2=A0 =C2=A0 that. Maybe something like how you specify password hashe=
s?<br>
<br>
</span>Good idea. Maybe something like<br>
<br>
ssl_fingerprint=3D&quot;sha256:DE:AD:BE:EF:...&quot;<br>
<br>
Irssi passes first token to EVP_get_digestbyname so user can switch to<br>
new type of hash as soon as it is available in Libre^WOpenSSL.<br>
<br>
</blockquote></div><br></div>

--047d7bdca67ea4ddbd0507d29eee--