Displaying 9 results from an estimated 9 matches for "tsecs".
Did you mean:
secs
2011 Nov 21
0
[PATCH] xsm/flask: fix resource list range checks
The FLASK security checks for resource ranges were not implemented
correctly - only the permissions on the endpoints of a range were
checked, instead of all items contained in the range. This would allow
certain resources (I/O ports, I/O memory) to be used by domains in
contravention to security policy.
This also corrects a bug where adding overlapping resource ranges did
not trigger an error.
2007 Jan 27
1
Memory leaks in backgroundrb
While debugging stale backgroundrb it became apparent that there''re
memory leaks in it. Here''s top object counts dump:
36715 String
6211 Array
5598 Proc
3150 Hash
1478 DRb::DRbObject
1313 Regexp
1272 Class
750 Thread
741 Socket
739 Slave
739 Slave::LifeLine
737 Process::Status
691 DrillReminderWorker
391 Module
160 Range
75 Gem::Version
2015 Nov 09
6
[PATCH 0/5] build: Enable some more warnings.
Add some warnings. Well, the first patch is a miscellaneous
change, but patches 2-5 add some warnings.
Rich.
2023 Mar 24
1
[PATCH v8 4/6] security: Allow all LSMs to provide xattrs for inode_init_security hook
On Fri, Mar 24, 2023 at 6:18?AM Roberto Sassu
<roberto.sassu at huaweicloud.com> wrote:
> On Thu, 2023-03-23 at 20:09 -0400, Paul Moore wrote:
> > On Tue, Mar 14, 2023 at 4:19?AM Roberto Sassu
> > <roberto.sassu at huaweicloud.com> wrote:
> > > From: Roberto Sassu <roberto.sassu at huawei.com>
> > >
> > > Currently,
1999 Oct 20
3
patch for tinc-0.3
Hi tinc list members,
There were some problems with Ivo's email adresses (both zarq@iname.com
and
zarq@spark.icicle.dhs.org) so I resent the stuff to the mailling list.
=============================================
Hi Ivo,
Hier is een oplossing voor een bugje in flush_queue(), en ook wat andere
troepjes
zoals een tincd scheduler. Dit werkt wat beter, omdat de
2012 Jan 31
26
[PATCH 00/10] FLASK updates: MSI interrupts, cleanups
This patch set adds XSM security labels to useful debugging output
locations, and fixes some assumptions that all interrupts behaved like
GSI interrupts (which had useful non-dynamic IDs). It also cleans up the
policy build process and adds an example of how to use the user field in
the security context.
Debug output:
[PATCH 01/10] xsm: Add security labels to event-channel dump
[PATCH 02/10] xsm:
2022 Dec 01
8
[PATCH v7 0/6] evm: Do HMAC of multiple per LSM xattrs for new inodes
From: Roberto Sassu <roberto.sassu at huawei.com>
One of the major goals of LSM stacking is to run multiple LSMs side by side
without interfering with each other. The ultimate decision will depend on
individual LSM decision.
Several changes need to be made to the LSM infrastructure to be able to
support that. This patch set tackles one of them: gives to each LSM the
ability to specify one
1999 Jul 28
6
You got some 'splaininn to do Lucy ;-)
We just had a security application vendor come in. We asked about Linux
support and he said that putting a security application on top of an
insecure OS was useless. When I asked what he meant by insecure he replied
that Linux does not have a true Auditing capability - as opposed to HP-UX &
Solaris which they do support. Can anyone explain to me what he was talking
about?
Thanks,
Marty
2023 Mar 14
7
[PATCH v8 0/6] evm: Do HMAC of multiple per LSM xattrs for new inodes
From: Roberto Sassu <roberto.sassu at huawei.com>
One of the major goals of LSM stacking is to run multiple LSMs side by side
without interfering with each other. The ultimate decision will depend on
individual LSM decision.
Several changes need to be made to the LSM infrastructure to be able to
support that. This patch set tackles one of them: gives to each LSM the
ability to specify one