<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>66919</bug_id>
          
          <creation_ts>2004-10-09 13:56 0000</creation_ts>
          <short_desc>pam_krb5 segfaults on logout when used in proftpd</short_desc>
          <delta_ts>2005-06-30 15:53:31 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Applications</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>minor</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>christophe@saout.de</reporter>
          <assigned_to>rphillips@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>christophe@saout.de</who>
            <bug_when>2004-10-09 13:56:21 0000</bug_when>
            <thetext>I spent the evening tracking down this bug.

I am using AuthPAM with proftpd and pam_krb5. proftpd always segfaults after logout, and lastlog then tells the user has gone without logout. Great... :)

Well, the problem is that proftpd does a chroot and then calls PAM_DELETE_CREDS. pam_krb5 tries to get the default krb5 realm and fails (because it can&apos;t access its config file due to chroot), the field is uninitialized, points into Nirvana and boom.

I&apos;ve attached a patch that explicitly sets it to &quot;&quot; (empty string, better than nothing) before getting the default realm so that at it doesn&apos;t crash anymore.


Reproducible: Always
Steps to Reproduce:
1.
2.
3.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>christophe@saout.de</who>
            <bug_when>2004-10-09 14:07:08 0000</bug_when>
            <thetext>Created an attachment (id=41434)
Workaround for pam_krb5 to not segfault when unable to get default realm (like
in a chroot environment)
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>christophe@saout.de</who>
            <bug_when>2004-10-09 14:08:24 0000</bug_when>
            <thetext>Created an attachment (id=41435)
Workaround for pam_krb5 to not segfault when unable to get default realm (like
in a chroot environment)

Sorry, wrong patch... this one is the working one.
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>rphillips@gentoo.org</who>
            <bug_when>2005-06-30 15:53:31 0000</bug_when>
            <thetext>Committed. Thanks</thetext>
          </long_desc>
      
          <attachment
              isobsolete="1"
              ispatch="1"
              isprivate="0"
          >
            <attachid>41434</attachid>
            <date>2004-10-09 14:07 0000</date>
            <desc>Workaround for pam_krb5 to not segfault when unable to get default realm (like in a chroot environment)</desc>
            <filename>pam_krb5_snap-2003.06.01-realm-empty.patch</filename>
            <type>text/plain</type>
            <data encoding="base64">ZGlmZiAtTnVyIHBhbV9rcmI1X3NuYXAtMjAwMy4wNi4wMS5vcmlnL3BhbV9rcmI1YWZzLmMgcGFt
X2tyYjVfc25hcC0yMDAzLjA2LjAxL3BhbV9rcmI1YWZzLmMKLS0tIHBhbV9rcmI1X3NuYXAtMjAw
My4wNi4wMS5vcmlnL3BhbV9rcmI1YWZzLmMJMjAwMy0wNi0wMSAyMzo0Mjo0NS4wMDAwMDAwMDAg
KzAyMDAKKysrIHBhbV9rcmI1X3NuYXAtMjAwMy4wNi4wMS9wYW1fa3JiNWFmcy5jCTIwMDQtMTAt
MDkgMjI6MzE6MjIuMTM0MzIyMjQ5ICswMjAwCkBAIC0xMDg5LDYgKzEwODksNyBAQAogCQkJICAg
cmV0LT5yZXRhaW5fdG9rZW4sICZyZXQtPnJldGFpbl90b2tlbik7CiAKIAkvKiBUaGUgZGVmYXVs
dCByZWFsbSB3ZSBhc3N1bWUgdXNlcnMgYXJlIGluIHVubGVzcyB0b2xkIG90aGVyd2lzZS4gKi8K
KwlyZXQtPnJlYWxtWzBdID0gMDsKIAlrcmI1X2dldF9kZWZhdWx0X3JlYWxtKGNvbnRleHQsICZy
ZXQtPnJlYWxtKTsKIAlhcHBkZWZhdWx0X3N0cmluZyhjb250ZXh0LCAicmVhbG0iLCBhcmdjLCBh
cmd2LAogCQkJICByZXQtPnJlYWxtLCAmcmV0LT5yZWFsbSk7Cg==
</data>        

          </attachment>
          <attachment
              isobsolete="0"
              ispatch="1"
              isprivate="0"
          >
            <attachid>41435</attachid>
            <date>2004-10-09 14:08 0000</date>
            <desc>Workaround for pam_krb5 to not segfault when unable to get default realm (like in a chroot environment)</desc>
            <filename>pam_krb5_snap-2003.06.01-realm-empty.patch</filename>
            <type>text/plain</type>
            <data encoding="base64">ZGlmZiAtTnVyIHBhbV9rcmI1X3NuYXAtMjAwMy4wNi4wMS5vcmlnL3BhbV9rcmI1YWZzLmMgcGFt
X2tyYjVfc25hcC0yMDAzLjA2LjAxL3BhbV9rcmI1YWZzLmMKLS0tIHBhbV9rcmI1X3NuYXAtMjAw
My4wNi4wMS5vcmlnL3BhbV9rcmI1YWZzLmMJMjAwMy0wNi0wMSAyMzo0Mjo0NS4wMDAwMDAwMDAg
KzAyMDAKKysrIHBhbV9rcmI1X3NuYXAtMjAwMy4wNi4wMS9wYW1fa3JiNWFmcy5jCTIwMDQtMTAt
MDkgMjI6MzE6MjIuMTM0MzIyMjQ5ICswMjAwCkBAIC0xMDg5LDYgKzEwODksNyBAQAogCQkJICAg
cmV0LT5yZXRhaW5fdG9rZW4sICZyZXQtPnJldGFpbl90b2tlbik7CiAKIAkvKiBUaGUgZGVmYXVs
dCByZWFsbSB3ZSBhc3N1bWUgdXNlcnMgYXJlIGluIHVubGVzcyB0b2xkIG90aGVyd2lzZS4gKi8K
KwlyZXQtPnJlYWxtID0gIiI7CiAJa3JiNV9nZXRfZGVmYXVsdF9yZWFsbShjb250ZXh0LCAmcmV0
LT5yZWFsbSk7CiAJYXBwZGVmYXVsdF9zdHJpbmcoY29udGV4dCwgInJlYWxtIiwgYXJnYywgYXJn
diwKIAkJCSAgcmV0LT5yZWFsbSwgJnJldC0+cmVhbG0pOwo=
</data>        

          </attachment>
    </bug>

</bugzilla>