<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>Am 29.04.2018 um 21:38 schrieb Daniel Schmidt <<a href="mailto:daniel.schmidt@wyo.gov">daniel.schmidt@wyo.gov</a>>:</div><div><br></div><blockquote type="cite"><div><div dir="ltr">Thank you very much, I will rebuild and provide the core file. It is exceedingly odd that old version of the libpam google auth works fine and the new one causes tac_plus to crash, but just with pap/nexus. I could also provide instructions to recreate the issue yourself if you have nexus. <br></div></div></blockquote><div><br></div>I‘ll need the executable too and possibly the build dir. If you like, i can provide the executable. <div><br></div><div>I have an older 3k now, so i could reproduce it if you provide the procedure. </div><div><br><blockquote type="cite"><div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Apr 29, 2018 at 9:09 AM, heasley <span dir="ltr"><<a href="mailto:heas@shrubbery.net" target="_blank">heas@shrubbery.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sat, Apr 28, 2018 at 11:59:14AM -0600, Daniel Schmidt:<br>
<div><div class="h5">> Well, that's just weird. Why does the latest libpam google authenticator<br>
> crash when using pap? Works just fine for login. Old libpam google<br>
> doesn't crash. Not sure where the problem is.<br>
> <br>
> ╭─dans@cwacs ~/google-authenticator-libpam ‹master›<br>
> ╰─$ *** Error in `tac_plus': double free or corruption (!prev):<br>
> 0x0000000000b3c000 ***<br>
> ======= Backtrace: =========<br>
> /lib/x86_64-linux-gnu/libc.so.<wbr>6(+0x777e5)[0x7fb0082a37e5]<br>
> /lib/x86_64-linux-gnu/libc.so.<wbr>6(+0x8037a)[0x7fb0082ac37a]<br>
> /lib/x86_64-linux-gnu/libc.so.<wbr>6(cfree+0x4c)[0x7fb0082b053c]<br>
> tac_plus[0x408f6a]<br>
> tac_plus[0x404234]<br>
> tac_plus[0x4129d0]<br>
> tac_plus[0x40312f]<br>
> /lib/x86_64-linux-gnu/libc.so.<wbr>6(__libc_start_main+0xf0)[<wbr>0x7fb00824c830]<br>
> tac_plus[0x4037a9]<br>
> ======= Memory map: ========<br>
> 00400000-0041b000 r-xp 00000000 fc:00 135832<br>
> /usr/local/bin/tac_plus<br>
> 0061a000-0061b000 r--p 0001a000 fc:00 135832<br>
> /usr/local/bin/tac_plus<br>
> 0061b000-0061c000 rw-p 0001b000 fc:00 135832<br>
> /usr/local/bin/tac_plus<br>
> 0061c000-0061f000 rw-p 00000000 00:00 0<br>
> 00b39000-00b5a000 rw-p 00000000 00:00 0<br>
> [heap]<br>
> (and so on)<br>
> <br>
<br>
</div></div>looking at the code surrounding the calls to PAM, its not obvious, if<br>
its even there.<br>
<br>
perhaps you can build tacacs with symbols and collect a core to share?<br>
</blockquote></div><br></div>
<br>
<br>E-Mail to and from me, in connection with the transaction <br>of public business, is subject to the Wyoming Public Records <br>Act and may be disclosed to third parties.<br></div></blockquote></div></body></html>