Re: [RFC] hurd/hurd_types.defs

2001-05-03 Thread Roland McGrath
> I have a patch ready to go that changes all int -> int32 That does not really do anything but potentially introduce many trivial headaches. > and off_t and ssize_t to int64. That would be a disaster, since that is not the protocol format. ___ Bug-

Re: [RFC] hurd/hurd_types.defs

2001-05-03 Thread Neal H Walfield
> It would be better if we dropped the C type "int" entirely, and > changed to using the MiG type "int32" or "int64", which can then have > C typedefs to the right native types, and the whole thing would be > clearer. I have a patch ready to go that changes all int -> int32 and off_t and ssize_t

Processed: Re: Mach lets processes write to I/O ports

2001-05-03 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 46709 security Bug#46709: Mach lets processes write to I/O ports Tags added: security > severity 46709 critical Bug#46709: Mach lets processes write to I/O ports Severity set to `critical'. > quit Stopping processing here. Please contact me if

Bug#46709: Mach lets processes write to I/O ports

2001-05-03 Thread Kalle Olavi Niemitalo
tags 46709 security severity 46709 critical quit Letting processes write to EGA ports isn't that awful (with today's sync-protected monitors), but if Mach also lets them write to ports used by IDE or SCSI, then it "introduces a security hole on systems where you install the package." No, I didn'