Over 1 million tech questions and answers.

XP OpenSSH

Q: XP OpenSSH

Hi,

I am trying to setup OpenSSH on XP and near the end I am getting kind of lost. I will post the tutorial and what I need help with below.
Tutorial: http://pigtail.net/LRP/printsrv/cygwin-sshd.html
8) important Pop a cygwin gwindow, harmonize Windows user information with cygwin, otherwise they cannot login
mkpasswd -cl > /etc/passwd
mkgroup --local > /etc/group

If your XP logs on to a domain, you most likely have to manually edit /etc/group. See this page.

If your XP logs on to a domain, you may want to edit /etc/passwd to replace /home/username by //unc_server/path_to_home
(thanks to Geoff Thomas)

mkpasswd creates a password file from Windows' user list, click here for more details.
mkgroup creates a group file from Windows' user list, click here for more details.
Thanks to John Skiggn of Cingular Wireless in Redmond, Washington for his tweak on domain user /etc/group
http://pigtail.net/LRP/printsrv/passwd-group.html

RELEVANCY SCORE 200
Preferred Solution: XP OpenSSH

I recommend downloading and running Reimage. It's a computer repair tool that has been proven to identify and fix many Windows problems with a high level of success.

I've used it in the past to identify and fix everything from blue screens (BSOD's), ActiveX errors, corrupt files and processes, dll/exe/sys errors, recover lost memory, Windows update problems, defragging, malware removal etc.

You can download it direct from this link http://downloadreimage.com/download.php. (This link will automatically start a download of Reimage that you can save to your computer.)

A: XP OpenSSH

What was the last step on the tutorial that you did? Also, is the PC you're using in a domain?

Read other 1 answers
RELEVANCY SCORE 48

ok Ive been studying this ssh service. Im running Fedora Core 3 and it is active on my machine...........or at least a "pgrep ssh and pgrep sshd" command show it running and the ssh daemon is listed as active in my list of active services.

My question is........if it is running on my linux box does the other windows boxes within my network have to be running it to connect to me?

If so or if not....how do I configure this thing? The information that I have found about it so far reads like stereo instructions in another language. I really need some help here!
 

A:openssh question?

If you post this in the Linux forum, you stand a better chance for an answer.
 

Read other 2 answers
RELEVANCY SCORE 47.2

Running Win XP MCE SP2
Cable connection
motorola surboard modem
linksys router

A few weeks ago I installed openssh on my computer using http://sshwindows.sourceforge.net/download/. I set up the group and passwd files, followed the instructions etc. Forwarded port 22 from my router to my computer and configured my firewall (zonealarm) to let traffic through. Everything worked fine until I screwed something up and had to format my hard drive. I've been trying to setup openssh the same way I did when it worked and I just can't get it to work. I've tried turning off the firewall and also connecting the modem directly to the computer, it just won't work. I have the user accounts setup with passwords. When i use putty to connect to my computer from that computer things work out but outside computers can't connect to it. I open putty, tell it to connect to my ip at port 22 using ssh and it brings up the connection window and asks me for a username, which I type in, and then it immiately asks for a password without showing the welcome/warning message it's supposed to show. When I type in the password, it tries to connect for a few seconds and then simply tells me "Access Denied".

Any suggestions? Any diagnostic tools or anything of that sort I can use to figure out what the problem is?
 

Read other answers
RELEVANCY SCORE 47.2

Hiya

There are two related vulnerabilities in the challenge response handling code in OpenSSH versions 2.3.1p1 through 3.3. They may allow a remote intruder to execute arbitrary code as the user running sshd (often root). The first vulnerability affects OpenSSH versions 2.9.9 through 3.3 that have the challenge response option enabled and that use SKEY or BSD_AUTH authentication. The second vulnerability affects PAM modules using interactive keyboard authentication in OpenSSH versions 2.3.1p1 through 3.3, regardless of the challenge response option setting. Additionally, a number of other possible security problems have been corrected in OpenSSH version 3.4.

Systems Affected

OpenSSH versions 2.3.1p1 through 3.3

http://www.cert.org/advisories/CA-2002-18.html

Regards

eddie
 

A:OpenSSH Vulnerabilities: June 27

July 02, 2002: Added Juniper Networks vendor statement.
July 02, 2002: Added Unisphere vendor statement.
July 02, 2002: Added Sun Microsystems vendor statement.
July 02, 2002: Added FreeBSD vendor statement.
July 02, 2002: Added Apple Computer Inc statement.

http://www.cert.org/advisories/CA-2002-18.html

Regards

eddie
 

Read other 3 answers
RELEVANCY SCORE 46.8

Hiya

The CERT/CC has received confirmation that some copies of the source code for the OpenSSH package were modified by an intruder and contain a Trojan horse.

We strongly encourage sites which employ, redistribute, or mirror the OpenSSH package to immediately verify the integrity of their distribution.

An intruder operating from (or able to impersonate) the remote address specified in the malicious code can gain unauthorized remote access to any host which compiled a version of OpenSSH from this Trojan horse version of the source code. The level of access would be that of the user who compiled the source code.

