All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Waychison <Michael.Waychison@Sun.COM>
To: "Dimitry V. Ketov" <Dimitry.Ketov@avalon.ru>
Cc: autofs@linux.kernel.org
Subject: Re: Exporting UID to userspace?
Date: Mon, 07 Jun 2004 12:06:40 -0400	[thread overview]
Message-ID: <40C49290.8060309@sun.com> (raw)
In-Reply-To: <E1B7C89B8DCB084C809A22D7FEB90B3841A4@frodo.avalon.ru>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dimitry V. Ketov wrote:
>
>>-----Original Message-----
>>From: Robin Rosenberg [mailto:robin.rosenberg.lists@dewire.com]
>>
>>On Saturday 05 June 2004 17.52, raven@themaw.net wrote:
>>..
>>
>>>How will you provide a consistent Unix UID <-> Windows UID mapping?
>>>And on multiple machines for the same user, over OS re-install? Ian
>>
>>cases you can use a mapping table in the script that
>>automount calls. Autofs should just provide the local uid,gid
>>from the calling process.
>
>
> Yes, you're definitely right. In fact I want this finctionality just for
> 'program' maps, lets say UID, GID and supplementary GIDs like a second,
> third, so on ... parameters to the map script.
>

My real problem with this RFE is that there is no indication on how you
are planning to acquire the user credentials.

For instance:
- - how are you going to acquire terminal information with just a uid/gid
pair?
- - how are you going to handle the case where there was no terminal?
- - what about when there was no terminal, but there were X resources
available? (kernelspace wouldn't know anything about this at all..)


Shouldn't this RFE also include some proposal for how you are going to
ensure that only a single uid ever attempts access to the automounted
directory as well? (if needed?)


The current work-around is to have the credentials supplied by the map
itself.

- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
mailto: Michael.Waychison@Sun.COM
http://www.sun.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE:  The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAxJKPdQs4kOxk3/MRAuX9AJ9FVcGKhOMzPLFkHspT02CiattpMQCdH56m
/AkQpZ1/5XmoGL+9cJ8poE0=
=9W5D
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-06-07 16:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-07 12:45 Exporting UID to userspace? Dimitry V. Ketov
2004-06-07 16:06 ` Mike Waychison [this message]
2004-06-07 22:53   ` Robin Rosenberg
  -- strict thread matches above, loose matches on Subject: below --
2004-06-10 16:14 Dimitry V. Ketov
2004-06-10 16:59 ` Mike Waychison
2004-06-10 14:55 Dimitry V. Ketov
2004-06-10 15:54 ` Mike Waychison
2004-06-09 18:10 Dimitry V. Ketov
2004-06-09 18:44 ` Mike Waychison
2004-06-10  1:13   ` Ian Kent
2004-06-08 17:47 Dimitry V. Ketov
2004-06-08 18:20 ` Robin Rosenberg
2004-06-07 12:38 Dimitry V. Ketov
2004-06-08  1:15 ` Ian Kent
2004-06-08 13:12   ` Brian Long
2004-06-08 16:28     ` raven
2004-06-08 18:45       ` Mike Waychison
2004-06-05 14:00 Dimitry V. Ketov
2004-06-05 15:47 ` raven
2004-06-05 15:52   ` raven
2004-06-05 17:11     ` Robin Rosenberg
2004-06-05 17:49       ` Ian Kent
2004-06-05 20:13         ` Robin Rosenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40C49290.8060309@sun.com \
    --to=michael.waychison@sun.com \
    --cc=Dimitry.Ketov@avalon.ru \
    --cc=autofs@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.