From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Logging-in using ssh elevates the user privilege.
Date: Thu, 07 Mar 2019 10:08:00 -0000 [thread overview]
Message-ID: <20190307190805.db49864f5a7a9249d348842f@nifty.ne.jp> (raw)
In-Reply-To: <20190306161731.GA3785@calimero.vinschen.de>
Hi Corinna,
On Wed, 6 Mar 2019 17:17:31 +0100 Corinna Vinschen wrote:
> > This is by design, and this is no new behaviour. As soon as an admin
> > account logs in, seteuid uses the elevated token. Cygwin is doing that
> > since 2015.
>
> Actually, since 2010.
>
> > After all, from an ssh session there would be *no* chance to run
> > administrative tasks if the user would only get a non-elevated token.
> > There's no way to switch to the elevated token from an ssh session.
I understood. It seems better to remove administrator privileges
from users who are normally used, even under UAC feature.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-03-07 10:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 16:00 Takashi Yano
2019-03-06 16:15 ` Corinna Vinschen
2019-03-06 16:17 ` Corinna Vinschen
2019-03-07 10:08 ` Takashi Yano [this message]
2019-03-06 18:33 ` Achim Gratz
2019-03-07 11:23 ` Takashi Yano
2019-03-07 11:20 ` Andrey Repin
2019-03-07 15:35 ` Andrey Repin
2019-03-08 14:01 ` Takashi Yano
2019-03-08 14:11 ` Corinna Vinschen
2019-03-08 14:46 ` Takashi Yano
2019-03-08 14:52 ` Corinna Vinschen
2019-03-08 17:57 ` Andrew Schulman
2019-03-08 22:36 ` Takashi Yano
2019-03-08 23:19 ` Andrew Schulman
2019-03-09 1:49 ` Takashi Yano
2019-03-09 7:47 ` Michael Wild
2019-03-08 15:39 ` Takashi Yano
2019-03-08 15:56 ` Corinna Vinschen
2019-03-08 16:21 ` Takashi Yano
2019-03-08 17:14 ` Corinna Vinschen
2019-03-07 11:14 Takashi Yano
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=20190307190805.db49864f5a7a9249d348842f@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).