public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
* HEADS-UP: struct pam_message in conversation function is now const
@ 2024-07-24  7:30 Andy Fiddaman
  0 siblings, 0 replies; only message in thread
From: Andy Fiddaman @ 2024-07-24  7:30 UTC (permalink / raw)
  To: developer


(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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2024-07-24  7:31 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-07-24  7:30 HEADS-UP: struct pam_message in conversation function is now const Andy Fiddaman

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).