http://www.cert.org/advisories/CA-2002-24.html

Regards

eddie
 

Read other answers
RELEVANCY SCORE 46.8

I did a search, but didn't quite see anything posted that might relate to my problem.

At one point early last year I installed OpenSSH on an xp business box I have at home. I set it up so that it was an automatic server that would start when the box turned on. I used Putty on my laptop, and through port forwarding on my WRT54G v8 router, I had it all working perfectly and could connect using Putty on my laptop to have a tunnel to my home comp. Last week the hard drive died and I just bought a new one to put in it, and went through the process of re-installing XP. I then reinstalled OpenSSH, put in all the same settings as it had before (detailed notes from when I did it the first time) and fired up Putty and it wouldn't connect. I thought maybe it was the box, so I tinkered and tweeked to no avail. The only firewall I have running is the XP, and I added OpenSSH and it's ports to the firewall exceptions. The ports are forwarded correctly on my router, and everything in Putty looks ok. After still more timed out connections I opened the routers incoming log and noticed that there were no requests to the port I have OpenSSH set to. I thought that this was odd, as I also have PCAnyWhere installed, and it works perfectly, and I can see in the log the incoming requests for that. So now I am stumped. I have tried Putty on 3 different computers, using three different connections, and still nothing. Any ideas?
 

A:Solved: Windows OpenSSH Problems

Read other 7 answers
RELEVANCY SCORE 46.4

Hi folks,

today I setup Cygwin and OpenSSH on my rented server. I following the usual direction and everything seemed to be fine.

I tested locally using ssh localhost und voila - connection, login, everything fine.

Then I tried to login from my laptop and got no connection. I checked the firewall - and it was off. Both the server provider's firewall and the local windows firewall were off (I turned them on afterwards, however).

Ok, I thought, let's connect locally, so I tried ssh <hostname> and ssh <server-ip> (On the server itself!). Could not connect.

I tried a lot of combinations, changed the port, used ListenAddress to explicitly bind to the local ip, looked at hosts.allow and hosts.deny etc. Actually one can see slight differences with netstat -a, but the effect remains the same: Using localhost and 127.0.0.1 I can connect, but not using the IP.

Server OS is Windows Web Server 2008.

Any ideas?

Thanks for hints or any idea how I can debug this. SSH debug mode shows no output, so it really seems no connection gets established.

Regards,

JavaBird
 

A:Cygwin OpenSSH doesn't listen on actual IP, only on 127.0.0.1

Does the software have an option to change what ports it is listening on? Is their a check mark that you could of over looked that would cause it it only be listening on the loop back address?
 

Read other 3 answers
RELEVANCY SCORE 46.4

I have a problems with Win 7 Pro x86 where the Openssh SSD service is playing up


Symptoms

Task Manager:
Services Tab:

GGSMGR is running
MySQL is stopped (Right click | start - give access denied), need to start this

Services.msc
Openssh ssd status is blank, and right click is grey out

I need to get these running any ideas please?

I have restarted the PC and cold booted already, no changes same situation as above

Read other answers
RELEVANCY SCORE 46.4

Hi all 
I have one question regarding the distribution of updates for open SSH server feature. 
How the Microsoft is distributing the update for this feature ? In the microsoft windows there is still older version when I'm compare the current distributed open SSH server version.
Thank you for any info. 

Read other answers
RELEVANCY SCORE 45.6

OpenSSH chink bares encrypted data packets.

One in 262,144 chance = good odds

Important Note: If your system uses OpenSSH, make sure you are running the latest version (5.2) of it!

-- Tom
 

Read other answers
RELEVANCY SCORE 44.8

A security vulnerability found in a widely-used open-source software has been described as "the most serious bug."
A major vulnerability has been found and fixed in OpenSSH, an open-source remote connectivity tool using the Secure Shell protocol. The flaw was the result of an "experimental" feature that allows users to resume connections
According to a mailing list disclosing the flaw, a malicious server can trick an affected client to leak client memory, including a client's private user keys.
The affected code is enabled by default in OpenSSH client versions 5.4 to 7.1. The matching server code was never shipped, the mailing list said.
The flaw doesn't have a catchy name like some other previous flaws, but disabling client-side roaming support fixes the issue.
The flaw, which is said to be years old, was found by Qualys' security advisory team.
 
Wolfgang Kandek, chief technology officer at Qualys, confirmed in an email that the company disclosed the bugs to the OpenSSH team on January 11, and commended the team for working "incredibly fast" to get a patch out three days later.

"Developers and admins are advised to regenerate and rotate keys to systems they touch, whether for hobby [or] weekend projects, or more sensitive servers -- including Github," he added.
Bottom line? Patch now, and patch fast.

 
 

Article

A:'Serious' security flaw in OpenSSH puts private keys at risk:ZDnet

HeartBleed 2.0?
 
*Frantically checks all administered servers*

Read other 5 answers