On Wednesday, April 04, 2012 12:24:33 pm Doug Ambrisko wrote:
> John Baldwin writes:
> | On Tuesday, April 03, 2012 12:37:50 pm Doug Ambrisko wrote:
> | > John Baldwin writes:
> | > | On Monday, April 02, 2012 7:27:13 pm Doug Ambrisko wrote:
> | > | > Doug Ambrisko writes:
> | > | > | John Baldwin
Peter Wemm wemm.org> writes:
> ...
> 5) If you own the machine's kernel, you can hide anything you wish.
> Relocations are not a factor in this.
>
OK. Thanks a lot guys for sharing your answers and time.
It was quite interesting.
jb
___
freebsd-stab
On Wed, Apr 4, 2012 at 10:34 AM, jb wrote:
> Peter Wemm wemm.org> writes:
>
>> ...
>> There is no way to interfere because it is done outside of user space
>> entirely, **after** the file has been copied out of the file system.
>> You can do whatever you like to the file, but it has no effect bec
If there is malicious code in a kernel module, then discussions of
relocations become moot.
Sent from my Android 4.0 device. Please forgive any spelling or grammatical
errors.
On Apr 4, 2012 11:35 AM, "jb" wrote:
> Peter Wemm wemm.org> writes:
>
> > ...
> > There is no way to interfere because
Peter Wemm wemm.org> writes:
> ...
> There is no way to interfere because it is done outside of user space
> entirely, **after** the file has been copied out of the file system.
> You can do whatever you like to the file, but it has no effect because
> all the relocation is done in a private kern
On Wed, Apr 4, 2012 at 8:58 AM, Ian Lepore
wrote:
[..]
> This whole relocation question is just a big red herring. The kernel
> loader relocating a kernel module at load time does not open any
> opportunity for userland code to launch an attack on the memory pages
> into which the module gets loa
John Baldwin writes:
| On Tuesday, April 03, 2012 12:37:50 pm Doug Ambrisko wrote:
| > John Baldwin writes:
| > | On Monday, April 02, 2012 7:27:13 pm Doug Ambrisko wrote:
| > | > Doug Ambrisko writes:
| > | > | John Baldwin writes:
| > | > | | On Saturday, March 31, 2012 3:25:48 pm Doug Ambrisko w
On Wed, Apr 4, 2012 at 8:05 AM, jb wrote:
> Ian Lepore damnhippie.dyndns.org> writes:
>
>> ...
>> > But of interest to me is this:
>> > "...
>> > Text relocations are a way in which references in the executable code to
>> > addresses not known at link time are solved. Basically they just write
>>
On Wed, Apr 4, 2012 at 1:38 AM, jb wrote:
> pobox.com> writes:
>
>> ...
>> You can appeal to authority by saying the Gentoo Hardened developers said
>> such-and-such all you want, but it would be more useful for you to be able
>> to make specific technical arguments yourself. Saying "it could be
Hello.
Does anyone know if FreeBSD 8.2 and FreeBSD 9.1 are fully compatible with this
processor: Intel XEON E3 1270 ?.
Thank you.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send
On Wed, 2012-04-04 at 15:05 +, jb wrote:
> Ian Lepore damnhippie.dyndns.org> writes:
>
> > ...
> > > But of interest to me is this:
> > > "...
> > > Text relocations are a way in which references in the executable code to
> > > addresses not known at link time are solved. Basically they just
jb wrote:
From the point of view of an attacker it does not matter whether kernel module
is loaded and linked once only. That's enough to create a window of opportunity
for interfering with relocation process and modifying text (code).
Well yes but said attacker has to be able to modify KERNEL
On Wed, Apr 4, 2012 at 5:19 AM, Matt Thyer wrote:
> So it seems that both the old and new mps driver have a problem with the
> Western Digital WD20EARX SATA 3 drive on a SuperMicro AOC-USAS2-L8i (SAS
> 6G) controller (flashed with -IT firmware).
I wouldn't say the driver has a problem with that s
Ian Lepore damnhippie.dyndns.org> writes:
> ...
> > But of interest to me is this:
> > "...
> > Text relocations are a way in which references in the executable code to
> > addresses not known at link time are solved. Basically they just write
> > the appropriate address at runtime marking the co
On Wed, 2012-04-04 at 08:38 +, jb wrote:
> pobox.com> writes:
>
> > ...
> > You can appeal to authority by saying the Gentoo Hardened developers said
> > such-and-such all you want, but it would be more useful for you to be able
> > to make specific technical arguments yourself. Saying "it c
Matt, Sorry for addressing to wrong person.!
I am working in Device Driver group and it difficult to track request coming
through emails. We can solve those request through emails which are
minor/medium in complexity.
There are some group in LSI which has expertise to root cause issue and provid
On 4 April 2012 21:55, Desai, Kashyap wrote:
> Mike,
> Have your purchase LSI controller through Channel or OEM ?
> It would be a difficult for developers to help you without any support
> channel invovoled ?
> If possible can you contact LSI support channel ?
>
Kashyap,
It's me, Matt, not Mike
> -Original Message-
> From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-
> sta...@freebsd.org] On Behalf Of Matt Thyer
> Sent: Wednesday, April 04, 2012 5:50 PM
> To: Mike Tancsa
> Cc: freebsd-stable@freebsd.org
> Subject: Re: 157k interrupts per second causing 60% CPU load on
On 25 March 2012 22:26, Matt Thyer wrote:
>
> Does anyone know if and when this driver was merged from current to
> 8-STABLE ?
>
> If I can work out what revision that occurred in I'll go back to just
> before then to confirm if the problem exists.
>
In the -CURRENT list I've been told that the
On Tuesday, April 03, 2012 12:37:50 pm Doug Ambrisko wrote:
> John Baldwin writes:
> | On Monday, April 02, 2012 7:27:13 pm Doug Ambrisko wrote:
> | > Doug Ambrisko writes:
> | > | John Baldwin writes:
> | > | | On Saturday, March 31, 2012 3:25:48 pm Doug Ambrisko wrote:
> | > | | > Sean Bruno writ
pobox.com> writes:
> ...
> You can appeal to authority by saying the Gentoo Hardened developers said
> such-and-such all you want, but it would be more useful for you to be able
> to make specific technical arguments yourself. Saying "it could be a
> problem" or "in the wild there may be" isn't
21 matches
Mail list logo
