Free Downloads, Community Forum,
FAQs and Developer Resources


Make /Tools Your Home | Link to us

Today's posts | Posts since last visit | Most Active Topics

All Forums Register Login Search Subscriptions My Profile Inbox
Tool Warehouse FAQs Resources Help Member List Address Book Logout

ssh_keysign ... Operation not permitted

 
Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [SFU / Interix / SUA Technology] >> Windows Server 2003 R2 SUA >> ssh_keysign ... Operation not permitted Page: [1]
Login
Message << Older Topic   Newer Topic >>
ssh_keysign ... Operation not permitted - Jun. 8, '06, 6:50:42 PM   
demyn

 

Posts: 34
Joined: Jun. 20, '05,
Status: offline
Hi ... I've setup ssh to login without a password. It works on one system,
but is very slow on another. Below, I'm ssh'ing from the slow system
to itself (no output to syslog):
$ ssh wiacdev
ssh_keysign: exec(/usr/local/libexec/ssh-keysign): Operation not permitted
ssh_keysign: no reply
key_sign failed
Welcome to the SUA utilities.

DISPLAY=localhost:0.0

Any ideas?

Thanks,
Demyn
Post #: 1
RE: ssh_keysign ... Operation not permitted - Jun. 9, '06, 2:27:27 PM   
Rodney

 

Posts: 3695
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
Slowness is usually attributed to lookups of users and/or groups.
So a slow connection to the domain server (e.g. AD) is usually the cause.
On this machine if you open a csh window does it take a while
before you get the shell prompt? I choose csh since it does more
lookups at startup than ksh and is thus easier to notice.

(in reply to demyn)
Post #: 2
RE: ssh_keysign ... Operation not permitted - Jun. 10, '06, 12:05:53 AM   
demyn

 

Posts: 34
Joined: Jun. 20, '05,
Status: offline
The ssh_keysign error and slow login (more than 10 seconds) occurs after
upgrading from openssh-4.3.0.2.1 to openssh-4.3.0.2.3.

Welcome to the SUA utilities.

DISPLAY=localhost:0.0
bash-3.00$ ssh wiacdev
Welcome to the SUA utilities.

DISPLAY=localhost:0.0
-bash-3.00$ exit
logout
Connection to wiacdev closed.
bash-3.00$ pkg_update -L -d openssh
Starting checks for updates
.Trying to add/update package openssh
pkg_add(openssh-4.3.0.2.3-bin): other version 'openssh-4.3.0.2.1-bin' already installed
pkg_add(openssh-4.3.0.2.3-bin): proceeding to install newer version
pkg_add(openssh-4.3.0.2.3-bin): proceeding to uninstall older version first
/usr/local/etc/ssh_host_key already exists, skipping.
/usr/local/etc/ssh_host_dsa_key already exists, skipping.
/usr/local/etc/ssh_host_rsa_key already exists, skipping.
/usr/local/etc/ssh_host_key already exists, skipping.
/usr/local/etc/ssh_host_dsa_key already exists, skipping.
/usr/local/etc/ssh_host_rsa_key already exists, skipping.
The Administrator can start SSHD directly.
You are a member of the Administrators group, not Administrator.
You can start SSHD by signaling init to stop and re-start all daemon processes.
Do you want to do this? (y/n)[n] y
Trying to start sshd daemon
Talking to the init process
Letting init process do some work
Talking to the init process again
Starting sshd daemon
Done.
bash-3.00$ ssh wiacdev
ssh_keysign: exec(/usr/local/libexec/ssh-keysign): Operation not permitted
ssh_keysign: no reply
key_sign failed
Welcome to the SUA utilities.

DISPLAY=localhost:0.0
-bash-3.00$

-- Demyn

(in reply to Rodney)
Post #: 3
RE: ssh_keysign ... Operation not permitted - Jun. 10, '06, 4:02:43 AM   
Rodney

 

Posts: 3695
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
Okay, one of the recent changes is to build a better token for the
key exchange (aka passwordless) logins.
For the user, on the target machine (machine to be logged into), run regpwd
to registry the user's password. This will allow the user network disk access
(which wasn't available before). See if that produces a difference.

(in reply to demyn)
Post #: 4
RE: ssh_keysign ... Operation not permitted - Jun. 12, '06, 4:27:18 PM   
demyn

 

Posts: 34
Joined: Jun. 20, '05,
Status: offline
Doesn't seem to change anything. One note: I only see the error messages when doing a local ssh -- ssh between systems is just as slow, but without the console errors.
bash-3.00$ regpwd
This program will save a password for user WIACDEV+gpfs
for use by privileged daemons and services like rlogind and cron.

Enter your current password:
Reenter your current password:
Password for WIACDEV+gpfs saved successfully
bash-3.00$ ssh wiacdev
ssh_keysign: exec(/usr/local/libexec/ssh-keysign): Operation not permitted
ssh_keysign: no reply
key_sign failed
Welcome to the SUA utilities.

DISPLAY=localhost:0.0
-bash-3.00$


-- Demyn

(in reply to Rodney)
Post #: 5
RE: ssh_keysign ... Operation not permitted - Jun. 13, '06, 3:22:19 AM   
Rodney

 

Posts: 3695
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
Do you have setuid enabled bythe registry on your system?
HKLM/SOFTWARE/Microsoft/Services for UNIX/EnableSetuidBinaries

(in reply to demyn)
Post #: 6
RE: ssh_keysign ... Operation not permitted - Jun. 19, '06, 8:33:47 AM   
demyn

 

Posts: 34
Joined: Jun. 20, '05,
Status: offline
Yes, setuid is enabled in the registry.

(in reply to Rodney)
Post #: 7
Page:   [1]
All Forums >> [SFU / Interix / SUA Technology] >> Windows Server 2003 R2 SUA >> ssh_keysign ... Operation not permitted Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Search All Forums -

Advanced search


SPONSORS



Forum Software © ASPPlayground.NET Advanced Edition 2.5 ANSI

0.031