This is the mail archive of the
mailing list for the Cygwin project.
Re: /bin/bash: Operation not permitted
- From: Aaron Digulla <digulla at hepe dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 11 Mar 2016 15:05:19 +0100
- Subject: Re: /bin/bash: Operation not permitted
- Authentication-results: sourceware.org; auth=none
- References: <60610071 dot 5233701 dot 1457534241961 dot JavaMail dot yahoo dot ref at mail dot yahoo dot com> <60610071 dot 5233701 dot 1457534241961 dot JavaMail dot yahoo at mail dot yahoo dot com> <loom dot 20160309T162147-290 at post dot gmane dot org> <56E042DD dot 2090804 at gmail dot com>
Am 09.03.2016 um 16:35 schrieb Marco Atzeri:
> On 09/03/2016 16:25, Achim Gratz wrote:
>> Francis Korning <fkorning <at> yahoo.ca> writes:
>>> Specifically, ssh-host-config needs these following lines:
>> The cyg_server account is actually set up in
>> /usr/share/csih/cygwin-service-installation-helper.sh and guess what, it
>> already does this. It also warns if a pre-existing account does not
>> these privileges enabled.
> It is correct Achim,
> however I have seen in corporate environment that some of those
> setting were removed by security scripts...at every boot.
How about a check in the code of sshd to make sure it has the necessary
I'm wondering if it would be better to do those check when it starts or
when someone logs in. The former would show the problem early but the
admin would have to look in the event log to see the error message
(especially after a reboot).
The latter would allow to send the error message to the local console
(local to the user, remote from the point of view of sshd) and there
would be a human who can read it.
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple