On Sat, Mar 31, 2012 at 3:42 AM, Richard Yao wrote:
>> There are no security implications, no system resources to be wasted.
>>
>> And if you think there are security implications, then lets see a
>> proof-of-concept.
>
> If I find time to write a proof-of-concept, I promise to publish it
> public
On Friday, March 30, 2012 5:30:34 pm Sean Bruno wrote:
>
> > This is the relevant bits:
> >
> > Handle 0x2600, DMI type 38, 18 bytes
> > IPMI Device Information
> > Interface Type: KCS (Keyboard Control Style)
> > Specification Version: 2.0
> > I2C Slave Address: 0x10
> > NV Stora
On Saturday, March 31, 2012 3:25:48 pm Doug Ambrisko wrote:
> Sean Bruno writes:
> | Noting a failure to attach to the onboard IPMI controller with this dell
> | R815. Not sure what to start poking at and thought I'd though this over
> | here for comment.
> |
> | -bash-4.2$ dmesg |grep ipmi
> | i
John Baldwin writes:
| On Saturday, March 31, 2012 3:25:48 pm Doug Ambrisko wrote:
| > Sean Bruno writes:
| > | Noting a failure to attach to the onboard IPMI controller with this dell
| > | R815. Not sure what to start poking at and thought I'd though this over
| > | here for comment.
| > |
| >
On 04/02/12 05:56, Tom Evans wrote:
> On Sat, Mar 31, 2012 at 3:42 AM, Richard Yao wrote:
>>> There are no security implications, no system resources to be wasted.
>>>
>>> And if you think there are security implications, then lets see a
>>> proof-of-concept.
>>
>> If I find time to write a proof-
On 4/2/12 12:49 PM, Richard Yao wrote:
> On 04/02/12 05:56, Tom Evans wrote:
>> On Sat, Mar 31, 2012 at 3:42 AM, Richard Yao wrote:
There are no security implications, no system resources to be wasted.
And if you think there are security implications, then lets see a
proof-of-c
Let's all calm down here. No need to make this personal. Let's please try
to keep this conversation professional and respectful to all parties
involved.
Richard, I suggest that if you think the current implementation is less
secure than other implementations, you could write a patch and submit it
On Mon, Apr 2, 2012 at 5:49 PM, Richard Yao wrote:
> On 04/02/12 05:56, Tom Evans wrote:
>> On Sat, Mar 31, 2012 at 3:42 AM, Richard Yao wrote:
There are no security implications, no system resources to be wasted.
And if you think there are security implications, then lets see a
>>
On 04/02/12 13:13, Tom Evans wrote:
> On Mon, Apr 2, 2012 at 5:49 PM, Richard Yao wrote:
>> On 04/02/12 05:56, Tom Evans wrote:
>>> On Sat, Mar 31, 2012 at 3:42 AM, Richard Yao wrote:
> There are no security implications, no system resources to be wasted.
>
> And if you think there ar
On Fri, Mar 30, 2012 at 7:42 PM, Richard Yao wrote:
> On 03/30/12 22:15, Peter Wemm wrote:
>> On Fri, Mar 30, 2012 at 3:47 PM, Richard Yao wrote:
>>> On 03/30/12 18:46, Konstantin Belousov wrote:
Reread what I wrote to you. Also, it pays off learning how ELF works
before making conclusi
On Mon, Apr 2, 2012 at 10:31 AM, Richard Yao wrote:
> On 04/02/12 13:13, Tom Evans wrote:
>> On Mon, Apr 2, 2012 at 5:49 PM, Richard Yao wrote:
>>> On 04/02/12 05:56, Tom Evans wrote:
On Sat, Mar 31, 2012 at 3:42 AM, Richard Yao
wrote:
>> There are no security implications, no sys
On 04/02/12 14:46, Peter Wemm wrote:
> Remember.. ASLR is a userland thing. .ko files, which is what this
> thread is about, already use random address layout. When you do a
> "kldload virtio.ko", you have no way to predict what address it will
> be loaded at. And you don't even have access to t
On Mon, Apr 2, 2012 at 12:23 PM, Richard Yao wrote:
> On 04/02/12 14:46, Peter Wemm wrote:
>> Remember.. ASLR is a userland thing. .ko files, which is what this
>> thread is about, already use random address layout. When you do a
>> "kldload virtio.ko", you have no way to predict what address it
On 04/02/12 15:37, Peter Wemm wrote:
> On Mon, Apr 2, 2012 at 12:23 PM, Richard Yao wrote:
>> On 04/02/12 14:46, Peter Wemm wrote:
>>> Remember.. ASLR is a userland thing. .ko files, which is what this
>>> thread is about, already use random address layout. When you do a
>>> "kldload virtio.ko",
On Mon, Apr 2, 2012 at 1:02 PM, Richard Yao wrote:
> On 04/02/12 15:37, Peter Wemm wrote:
>> On Mon, Apr 2, 2012 at 12:23 PM, Richard Yao wrote:
>>> On 04/02/12 14:46, Peter Wemm wrote:
Remember.. ASLR is a userland thing. .ko files, which is what this
thread is about, already use rand
Doug Ambrisko writes:
| John Baldwin writes:
| | On Saturday, March 31, 2012 3:25:48 pm Doug Ambrisko wrote:
| | > Sean Bruno writes:
| | > | Noting a failure to attach to the onboard IPMI controller with this dell
| | > | R815. Not sure what to start poking at and thought I'd though this over
| |
Good Day ,
I pray my mail gets to you this time. I'd write you on two occasions concerning
your assistance to help certify a piece of document due to some similarities in
location with the supposed care-taker to enable a safe transfer of securities
proceeds out of Turkey.
Please let me know i
Hello,
r232411 broke onboard 1068 detection on all boxes with SuperMicro
X8ST3 motherboards for us.
All of them are also equipped with two extra 1068 controllers, which
are detected fine. Reverting to r231518 with otherwise latest stable
kernel works around the problem.
The issue is still there
18 matches
Mail list logo
