public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Maayan Apelboim <Maayan.Apelboim@clarizen.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: can't access remote shares when using ssh with rsa key - passwd -R / set(e)uid / LogonUser is not working as expected
Date: Thu, 14 Mar 2019 10:41:00 -0000	[thread overview]
Message-ID: <AM6PR07MB533433E14C36CC4D12E7EA86954B0@AM6PR07MB5334.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <20190313090418.GT3785@calimero.vinschen.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1766 bytes --]


When you login with stored password, Cygwin performs the same LogonUser call as if you login with password, so the same user token is generated.

Off the top of my head I don't know why it shouldn't work for you.  You sure you have the correct password stored?  When you login and call `id', what does it print?  Does it contain the "interactive" group or the "network" group?  If the latter, then the internal LogonUser call performed with stored password failed for some reason.


Corinna

--
Corinna Vinschen
Cygwin Maintainer

---------------------------------------------------------------------------------------

Yes, I'm sure I used the correct password, I use it all the time and I also tried running passwd -R multiple times in case I entered it wrongly.
I'm not sure what are "interactive" & "network" groups - do you mean literally groups called network & interactive?
Either way - I'm always getting a group named "interactive" among other groups - either with password ssh or with RSA - never "network"
I do have some different groups when running id - comparing password ssh and RSA ssh.
Also, when I run mkpasswd -d when I log in with password, it generates users from the domain, comparing RSA ssh that generates only a few entries unrelated to my domain..

I think the same as you (also mentioned in the email title :) ) that the LogonUser call doesn't work as expected. Is there a way to verify it? Any logs I can check?
Would it help if I'll send the different groups I'm getting?

Thanks!
 
\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

  reply	other threads:[~2019-03-14 10:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AM6PR07MB5334CE88B67F5421BA671C43957B0@AM6PR07MB5334.eurprd07.prod.outlook.com>
2019-02-26 13:39 ` Maayan Apelboim
2019-02-26 15:33   ` Andrey Repin
2019-02-26 18:00     ` Houder
2019-02-27  1:17       ` Andrey Repin
2019-03-05  8:19         ` Maayan Apelboim
2019-03-05 19:27           ` Achim Gratz
2019-03-06 10:09             ` Maayan Apelboim
2019-03-06 12:28               ` Corinna Vinschen
2019-03-06 12:35                 ` Corinna Vinschen
2019-03-13  8:32                 ` Maayan Apelboim
2019-03-13  9:04                   ` Corinna Vinschen
2019-03-14 10:41                     ` Maayan Apelboim [this message]
2019-03-14 11:11                       ` Corinna Vinschen
2019-03-18 13:53                         ` Maayan Apelboim

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=AM6PR07MB533433E14C36CC4D12E7EA86954B0@AM6PR07MB5334.eurprd07.prod.outlook.com \
    --to=maayan.apelboim@clarizen.com \
    --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).