From: Andy Fiddaman <illumos@fiddaman.net>
To: developer@lists.illumos.org
Subject: HEADS-UP: struct pam_message in conversation function is now const
Date: Wed, 24 Jul 2024 07:30:56 +0000 (UTC) [thread overview]
Message-ID: <5b282ce8-f651-412f-8387-a2be8e8243f2@fiddaman.net> (raw)
(I'm sending this out on Dominik's behalf):
"15657 struct pam_message in conversation function should be const" has
recently been integrated and it updates the definition of the pam_message
parameter to a conversation function to be const. This brings it in line
with what was already in at least one man page
(https://illumos.org/man/3PAM/pam_start),
and with other systems such as FreeBSD and Linux.
This should improve compatibility with 3rd party software which already
generally expects this. However, some software has conditionals based on
illumos/Solaris to select a non-const variant on those platforms.
(A good example is
https://github.com/openssh/openssh-portable/blob/V_9_8/auth-pam.c#L70-L75)
Doing so is usually just a compiler warning, but can become an error if
software is:
- built with clang >= 16
- built with gcc >= 14
- built with `-Werror`
We are working on patching 3rd party software upstream. If you hit a
problem, please reach out, but you can also define `_PAM_LEGACY_NONCONST`
as a last resort to get back the legacy non-const interface.
Regards,
Dominik
reply other threads:[~2024-07-24 7:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5b282ce8-f651-412f-8387-a2be8e8243f2@fiddaman.net \
--to=illumos@fiddaman.net \
--cc=developer@lists.illumos.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).