Re: Certificate validation confusion

--===============8510874225097696966==
Content-Type: multipart/alternative; boundary="000000000000482de90567accf00"

--000000000000482de90567accf00
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Yes, that would be good.

=D0=BF=D1=82, 16 =D0=BC=D0=B0=D1=80. 2018 =D0=B3. =D0=B2 10:08, Manfred Lot=
z <[email protected]>:

> On Thu, 15 Mar 2018 21:58:17 +0000
> Alexander Lukyanov <[email protected]> wrote:
>
> > I think the name of your certificate was recognized as a false value.
> > The ssl:verify-certificate setting expacts a boolean value (true,
> > false, yes, no, on, off, 1, 0).
> >
>
> Yes, you are right. My fault. Actually the file name started with a
> letter 'F'.
>
> But why doesn't ResMgr.cc check boolean values more thoroughly?
>
> I think values should be either the full value or a single letter, and
> case-insensitive. For instance: f,F, false and any lower/upper case
> combination of 'false'. Something like: ftp.certificate should give an
> "Invalid boolean value".
>
> Then specyfing a filename would have given a warning.
>
> What do you think.
>
>
> --
> Manfred
> _______________________________________________
> lftp mailing list
> [email protected]
> http://univ.uniyar.ac.ru/mailman/listinfo/lftp
>

--000000000000482de90567accf00
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Yes, that would be good.<br></div><br><div class=3D"gmail_=
quote"><div dir=3D"ltr">=D0=BF=D1=82, 16 =D0=BC=D0=B0=D1=80. 2018 =D0=B3. =
=D0=B2 10:08, Manfred Lotz &lt;<a href=3D"mailto:[email protected]">ml_news=
@posteo.de</a>&gt;:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, 15 Mar =
2018 21:58:17 +0000<br>
Alexander Lukyanov &lt;<a href=3D"mailto:[email protected]" target=3D"_blank=
">[email protected]</a>&gt; wrote:<br>
<br>
&gt; I think the name of your certificate was recognized as a false value.<=
br>
&gt; The ssl:verify-certificate setting expacts a boolean value (true,<br>
&gt; false, yes, no, on, off, 1, 0).<br>
&gt;<br>
<br>
Yes, you are right. My fault. Actually the file name started with a<br>
letter &#39;F&#39;.<br>
<br>
But why doesn&#39;t ResMgr.cc check boolean values more thoroughly?<br>
<br>
I think values should be either the full value or a single letter, and<br>
case-insensitive. For instance: f,F, false and any lower/upper case<br>
combination of &#39;false&#39;. Something like: ftp.certificate should give=
 an<br>
&quot;Invalid boolean value&quot;.<br>
<br>
Then specyfing a filename would have given a warning.<br>
<br>
What do you think.<br>
<br>
<br>
--<br>
Manfred<br>
_______________________________________________<br>
lftp mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a=
><br>
<a href=3D"http://univ.uniyar.ac.ru/mailman/listinfo/lftp" rel=3D"noreferre=
r" target=3D"_blank">http://univ.uniyar.ac.ru/mailman/listinfo/lftp</a><br>
</blockquote></div>

--000000000000482de90567accf00--

--===============8510874225097696966==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
lftp mailing list
[email protected]
http://univ.uniyar.ac.ru/mailman/listinfo/lftp

--===============8510874225097696966==--