blob: a1d42b06b592509db7658e1b3ae748925443896d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
<html>
<body>
<a href="/ninit/index.html">ninit</a>
<h1>The ninit security guarantee</h1>
I offer <b><font size=+1 color=red>100 Euro</font></b>
to the first person
who publish a verifiable security hole in the latest stable
version of ninit (0.12): for example,
a way for a user to exploit ninit to take over another account.
<p>
Don't change the permition of files.<br>
<pre>
Execs + Dirs: root:root 755
Ninit in/out pipes: root:root 600
Man pages: root:root 644
Files in /etc/ninit: root:root 644
</pre>
My judgment is final as to what constitutes a security hole in
ninit. Any disputes will be reported here.
<p>
<b>Remark <tt>/etc/ninit</tt> config subdirs</b><br>
Ninit uses system functions like setuid, setgid, open, close.
On some UNIX-like OS they are different. For example
uid_t is uint16_t or uint32_t. There are also setuid32, setgid32, ...
analogs of the above functions. Try to use for UID:GID
numbers smaller than 65530.
Who uses daemons with UID bigger than 65530?
If somebody really needs such numbers let me know. How to use
UID:GID see <a href=files.html#Gid>here</a>.
Don't make config files (for example depends 12G, environ 5G)
too big also. I have set limits in the code.
<p>
2 November 2007, Sofia
<br>
Nikola Vladov
<p>
see also
<a href=http://cr.yp.to/qmail/guarantee.html>here</a>
<br>
Last modifed: Tue, 27 Nov 2007 09:08:30
</body>
</html>
|
