Bug 630 - check_ttyname: FAIL none (sudo) vs. /dev/console (libc)
check_ttyname: FAIL none (sudo) vs. /dev/console (libc)
Status: RESOLVED FIXED
Product: Sudo
Classification: Unclassified
Component: Sudo
1.8.9
PC Linux
: low normal
Assigned To: Todd C. Miller
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-13 09:58 MST by Evangelos Foutras
Modified: 2014-01-13 12:16 MST (History)
0 users

See Also:


Attachments
Build log (110.26 KB, text/x-log)
2014-01-13 09:59 MST, Evangelos Foutras
Details
Test-suite log (18.70 KB, text/x-log)
2014-01-13 10:02 MST, Evangelos Foutras
Details
Fix for /proc/self/stat parsing bugs (680 bytes, application/octet-stream)
2014-01-13 11:04 MST, Todd C. Miller
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Evangelos Foutras 2014-01-13 09:58:32 MST
I'm getting the following test failure for sudo 1.8.9–1.8.9p2:

> check_ttyname: FAIL none (sudo) vs. /dev/console (libc)

This occurs on Arch Linux with glibc 2.18.

The previous version, sudo 1.8.8, doesn't fail any test cases.

You can see the PKGBUILD file below for configure options used:

https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/sudo

I'm not sure what other information might be useful; let me know if I missed something.
Comment 1 Evangelos Foutras 2014-01-13 09:59:12 MST
Created attachment 390 [details]
Build log
Comment 2 Evangelos Foutras 2014-01-13 10:02:16 MST
Created attachment 391 [details]
Test-suite log
Comment 3 Todd C. Miller 2014-01-13 11:04:49 MST
Created attachment 392 [details]
Fix for /proc/self/stat parsing bugs

This is fallout from the introduction of strtonum().  I'll release 1.8.9p3 shortly with the attached patch.
Comment 4 Evangelos Foutras 2014-01-13 11:34:16 MST
(In reply to Todd C Miller from comment #3)
> Created attachment 392 [details]
> Fix for /proc/self/stat parsing bugs
> 
> This is fallout from the introduction of strtonum().  I'll release
> 1.8.9p3 shortly with the attached patch.

I can confirm that the issue is fixed in 1.8.9p3.

Many thanks.