public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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 11:23:00 -0000	[thread overview]
Message-ID: <20190307202253.1a0ce6380e57cae2754e2334@nifty.ne.jp> (raw)
In-Reply-To: <87ftrz6efm.fsf@Rainer.invalid>

Sorry, the message bellow accidentally lost the references.

On Thu, 7 Mar 2019 20:14:39 +0900 Takashi Yano wrote:
> On Wed, 06 Mar 2019 19:33:17 +0100 Achim Gratz wrote:
> > 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.
> 
> Thank you for your reply. I had tried cygdrop, and confirmed that
> the problems below cannot be solved by cygdrop.
> 
> But I don't understand why...
> 
> On Thu, 7 Mar 2019 01:00:00 +0900 Takashi Yano wrote:
> > Because of this behaviour, the process started in a ssh
> > session cannot be killed from a normal mintty session.
> > 
> > This also causes gnu screen to freeze.
> > 
> > To reproduce this:
> > (1) Start screen in mintty window.
> > (2) Detatch from the screen (Ctrl-A d).
> > (3) Login via ssh.
> > (4) Attach screen by 'screen -r' in ssh session.
> > (5) Detach from the screen (Ctrl-A d).
> > (6) screen freezes and is not terminated normally.

-- 
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

  reply	other threads:[~2019-03-07 11:23 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
2019-03-07 11:23   ` Takashi Yano [this message]
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=20190307202253.1a0ce6380e57cae2754e2334@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).