Lines Matching refs:we

1 Platforms offer varying security features; we'd like to support the best.
3 This is a document that notes which security hardening we have implemented and
4 which things we'd like to see implemented for various platforms. We
12 wrapping because we believe the practical benefit outweights the implied risks.
13 As such, we prefer to be explicit rather than implicit in our casting or other
17 consider autotools warnings to be an exception as we would like to support
22 On all platforms we attempt to support available compiler hardening and linking
29 On all platforms, we attempt to switch from the administrative user to an
30 unimportant role account which shares data with no other processes. If we start
31 as any user other than an administrative user, we will likely be unable to
36 In addition to the above hardening options, we have tried to extend our
38 we take is documented as well as planned or desired improvements.
40 We do not currently support or set ulimits, we should do so where possible.
42 On Debian Gnu/Linux platforms, we ship with a minimal AppArmor profile, see
52 On ChromeOS we use minijail and seccomp filters, see the following policies for
61 On FreeBSD, we'd like to support jails, chroot, and Capsicum.
63 On OpenBSD, we'd like to support chroot and systrace.
65 On NetBSD, we'd like to chroot.
67 On DragonFly BSD, we'd like to support chroot and jails.
69 On Mac OS X, we'd like to support chroot and seatbelt.
71 On Plan9, we'd like to chroot.
73 On Windows, we do nothing beyond compile time hardening. We'd like to do more.
75 On other platforms, we'll try to run correctly with the understanding that any