From: Casey Schaufler <casey@schaufler-ca.com>
To: "James W. Hoeft" <Jim@MagitekLtd.com>
Cc: LC Bruzenak <lenny@MagitekLtd.com>, Linux Audit <linux-audit@redhat.com>
Subject: Re: user message limits
Date: Thu, 29 Jan 2009 20:49:54 -0800 [thread overview]
Message-ID: <498286F2.9060200@schaufler-ca.com> (raw)
In-Reply-To: <49815353.7080105@MagitekLtd.com>
James W. Hoeft wrote:
> The requirement to include the entire cut buffer was only for high to
> low (downgrade) transfers (which are only allowed for text), and was a
> "derived" requirement, in that we had to include the text in the audit
> logs in order to get approval to provide that capability.
... if she floats, she weighs less than a duck, and that makes her
a witch! Burn her!
How did you become so wise in the ways of science?
Ah yes, evaluators. There were several places in the CMW spec
that pretty well required things that it also forbade you from
doing. It explains much.
next prev parent reply other threads:[~2009-01-30 4:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 0:01 user message limits LC Bruzenak
2009-01-28 15:30 ` LC Bruzenak
2009-01-28 17:15 ` Steve Grubb
2009-01-28 17:44 ` LC Bruzenak
2009-01-28 20:14 ` Steve Grubb
2009-01-28 20:30 ` LC Bruzenak
2009-01-28 21:04 ` LC Bruzenak
2009-01-28 23:37 ` Casey Schaufler
2009-01-28 23:52 ` LC Bruzenak
2009-01-29 0:36 ` Casey Schaufler
2009-01-29 6:57 ` James W. Hoeft
2009-01-30 4:49 ` Casey Schaufler [this message]
2013-09-17 14:48 ` Richard Guy Briggs
2013-09-17 18:10 ` Steve Grubb
2013-09-18 2:25 ` Richard Guy Briggs
2013-09-18 14:25 ` Steve Grubb
2013-09-18 15:10 ` spurious \n in session id helper [was: Re: user message limits] Richard Guy Briggs
2009-06-08 22:08 ` user message limits LC Bruzenak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=498286F2.9060200@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=Jim@MagitekLtd.com \
--cc=lenny@MagitekLtd.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox