projects / packages / chrootuid.git / blame
| Commit | Line | Data |
|---|---|---|
| 901e7125 ER |
1 | Summary: Runs Daemons with restricted File System Access |
| 2 | Name: chrootuid | |
| 3 | Version: 1.3 | |
| 4 | Release: 1 | |
| 5 | License: BSD License | |
| 6 | Group: Applications | |
| 7 | Source0: http://ftp.porcupine.org/pub/security/%{name}%{version}.tar.gz | |
| 8 | # Source0-md5: 15510abadf5de189e1c22a1544dc926a | |
| 9 | Patch1: http://ftp.debian.org/debian/pool/main/c/chrootuid/%{name}_1.3-6.diff.gz | |
| 10 | # Patch1-md5: 5d2b52c59c6f915b973055375e9b0ec0 | |
| 11 | URL: http://ftp.porcupine.org/pub/security/index.html | |
| 12 | BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) | |
| 13 | ||
| 14 | %description | |
| 15 | Chrootuid makes it easy to run a network service at low privilege | |
| 16 | level and with restricted file system access. At Eindhoven University | |
| 17 | we use this program to run the gopher and www (world-wide web) network | |
| 18 | daemons in a minimal environment: the daemons have access only to | |
| 19 | their own directory tree, and run under a low-privileged userid. The | |
| 20 | arrangement greatly reduces the impact of possible loopholes in daemon | |
| 21 | software. | |
| 22 | ||
| 23 | %prep | |
| 24 | %setup -q -n %{name}%{version} | |
| 25 | %patch1 -p1 | |
| 26 | ||
| 27 | %build | |
| 28 | %{__make} \ | |
| 29 | CC="%{__cc}" \ | |
| 30 | CFLAGS="%{rpmcflags}" \ | |
| 31 | all | |
| 32 | ||
| 33 | %install | |
| 34 | rm -rf $RPM_BUILD_ROOT | |
| 35 | install -d $RPM_BUILD_ROOT{%{_bindir},%{_mandir}/man1} | |
| 36 | install -p chrootuid $RPM_BUILD_ROOT%{_bindir} | |
| 37 | cp -p chrootuid.1 $RPM_BUILD_ROOT%{_mandir}/man1 | |
| 38 | ||
| 39 | %clean | |
| 40 | ||
| 41 | %files | |
| 42 | %defattr(644,root,root,755) | |
| 43 | %doc README chrootuid_license | |
| 44 | %attr(755,root,root) %{_bindir}/chrootuid | |
| 45 | %{_mandir}/man1/chrootuid.1* |