atom feed20 messages in org.freebsd.freebsd-archRe: short uid/gid
FromSent OnAttachments
Vladimir B. Grebenschikov,Moscow,408-7227,123-4567,Some-infoOct 14, 2002 12:33 am 
Robert WatsonOct 14, 2002 10:27 am 
Maxim SobolevOct 14, 2002 12:17 pm 
Danny J. ZerkelOct 15, 2002 7:47 pm 
Terry LambertOct 15, 2002 9:35 pm 
Robert WatsonOct 15, 2002 9:42 pm 
Terry LambertOct 16, 2002 2:03 am 
Maxim SobolevOct 16, 2002 2:30 am 
Robert WatsonOct 16, 2002 6:03 am 
Maxim SobolevOct 16, 2002 8:06 am 
Robert WatsonOct 16, 2002 9:06 am 
Terry LambertOct 16, 2002 9:29 am 
Terry LambertOct 16, 2002 9:45 am 
Robert WatsonOct 16, 2002 10:01 am 
Gary ThorpeOct 16, 2002 10:38 am 
Terry LambertOct 16, 2002 11:02 am 
Terry LambertOct 16, 2002 11:13 am 
Danny J. ZerkelOct 16, 2002 4:50 pm 
Danny J. ZerkelOct 16, 2002 8:44 pm 
Terry LambertOct 16, 2002 11:06 pm 
Subject:Re: short uid/gid
From:Robert Watson (rwat@FreeBSD.ORG)
Date:Oct 16, 2002 6:03:25 am
List:org.freebsd.freebsd-arch

On Wed, 16 Oct 2002, Maxim Sobolev wrote:

What about source-level compatibility, which IMO is a good thing, at least if it doesn't add too much complexity (it clearly doesn't in this case)? Also, handling single flag should be easier from the coding perspective than a load of new values, after all we can do something like:

I'm not convinced there's any value to providing the backward compatibility that has to be asked for: the only benefit to the current short-based API is that it allow serious security holes while not following the standard API offered by other platforms (except Linux). Freshly compiled applications should be using the proper types to represent uid's and gid's -- if they're not doing that in the existing code, they'll get truncated to the right size for "bug compatibility". If they are using the correct size, they'll work correctly. To be able to run properly on other platforms (vis Solaris), they already should be using those types.

And it's not like the approach you've described makes it any easier to implement: you still have to break out the old and new structures since changing ipc_perm breaks the ABI for all of the System V interfaces, rewrite the kernel code, etc. You might as well have added the compatibility system calls since you still have to do all the mapping.

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects rob@fledge.watson.org Network Associates Laboratories

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message