From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Logging-in using ssh elevates the user privilege.
Date: Wed, 06 Mar 2019 18:33:00 -0000 [thread overview]
Message-ID: <87ftrz6efm.fsf@Rainer.invalid> (raw)
In-Reply-To: <20190307010000.fc28b73739c2dd66e609982b@nifty.ne.jp> (Takashi Yano's message of "Thu, 7 Mar 2019 01:00:00 +0900")
Takashi Yano writes:
> I would like to report a problem of recent cygwin.
>
> If a user logs in via ssh, the user aqcuires the elevated
> privilege if the user belongs to Administrators group.
This has been the case for as long as I use ssh logins and is by design.
You can drop privileges after logon (see cygdrop), but not aquire new
ones.
So if that's changed behaviour for you, then your ssh logins didn't
actually work the way you thought they were.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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-06 18:33 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
2019-03-06 18:33 ` Achim Gratz [this message]
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=87ftrz6efm.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).