<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/lib/libpam/modules/pam_exec/pam_exec.c, branch releng/12.4</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=releng%2F12.4</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=releng%2F12.4'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2021-12-22T10:01:30Z</updated>
<entry>
<title>Apply tentative fix for clang 11 warning in pam_exec(8):</title>
<updated>2021-12-22T10:01:30Z</updated>
<author>
<name>Dimitry Andric</name>
<email>dim@FreeBSD.org</email>
</author>
<published>2020-08-06T19:31:52Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=cef2fa92dcb3157d93b9f85f24c0d8aab38ed578'/>
<id>urn:sha1:cef2fa92dcb3157d93b9f85f24c0d8aab38ed578</id>
<content type='text'>
lib/libpam/modules/pam_exec/pam_exec.c:222:56: error: format specifies type 'char *' but the argument has type 'const void *' [-Werror,-Wformat]
               if (asprintf(&amp;envstr, "%s=%s", pam_item_env[i].name, item) &lt; 0)
                                         ~~                         ^~~~

(cherry picked from commit 228005931ca9c800e306e7b7d4aa0803197fea7d)
</content>
</entry>
<entry>
<title>For full Linux-PAM compatibility, add a trailing NUL character when</title>
<updated>2018-09-04T10:51:41Z</updated>
<author>
<name>Dag-Erling Smørgrav</name>
<email>des@FreeBSD.org</email>
</author>
<published>2018-09-04T10:51:41Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=e165d7bc3934136f4e22d417d7f429fa4cdd87d2'/>
<id>urn:sha1:e165d7bc3934136f4e22d417d7f429fa4cdd87d2</id>
<content type='text'>
passing the authentication token to the external program.

Approved by:	re (kib)
Submitted by:	Thomas Munro &lt;munro@ip9.org&gt;
MFC after:	1 week
Differential Revision:	D16950
</content>
</entry>
<entry>
<title>Add support for Linux-PAM's badly named expose_authtok option.</title>
<updated>2018-08-14T00:14:17Z</updated>
<author>
<name>Dag-Erling Smørgrav</name>
<email>des@FreeBSD.org</email>
</author>
<published>2018-08-14T00:14:17Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=bb3ba83eeefba8d3e19fd54a450bea57ccd2b8c8'/>
<id>urn:sha1:bb3ba83eeefba8d3e19fd54a450bea57ccd2b8c8</id>
<content type='text'>
Submitted by:	Thomas Munro &lt;munro@ip9.org&gt;
MFC after:	1 week
Differential Revision:	D16171
</content>
</entry>
<entry>
<title>lib: further adoption of SPDX licensing ID tags.</title>
<updated>2017-11-26T02:00:33Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2017-11-26T02:00:33Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=5e53a4f90f82c4345f277dd87cc9292f26e04a29'/>
<id>urn:sha1:5e53a4f90f82c4345f277dd87cc9292f26e04a29</id>
<content type='text'>
Mainly focus on files that use BSD 2-Clause license, however the tool I
was using mis-identified many licenses so this was mostly a manual - error
prone - task.

The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.
</content>
</entry>
<entry>
<title>Add options to capture stdout and / or stderr and pass the output on</title>
<updated>2017-03-22T13:16:04Z</updated>
<author>
<name>Dag-Erling Smørgrav</name>
<email>des@FreeBSD.org</email>
</author>
<published>2017-03-22T13:16:04Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=3869fb783225f2417b2d420a36130c779441f652'/>
<id>urn:sha1:3869fb783225f2417b2d420a36130c779441f652</id>
<content type='text'>
to the user.  There is currently no buffering, so the result may be
somewhat unpredictable if the conversation function adds a newline,
like openpam_ttyconv() does.

Clean up and simplify the environment handling code, which triggered
an inexplicable bug on some systems.

MFC after:	2 weeks
</content>
</entry>
<entry>
<title>Revert r314780</title>
<updated>2017-03-12T17:41:51Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2017-03-12T17:41:51Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=94a1344578b5cba4aba17dc38db0b619d51d2f1d'/>
<id>urn:sha1:94a1344578b5cba4aba17dc38db0b619d51d2f1d</id>
<content type='text'>
libpam: extra bounds checking through reallocarray(3).

It appears to be causing brokenness when reporting PAM_* environment
variables. This requires more investigation.

Reported by:	lstewart
</content>
</entry>
<entry>
<title>libpam: extra bounds checking through reallocarray(3).</title>
<updated>2017-03-06T15:45:46Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2017-03-06T15:45:46Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=b5120bbada1620593d9ea721ca733a0f3cda3c6d'/>
<id>urn:sha1:b5120bbada1620593d9ea721ca733a0f3cda3c6d</id>
<content type='text'>
Reviewed by:	des
MFC after:	1 week
</content>
</entry>
<entry>
<title>Revert r314777: wrong log, the change was to libpam.</title>
<updated>2017-03-06T15:42:03Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2017-03-06T15:42:03Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=fdd2f2ebdd2d3baf8ce4100194facdb18158a2e7'/>
<id>urn:sha1:fdd2f2ebdd2d3baf8ce4100194facdb18158a2e7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>libfetch: extra bounds checking through reallocarray(3).</title>
<updated>2017-03-06T15:37:34Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2017-03-06T15:37:34Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=bb7d0109d7e88a18d1eb22518f302c335d634af6'/>
<id>urn:sha1:bb7d0109d7e88a18d1eb22518f302c335d634af6</id>
<content type='text'>
Reviewed by:	des
MFC after:	1 week
</content>
</entry>
<entry>
<title>Fix error messages containing the executed command name</title>
<updated>2012-04-12T14:02:59Z</updated>
<author>
<name>Jean-Sébastien Pédron</name>
<email>dumbbell@FreeBSD.org</email>
</author>
<published>2012-04-12T14:02:59Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=3902d8a991387ba1fd7384820f17dd107d09793f'/>
<id>urn:sha1:3902d8a991387ba1fd7384820f17dd107d09793f</id>
<content type='text'>
Before, we took the first argument to pam_exec(8). With the addition of
options in front of the command, this could be wrong.

Now, options are parsed before calling _pam_exec() and messages contain
the proper command name.

While here, fix a warning.

Sponsored by:	Yakaz (http://www.yakaz.com)
</content>
</entry>
</feed>
