Bug 1221492 - sudo-1.9.12p1-150500.7.7.1.x86_64 has a bug
Summary: sudo-1.9.12p1-150500.7.7.1.x86_64 has a bug
Status: RESOLVED FIXED
Alias: None
Product: PUBLIC SUSE Linux Enterprise Server 15 SP6
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: unspecified
Hardware: Other Other
: P2 - High : Normal
Target Milestone: ---
Assignee: Otto Hollmann
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-15 21:23 UTC by Johann Pickl
Modified: 2024-05-06 15:04 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Johann Pickl 2024-03-15 21:23:30 UTC 
sudo-1.9.12p1-150500.7.7.1.x86_64 has a bug (sudo without password did not work) and must  replaced by sudo-1.9.12p1-150500.7.10.1.x86_64


* Fri Mar 08 2024 otto.hollmann@suse.com
- Fix NOPASSWD issue introduced by patches for CVE-2023-42465
  [bsc#1221151, bsc#1221134]
  * Update sudo-CVE-2023-42465-1of2.patch sudo-CVE-2023-42465-2of2.patch
  * Enable running regression selftests during build time.
Comment 1 Johann Pickl 2024-03-15 23:11:54 UTC 
Snapshot-202403-1
Comment 2 Otto Hollmann 2024-03-18 09:38:49 UTC 
There is a pending request with version upgrade to sudo 1.9.15p5
https://build.suse.de/request/show/316558

This broken version sudo-1.9.12p1-150500 comes from SLE15-SP5 and there is also fix for SLE15-SP5:
https://build.suse.de/request/show/323616

So for fixing this issue we should accept SR#316558 (preffered way) or inherit fixed version from SLE15-SP5 (sudo-1.9.12p1-150500.7.10.1, see bug 1221134 comment 19).
Comment 3 Otto Hollmann 2024-04-18 12:23:52 UTC 
@Johann, can you please confirm if this issue is resolved?
Comment 4 Johann Pickl 2024-04-18 13:13:11 UTC 
(In reply to Otto Hollmann from comment #3)
> @Johann, can you please confirm if this issue is resolved?

yes, this issue is resolved
Comment 5 Otto Hollmann 2024-05-06 15:04:15 UTC 
Thank you for confirmation, closing this bug.