well, the answers would be: because...
- the security scheme of the current debs are inherited from the
previous maintainer,
- no users have explicitly expressed the need (or wish) of more
security hardening by default,
- I've not had yet the time to cleanly complete these packages (need
debconf, cdbs refactoring, security hardening), nor received help to
do so,
- I've dedicated most of my time upstream (you might want to have a
look at my launchpad wiki),
- ...
In fact, I have the NPS project linked to the packaging
standardization and improvement. I've explicitly added a security
hardening comment: https://alioth.debian.org/pm/?group_id=30602
So, if you're interested in helping, you're more than welcome ;-)
Hi Jamie,
2008/2/8, Jamie Strandboge <email address hidden>: www.networkupst ools.org/ faq/ www.networkupst ools.org/ doc/2.2. 0/chroot. html
> Arnaud,
>
> I was curious as to why the Debian packaging doesn't do the 'security domains' as listed in:
> http://
>
> or even the chrooting as in:
> http://
well, the answers would be: because...
- the security scheme of the current debs are inherited from the
previous maintainer,
- no users have explicitly expressed the need (or wish) of more
security hardening by default,
- I've not had yet the time to cleanly complete these packages (need
debconf, cdbs refactoring, security hardening), nor received help to
do so,
- I've dedicated most of my time upstream (you might want to have a
look at my launchpad wiki),
- ...
You have missed that one ;-) www.networkupst ools.org/ doc/2.2. 0/ideas. html
"Completely unprivileged upsmon" (to drop the remaining root privs)
http://
In fact, I have the NPS project linked to the packaging /alioth. debian. org/pm/ ?group_ id=30602
standardization and improvement. I've explicitly added a security
hardening comment:
https:/
So, if you're interested in helping, you're more than welcome ;-)