Re: SHA256 fingerprints

--001a113fc1d470ee180507864ada
Content-Type: text/plain; charset=UTF-8

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?

I was hoping to generate discussion as Id be happy with either options.

Thanks for your work

On Mon, Nov 10, 2014 at 2:06 PM, <[email protected]> wrote:

> On Mon, Nov 10, 2014 at 12:12:30PM -0500, Guillaume Parent wrote:
> >    Hey,
> >    Note that I'm no irssi developer, just curious about this since I have
> >    implemented it in my own client a long time ago.
> >    Wouldn't it be better to use an implementation independent name like
> >    ssl_fingerprint?
>
> I think it is better to use different names for different kinds of
> fingerprints. So, for example, if SHA3 is implemented later, it would be
> possible to have both ssl_sha256 and ssl_sha3 in the same file.
>
> If ssl_fingerprint means sha256 now and changes to sha3 in some version,
> you will get broken configuration file.
>
> Your own client is patched irssi? Can you share the patch too?
>
>

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

<div dir=3D"ltr"><div><div><div><div>Hi,<br><br></div>Yes, my client is a p=
atch over 0.8.16-rc1 if I recall correctly. I am busy tonight but can possi=
bly share the patch when I&#39;m home.<br><br></div>I think it&#39;s an ann=
oying 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 ex=
isting option. I had an attempt where I used the length of the fingerprint =
even though that&#39;s pretty inaccurate. It worked during my testing but I=
 didnt evolve it beyond that. Maybe something like how you specify password=
 hashes?<br><br></div><div>I was hoping to generate discussion as Id be hap=
py with either options.<br><br></div><div>Thanks for your work<br></div></d=
iv></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, =
Nov 10, 2014 at 2:06 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:noname@in=
ventati.org" target=3D"_blank">[email protected]</a>&gt;</span> wrote:<b=
r><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 1=
2:12:30PM -0500, Guillaume Parent wrote:<br>
&gt;=C2=A0 =C2=A0 Hey,<br>
&gt;=C2=A0 =C2=A0 Note that I&#39;m no irssi developer, just curious about =
this since I have<br>
&gt;=C2=A0 =C2=A0 implemented it in my own client a long time ago.<br>
&gt;=C2=A0 =C2=A0 Wouldn&#39;t it be better to use an implementation indepe=
ndent name like<br>
&gt;=C2=A0 =C2=A0 ssl_fingerprint?<br>
<br>
</span>I think it is better to use different names for different kinds of<b=
r>
fingerprints. So, for example, if SHA3 is implemented later, it would be<br=
>
possible to have both ssl_sha256 and ssl_sha3 in the same file.<br>
<br>
If ssl_fingerprint means sha256 now and changes to sha3 in some version,<br=
>
you will get broken configuration file.<br>
<br>
Your own client is patched irssi? Can you share the patch too?<br>
<br>
</blockquote></div><br></div>

--001a113fc1d470ee180507864ada--