Package Details: sudo-selinux 1.9.17.p2-1

Git Clone URL: https://aur.archlinux.org/sudo-selinux.git (read-only, click to copy)
Package Base: sudo-selinux
Description: Give certain users the ability to run some commands as root - SELinux support
Upstream URL: https://www.sudo.ws/sudo/
Keywords: selinux
Licenses: custom
Groups: selinux
Conflicts: selinux-sudo, sudo
Provides: selinux-sudo, sudo
Submitter: Siosm
Maintainer: IooNag
Last Packager: IooNag
Votes: 17
Popularity: 0.000315
First Submitted: 2013-11-03 20:05 (UTC)
Last Updated: 2025-10-23 04:38 (UTC)

Required by (371)

Sources (4)

Latest Comments

TymonMarek commented on 2026-03-11 06:14 (UTC) (edited on 2026-03-11 06:19 (UTC) by TymonMarek)

I am having issues installing this package on a fresh Arch Linux install. The issue is similar to the one mentioned by @fhenriquedev, where check() is failing.

I followed the Arch Linux Wiki SELinux guide: https://wiki.archlinux.org/title/SELinux

...
fuzz_policy: verifying corpus
check_addr: 9 tests run, 0 errors, 100% success rate
check_base64: 12 tests run, 0 errors, 100% success rate
check_editor: 16 tests run, 0 errors, 100% success rate
check_env_pattern: 22 tests run, 0 errors, 100% success rate
check_exptilde: 6 tests run, 0 errors, 100% success rate
check_fill: 18 tests run, 0 errors, 100% success rate
check_gentime: 17 tests run, 0 errors, 100% success rate
check_iolog_plugin: 8 tests run, 0 errors, 100% success rate
check_serialize_list: 2 tests run, 0 errors, 100% success rate
check_starttime: test 1: unable to get start time for pid 101493
check_starttime: test 2: unexpected start time for pid 101493: Thu Jan  1 00:34:08 1970
check_starttime: test 3: unable to get start time for pid 101345
check_starttime: 3 tests run, 3 errors, 0% success rate
check_unesc: 19 tests run, 0 errors, 100% success rate
check_symbols: 8 tests run, 0 errors, 100% success rate
sudoers: 174 tests run, 0 errors, 100% success rate
testsudoers: 62 tests run, 0 errors, 100% success rate
visudo: 20 tests run, 0 errors, 100% success rate
cvtsudoers: 82 tests run, 0 errors, 100% success rate
make[1]: *** [Makefile:653: check] Error 3
make[1]: Leaving directory '/home/tymon/sudo-selinux/src/sudo-1.9.17p2/plugins/sudoers'
make: *** [Makefile:116: check] Error 2
==> ERROR: A failure occurred in check().
    Aborting...
[tymon@archiso sudo-selinux]$

Running makepkg with the --nocheck flag installs fine but obviously skips the check() stage:

==> Creating package "sudo-selinux-debug"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: sudo-selinux 1.9.17.p2-1 (Wed Mar 11 06:13:42 2026)
==> Installing package sudo-selinux with pacman -U...
loading packages...
resolving dependencies...
looking for conflicting packages...
:: sudo-selinux-1.9.17.p2-1 and sudo-1.9.17.p2-2 are in conflict. Remove sudo? [y/N] y

Packages (3) sudo-1.9.17.p2-2 [removal]  sudo-selinux-1.9.17.p2-1  sudo-selinux-debug-1.9.17.p2-1

Total Installed Size:  17.48 MiB
Net Upgrade Size:       9.65 MiB

:: Proceed with installation? [Y/n] y
(2/2) checking keys in keyring                                           [########################################] 100%
(2/2) checking package integrity                                         [########################################] 100%
(2/2) loading package files                                              [########################################] 100%
(2/2) checking for file conflicts                                        [########################################] 100%
(3/3) checking available disk space                                      [########################################] 100%
:: Processing package changes...
(1/1) removing sudo                                                      [########################################] 100%
warning: /etc/sudoers saved as /etc/sudoers.pacsave
(1/2) installing sudo-selinux                                            [########################################] 100%
(2/2) installing sudo-selinux-debug                                      [########################################] 100%
:: Running post-transaction hooks...
(1/4) Creating temporary files...
(2/4) Reloading system manager configuration...
  Skipped: Running in chroot.
(3/4) Restarting marked services...
  Skipped: Running in chroot.
(4/4) Arming ConditionNeedsUpdate...
[tymon@archiso sudo-selinux]$

The commands to do the same are the following. I am unsure if this leaves the system in a secure and safe state so please use at your own risk:

yay -Rns sudo-selinux
yay -Syu
yay -G sudo-selinux
cd sudo-selinux
makepkg -si --nocheck

EDIT: Make sure this command runs in a directory where you have sufficient permissions (e.g. /home/USERNAME):

cd ~
yay -Rns sudo-selinux
yay -Syu
yay -G sudo-selinux
cd sudo-selinux
makepkg -si --nocheck

EDIT: Remember to update the /etc/sudoers file to include the wheel group after you do this, since it will override your current configuration.

fhenriquedev commented on 2019-11-14 01:09 (UTC) (edited on 2019-11-14 01:10 (UTC) by fhenriquedev)

I'm having an error in the check() function inside the PKGBUILD while checking cvtsudoers, had to build with --nocheck option and it installed just fine, and I don't know if it's on purpose but I had to manually run libtool --finish /bin/sudo I didn't saw the warnings in the first time I installed because I was following the Wiki guide and replacing a lot of packages and I got stuck for a couple minutes trying to figure out why I was not able to login after installing all of them, and then I saw the sudo issue in the journal, had to reinstall this package and now, paying more attention, I saw the warning telling to run this command. It solved the issue then.

Siosm commented on 2014-01-02 21:48 (UTC)

Renamed to sudo-selinux

Nicky726 commented on 2012-03-04 09:47 (UTC)

Strage, I thought a build-tested it succesfully. Uploaded new revision from [core] which builds fine.

coolmast commented on 2012-03-03 00:03 (UTC)

The md5sums seem to be broken. At least on my machines I repeatedly get wrong md5 checks for the tar.gz and the tar.gz.sig. Would be nice if someone can fix the issue.

Nicky726 commented on 2010-07-22 11:19 (UTC)

Initial release of selinux-sudo, which is able to set security context.