On Jun 21, 2007, [email protected] wrote: > On Thu, 21 Jun 2007, Alexandre Oliva wrote: >> On Jun 21, 2007, [email protected] wrote: >> >>> no, one of the rules for the network is that the software must be >>> certified, >> >> In this case you might have grounds to enforce this restriction of the >> network on the network controller itself, I suppose. > how would the network controller know if the software has been modified? The loader could check that and set a flag in the controller. > what sort of signal can the network controller send that couldn't be > forged by the OS? Whatever the network controller designer created to enable it to do so. > how would you do this where the device is a receiver on the netwoek > (such as a satellite receiver) If it's input-only, then you can't possibly harm the operation of the network by only listening in, can you? -- Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/ FSF Latin America Board Member http://www.fsfla.org/ Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org} Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org} - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Al Viro <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Linus Torvalds <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Linus Torvalds <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Linus Torvalds <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Andrew McKay <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alan Cox <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Andrew McKay <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: [email protected]
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: [email protected]
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: [email protected]
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: [email protected]
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Prev by Date: Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching
- Next by Date: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Previous by thread: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Next by thread: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Index(es):