[Vserver] Alert! --secure broken in 0.27 + vs1.1.5:
 vserver development mailing list 
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
About this list Date view Thread view Subject view Author view Attachment view

From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Sat 22 Nov 2003 - 19:36:15 GMT

Hi Jack!

I get this on Linux version 2.4.22-vs1.1.5
with vserver-0.27

# chcontext --secure --ctx 100 grep -i cap /proc/self/status
New security context is 100
CapInh: 0000000000000000
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff
CapBset: 00000000fffffeff

(which basically means, all except CAP_SETPCAP)

where on Linux version 2.4.22-vs1.00 it gives

# chcontext --secure --ctx 100 grep -i cap /proc/self/status
New security context is 100
CapInh: 0000000000000000
CapPrm: 00000000f40c04ff
CapEff: 00000000f40c04ff
CapBset: 00000000f40c04ff

util-vserver 0.26 gave me on both vs1.00 and vs1.1.5

# chcontext --secure --ctx 100 grep -i cap /proc/self/status
New security context is 100
CapInh: 0000000000000000
CapPrm: 00000000d40c04ff
CapEff: 00000000d40c04ff
CapBset: 00000000d40c04ff

which I consider correct, as CAP_QUOTACTL should be
optional ...

please explain/fix

TIA,
Herbert

_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

About this list Date view Thread view Subject view Author view Attachment view
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Sat 22 Nov 2003 - 19:37:22 GMT by hypermail 2.1.3