similar to: unsubscribe this service

Hi all, I try to implement a secure ODBC connection via ssh tunnel from a win-pc to a linux server. I am looking for a kind of service under nt that builds a secure tunnel connection from the pc to the server at time of login of the user at the desktop and going into the background after that. That means the conncetion is always open until the user shuts down the pc. It should run completely in

Hi, the following patch is a (hopefully least intrusive) extension when sshd is started so that it daemonizes itself. In that case Windows 9x/Me has a slight problem with sshd as soon as the current user logs off. The sshd daemon will be killed as well. Since installing services is very different between NT and 9x, the way used for NT boxes isn't working well for 9x. For that reason

Stephan Hendl wrote: >Darren Tucker wrote: >> The first part should be easy: use cygwin openssh client using some kind >> of passwordless authentication (eg RSA). >> >> To make it run entirely in the background, run it from cygrunsrv (part >> of Cygwin) or SRVANY (NT resource kit). Neither of these work on W95, >> only NT or W2K. > > How does the

I'm sorry to bug you guys but when I tried to install the sshd service it didn't work. I'm running the newest build of Cygwin with Openssh and cygrunsrv on windows 2000. The configuration file was supposed to register sshd as a service but the service couldn't start! It was supposed to but it DIDN'T!!!!!!!!!!!!!!! I got instructions that were supposed to work from

Please take me out of your member list. Thank you. Best regards, Mary. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20020423/6d63516f/attachment.html

https://bugzilla.mindrot.org/show_bug.cgi?id=2244 Bug ID: 2244 Summary: The OPENSSH service has not been started after installed on windows 8/windows 2012 Product: Portable OpenSSH Version: 6.0p1 Hardware: Other OS: Other Status: NEW Severity: critical Priority: P5

davidl@cn.ca wrote: > A "service" on an NT 4 server cannot connect to a samba > share on my linux machine. The specific versions are given > below. From the NT machine I have no problem as the administrator > to login to samba server and view the target share. The > supplier's service however cannot seem to do the same. The > service does have a config

Hi, I have a client on a Windows machine that connects through openssh on a linux server. I have this script (tunnel.cmd): @echo off :RUN echo Connecting? "C:/Program Files/OpenSSH/bin/ssh.exe" -R 40201:localhost:50300 -o TCPKeepAlive=no -o ServerAliveInterval=15 -o ServerAliveCountMax=2 -i id_rsa visma at 10.55.40.123 echo Restarting in 10 seconds? GOTO RUN It is runned from another

Currently, openssh's PAM service name is a compile-time choice. That's fine when one uses one sshd to serve normal shell logins and the like. But this will not work IF sshd is nor run as root (which I don't want it to do), because pam_open_session usually requires access to one's shadow information (for account expiration perhaps?), and there is no way (and need: this sshd is

Hello. Which pam service is sshd using on Solaris? Is it sshd? Thanks, Alexander Skwar -- Message from Our Sponsor on ttyTV at 13:58 ...

Hi, could somebody with checkin rights please apply the below patch to the Cygwin service creator script? It patches a problem when using an existing account to start the sshd service. In that case the script so far doesn't make sure that the user has th right to logon as a service. Index: contrib/cygwin/ssh-host-config ===================================================================

Hello All, The attached patch allows openssh to specify which pam service name to authenticate users against by specifying the PAMServiceName attribute in the sshd_config file. Because the parameter can be included in the Match directive sections, it allows different authentication based on the Match directive. In our case, we use it to allow different levels of authentication based on the

Hi SAMBA, This is not quite a remark on SAMBA, more a report of a problem that is not related to SAMBA. However it could be of concern to your developers team. At our company we recently (last week) installed two new fileservers. The next thing we got was a very strange effect. The configuration: - Two fileservers, running (i believe) Windows 2000, with service pack 6A and included all service

Hi All - It seems to be an odd scenario. I have a simple ssh command which establishes connection with a UNIX machine and executes some commands over there. When I ran the command from command window, I was able to successfully run them. In reality I wanted the ssh command to be invoked by a windows 2003 service. I tried to debug the ssh command while running from a service and I get the below

The attached patch enables specifying the PAM service name in the sshd_config file. It requires an entry similar to the follows to be added to the configuration file- PAMServiceName MyFavoriteServiceName If this option is not specified, the default scheme of picking up the service name from the application name will be in effect. Thanks, Santanu -------------- next part -------------- A

Hi, the below patch is necessary for the contrib/cygwin/ssh-host-config script to work on Cygwin 1.5.x as well as on the new Cygwin 1.7.x. The information given for the setting of the CYGWIN environment variable is wrong for both releases so I just removed it, together with the unnecessary (Cygwin 1.5.x) or wrong (Cygwin 1.7.x) default setting. Could somebody with checkin rights please apply

I've attached a patch relative to OpenSSH 2.5.1p1 which sets the default PAM service name to __progname instead of the hard-coded value "sshd". This allows you to have multiple invokations of sshd under different names, each with its own PAM configuration. Please let me know if you have any questions or problems. -- Mark D. Roth <roth at feep.net> http://www.feep.net/~roth/

Microsoft hijacked the sshd service name without asking. --- contrib/cygwin/ssh-host-config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/cygwin/ssh-host-config b/contrib/cygwin/ssh-host-config index 2903125f8592..52916d14ba94 100644 --- a/contrib/cygwin/ssh-host-config +++ b/contrib/cygwin/ssh-host-config @@ -61,7 +61,7 @@ LOCALSTATEDIR=/var

It's sometimes desired to be able to alter login policy depending upon how the person was connecting for the ssh server. For example you might want different rules on the internal and external interface of a gateway. In another setup you might want an sshd with a different login policy running on a different port - and setup different firewalling rules (for example). I have implemented such

Hi, Cygwin only: Under some circumstances, the sshd service gets accidentally started *before* the network service has been started up. The reason that this can happen is, that the sshd service gets installed without a dependency to the network service in contrib/cygwin/ssh-host-config so far. The below patch fixes that by adding a dependency to the "tcpip" Windows service. This