[Bug 345564] Re: bug in chrpath option parsing

[Ubuntu Foundation's Bug Bot]

The attachment "chrpath-0.13-getopt_long.patch" of this bug report has
been identified as being a patch.  The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch.  In the
event that this is in fact not a patch you can resolve this situation by
removing the tag 'patch' from the bug report and editing the attachment
so that it is not flagged as a patch.  Additionally, if you are member
of the ubuntu-reviewers team please also unsubscribe the team from this
bug report.

[This is an automated message performed by a Launchpad user owned by
Brian Murray.  Please contact him regarding any issues with the action
taken in this bug report.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to chrpath in Ubuntu.
https://bugs.launchpad.net/bugs/345564

Title:
  bug in chrpath option parsing

Status in “chrpath” package in Ubuntu:
  New

Bug description:
  Binary package hint: chrpath

  In package chrpath-0.13-2, in source file main.c at line 26, the long_options array should be terminated with a zeroed entry, as per getopt_long(3), but it is not.
  This causes chrpath to crash if an unknown long option is specified.

  On my system (ubuntu jaunty amd64) the bug does not always show in the distributed binary because (by luck) some null bytes happen to follow the array in the compiled image, but the executable will crash if you specify a "forged" option such as:
     chrpath --$(printf "\206 \255\373")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrpath/+bug/345564/+subscriptions