Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: innd(8), nnrpd(8) filter return value (Julien ?LIE)
2. Re: OpenSSL 3 (Julien ?LIE)
----------------------------------------------------------------------
Message: 1
Date: Sun, 2 Aug 2020 19:24:23 +0200
From: Julien ?LIE <[email protected]>
To: [email protected], [email protected]
Subject: Re: innd(8), nnrpd(8) filter return value
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Kevin,
> The filter documentations say that
> innd(8) nnrpd(8) accepts an article if filter_art and filter_post function
> returns empty string, rejects an article if otherwise returns nonempty string.
> If filter_art and filter_post written not to return any value(not even empty
> string),
> how innd(8), nnrpd(8) behaves?
Just tested with no return value for filter_post: nnrpd behaves as
though the return value were an empty string ''.
Checked in source code afterwards for both innd and nnrpd. They
consider NULL (no return value) as an empty string.
> Accepts or rejects or skips decision and does somthing else?
Accepts.
--
Julien ?LIE
??La grippe, ?a dure huit jours si on la soigne et une semaine si on ne
fait rien.?? (Raymond Devos)
------------------------------
Message: 2
Date: Sun, 2 Aug 2020 21:11:54 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: OpenSSL 3
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi The Doctor,
> Anyone trying openssl 3 again INN ?
https://wiki.openssl.org/index.php/OpenSSL_3.0
"Upgrading to OpenSSL 3.0 from OpenSSL 1.1.1 should be relatively
straight forward in most cases."
The good news is that INN 2.6.3 added support for OpenSSL 1.1.x :)
I've just built OpenSSL 3.0-alpha 5, and then INN against it and I
confirm it works fine as-is.
Just 2 spurious warnings originating from OpenSSL files. Could you
mention it to OpenSSL developers so that they fix them? (notably the
second one)
/home/iulius/work/openssl-3.0.0-alpha5/include/openssl/crypto.h:371:20:
attention: le C99 ISO ne supporte pas ??_Noreturn?? [-Wc99-c11-compat]
371 | ossl_noreturn void OPENSSL_die(const char *assertion, const
char *file, int line);
| ^~~~~~~~~~~
=> maybe building INN with the "-Wc99-c11-compat" GCC warning is not
useful and could be removed...
/home/iulius/work/openssl-3.0.0-alpha5/include/openssl/err.h:223:51:
attention:param?tre ??errcode?? inutilis? [-Wunused-parameter]
223 | static ossl_inline int ERR_GET_FUNC(unsigned long errcode)
| ~~~~~~~~~~~~~~^~~~~~~
=> static ossl_inline int ERR_GET_FUNC(ossl_unused unsigned long errcode)
fixes the warning.
--
Julien ?LIE
??Video meliora proboque deteriora sequor.?? (Ovide)
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 122, Issue 3
*******************************************
