public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: michael pitoniak <pitoniakm@msn.com>
To: cygwin@cygwin.com
Subject: /bin/bash: Operation not permitted
Date: Tue, 21 Aug 2012 17:37:00 -0000	[thread overview]
Message-ID: <loom.20120821T162855-284@post.gmane.org> (raw)

greetings,

 i have a really strange problem...i install the latest cygwin release
1.7.16(0.262/5/3) with the openssh option and configure it with ssh-host-config
on a 64 bit windows 7 system...it works perfectly for one day...allowing for
putty access after reboots and log in/out...yet when i come into work the next
day i can  log in via putty but instantly get thrown out with:

/bin/bash: Operation not permitted error.

attached is a debug trace of $ssh -vvv localhost -l michael.pitoniak that fails.

i suspect it has something to do wit anti virus software of public kyes...any
suggestions on how to further debug greatly appreciated...passwd files look the
same...really stumped here...

many thanks,

mp



michael.pitoniak@Pitoniak-wkst2 ~
$ ssh -vvv localhost -l michael.pitoniak

......


debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
Last login: Tue Aug 21 08:45:12 2012 from ::1
/bin/bash: Operation not permitted
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug2: channel 0: obuf empty
debug2: channel 0: close_write
debug2: channel 0: output drain -> closed
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
debug2: channel 0: rcvd eow
debug2: channel 0: close_read
debug2: channel 0: input open -> closed
debug2: channel 0: rcvd close
debug3: channel 0: will not send data after close
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
  #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1)

Connection to localhost closed.
Transferred: sent 2168, received 1840 bytes, in 0.2 seconds
Bytes per second: sent 11976.7, received 10164.7
debug1: Exit status 1


--
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:[~2012-08-21 16:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 17:37 michael pitoniak [this message]
2012-08-22  0:11 ` Larry Hall (Cygwin)
2012-08-27 15:08   ` michael pitoniak
2012-08-28  6:31     ` Larry Hall (Cygwin)
2015-08-11 11:45 stephane
2015-08-12  8:16 ` stephane
     [not found] <60610071.5233701.1457534241961.JavaMail.yahoo.ref@mail.yahoo.com>
2016-03-09 14:37 ` Francis Korning
2016-03-09 15:26   ` Achim Gratz
2016-03-09 15:36     ` Marco Atzeri
2016-03-11 14:05       ` Aaron Digulla

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=loom.20120821T162855-284@post.gmane.org \
    --to=pitoniakm@msn.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).