On Fri, 26 May 2006, Paul Moore wrote:
> The NetLabel netlink protocol does have a "version" message which can be
> used to get the version. My main reason for doing this is not to signal
> changes to existing messages, i.e. break backward compatability, but to
> signal to user space applications
James Morris wrote:
> On Fri, 26 May 2006, Paul Moore wrote:
>>>- Why does this module have a version number?
>>>
>>>+ printk(KERN_INFO "NetLabel: Initializing (v%s %s)\n",
>>>+ NETLBL_VER_STR, NETLBL_VER_DATE);
>>>
>>
>>The version number is there primarily to help signal possib
Same issue, I would drop them.
Paul Moore wrote:
Mikel L. Matthews wrote:
Paul Moore wrote:
James Morris wrote:
Outgoing fragment *should* be labeled correctly assuming the Linux base
network stack does the right thing (I haven't tested this yet). The
issue we are discussing here is wha
Mikel L. Matthews wrote:
> Paul Moore wrote:
>>James Morris wrote:
>>>On Thu, 25 May 2006, Paul Moore wrote:
>>>
This patch introduces a new kernel feature designed to support labeled
networking protocols such as RIPSO and CIPSO. These protocols are required
to
interoperate with e
Paul Moore wrote:
James Morris wrote:
On Thu, 25 May 2006, Paul Moore wrote:
This patch introduces a new kernel feature designed to support labeled
networking protocols such as RIPSO and CIPSO. These protocols are required to
interoperate with existing "trusted" operating systems such as Trust
On Fri, 26 May 2006, Paul Moore wrote:
> There may be an issue with packets generated by the kernel directly and
> not as a result of an incoming packet but I can't think of a case where
> this would happen (although I suspect I am just not thinking hard
> enough). Do you have a scenario in mind?
James Morris wrote:
> On Thu, 25 May 2006, Paul Moore wrote:
>>This patch introduces a new kernel feature designed to support labeled
>>networking protocols such as RIPSO and CIPSO. These protocols are required to
>>interoperate with existing "trusted" operating systems such as Trusted
>>Solaris.
On Thu, 25 May 2006, Paul Moore wrote:
> This patch introduces a new kernel feature designed to support labeled
> networking protocols such as RIPSO and CIPSO. These protocols are required to
> interoperate with existing "trusted" operating systems such as Trusted
> Solaris.
A few initial commen
Stephen Hemminger wrote:
On Thu, 25 May 2006 16:06:01 -0400
Paul Moore <[EMAIL PROTECTED]> wrote:
This patch introduces a new kernel feature designed to support labeled
networking protocols such as RIPSO and CIPSO. These protocols are required to
interoperate with existing "trusted" operating s
On Thu, 25 May 2006 16:06:01 -0400
Paul Moore <[EMAIL PROTECTED]> wrote:
> This patch introduces a new kernel feature designed to support labeled
> networking protocols such as RIPSO and CIPSO. These protocols are required to
> interoperate with existing "trusted" operating systems such as Truste
This patch introduces a new kernel feature designed to support labeled
networking protocols such as RIPSO and CIPSO. These protocols are required to
interoperate with existing "trusted" operating systems such as Trusted Solaris.
I am posting the patch now not because I feel it is ready for inclus
11 matches
Mail list logo
