SSH To Windows Using Public Key 

Yes it's not a simple process. Was some work just to figure out best way to describe all of that without making it more confusing. Great to hear that effort was successful.

I'm glad it helped. Thank you for the feedback.

Exactly, I am having same problem, definitely I will try this, thanks

Is it bad to use authorized_keys under the Administrator user's .ssh folder?

Thank you for the kinds words. Good to hear the effort put in the video helps others.

Great to hear. I'm glad it helped.

Awesome! I'm glad it helped. Any other topics, leave a comment. I'm always looking for ideas for new videos. Thanks!

Good to hear. Thanks for watching.

Thank you! That inspires me to make more similar content. Any suggestions for topics I should cover?

Thanks. Glad it helps.

Great to hear. Thanks for watching.

Yes I encountered this with a German user. The value here is whatever name your system uses for the Administrators group. This can be determined by opening Computer Management (a number of ways, for example, right-click Start menu and select in fly-out menu), then in section "Local Users and Groups", look inside the "Groups" section. In English systems it is second item "Administrators". Look here for your variation. Use that in the command.

Nice. Thanks.

Great! Glad I could help.

Great! Thank you!

You're welcome. I'm glad to help.

Glad it helped.

Good to hear it works for you. Thanks for watching.

Thanks

You are welcome, and thanks for the + on clarity. I am glad it helps.

And I found this method might only work with rsa key instead of dsa key

Great. I'm glad it helped.

Thanks. Glad you like like it.

You're welcome. Thanks for watching.

Glad it helps. Thanks for watching.

Thanks.

You're welcome. Thanks for watching.

Great. I'm glad it helped.

Thanks

Great. I'm glad it helps.

You are welcome. Glad it helps.

Glad to help.

Great. I'm glad it helps.

Glad it helped!

I'm glad it helps. Thanks for watching.

It is possible. You would have to open port 22 on your router, and forward it to your Windows machine, which would also have to allow connections on the port. HOWEVER, I would strongly recommend using a different port number. Everyone (every hacker) knows what port 22 is for. Set your router and your Windows SSH server to something in the range 12000-14000 (usually safe to use). Just pick at random, say 12533 (for example; pick your own). Only you know that is the correct port. It's safer that way. Chances of someone guessing your obscure port number are low.

I do not.

Thank you! Is there any other subject I should make a video? All suggestions are welcome.

@@wc7 welcome, can I copy Linux public key and copy in the windows

@@vetriforward6819 Yes, that is possible. It does work. But the typical use is to have each client have its own private key, different from others. At least, that seems to be the recommended method. But I have done what you describe, and it does will work.

You're welcome. Thanks for watching.

Thanks.

A Debian host isn't required, but to test you need something else besides the Windows host, from which to connect to the Windows host. For that I used a Debian virtual machine as the other computer. It could be another physical computer or laptop, whatever is on the same network. Public/private keys can be generated in Windows or any flavor of Linux.

I had the same problem. I started the video thinking the instructions were for two different platforms, and I was just following the Windows instructions. Would be helpful if this was done with two windows laptops.

I don't what it means to comment out match group administrators, etc. Are you referring to lines in the sshd_config file? Regardless, if another suggest commenting something to disable it, OK maybe that's a good suggestion. I have no idea. I can only relay what I have found to work, which is the content of the video. I'm sure there's plenty more to it that I don't know. About using a password, keep the line "PasswordAuthentication" set to "yes".

Not sure. I have only tried this on Windows 10 but I don't see why it would be different on Server. See if you can find any logs. Should be in "%programdata%\ssh\logs\" Look for auth.log. Maybe in Event log security also. Either might have a more specific reason authentication fails.

Run keygen to make id_rsa and pub. Watch video again. Pay close attention at 4:30 to 5:10

It is difficult for me to help knowing so little about your configuration. My first advice would be to ensure your account is an Administrator. And be sure to follow the steps explained in the video about how that is a different file to edit than regular users (I can't imagine giving non-admin users SSH access, so I didn't bother to include that). I'm not sure what you mean by "clone" in your comment. Perhaps back up your current key (if you have an existing one you're trying to preserve) then do ALL steps in the video, including generating a fresh key file. Beyond that I don't know how much more I can help without being there.

Follow the steps in the video and it should work. Unless you're not an admin user. I wouldn't recommend that anyway. To reach me by email, start at my website contact page: www.marspremedia.com/contact/

@@wc7 thanks for your response. The problem happens to be I logged in to my computer with my Microsoft account. It worked when I logged in locally

@@yonite4355 Great. I'm glad to hear it worked out. Thank you for responding. It may help others users who have the same problem.

Just like it says. You need admin permissions. I mentioned this at the start. Log in as Administrator or add your user account to the Administrators group. Windows 10 right-click Start menu, Computer Management. In Section Local Users and Groups, find the user account, right-click properties, Member of tab, add the Administrators group.

Copy the same .pub file to both servers.

There is no password. The public/private key pair acts as the password. That's the point. But if you set a passphrase during key generation, you are prompted to enter that, similar to a password. Only you know that passphrase, if one was set.

I don't know. I don't use WSL so I'm not sure, but there shouldn't be any reason it wouldn't work the same it does with an actual server or virtual machine. As for the problem, please be more specific. "It's not working" is vague. What isn't working?

Great! Good to hear it.

I have no idea what a "vagrant" user is, other than by its definition, a person without a home. Not sure what that means in relation to a computer systems user account.

I came across an automation tool called Vagrant for managing multiple Virtual machines thank you for the meaning 😆

@@srinath8626 OK. I am not familiar with the product so I can't answer your question. I don't know an answer any better than you do. You need to pick the brain of someone familiar with the VM hosting product.

This video is the other way around -- ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-ORks4JXxJp0.html If you have already made a key pair in Windows, skip the part about running keygen. Do all the rest as the video describes, just not keygen, or it will replace your current key, which then breaks any other SSH you had previously set up. All the rest is OK, just don't run keygen again. Unless you want to start clean with a fresh key. Then follow the video instructions for that part too.

Hi @@wc7 Thanks for the reply.

the password for the user at the server you want to access

User name and password for Windows user account on the server.

@@wc7 i see, thank you so much for the info and fast reply. you got a new subscriber :D

@@zxcvbqwerty2091 Awesome. Thanks for watching.

Giving regular users SSH access is not recommended, likely why there are no videos showing how to do it. This does not mean access is limited to the user "Administrator" or "root". Other users may be given access. They just have to be members of the Administrators Group.

@@wc7 So only admins can be ssh’d into on windows?

@@thenewone3944 Any user can be given SSH access. But that level of access SHOULD only be given to admin users.

@@wc7 I can’t figure out why it’s not working for me. It’s so much easier with linux. I’ve got the pub copied into the users authorized_keys, Modified sshd_config, checked permissions.

Thanks. I'm glad you like it. Suggestions for other topics are always welcome.

If there are no currently installed optional features, I would question if your Windows install is valid. There are usually at least a few items already installed. If typing "ssh" in the search input does not show "OpenSSH Server" then again I suspect something is wrong with the installation of Windows. Are you connected to the Internet? Are all latest updates installed? What version of Windows?

There must be a user account with the same credentials on the Windows server hosting SSH server.

@@wc7 So the User needs to have an Microsoft account?

@@dwd_0105 No. Just a regular user account, like any Windows machine. What is used to log in to Windows. The server may have other credentials, perhaps "Administrator" but for a regular user to get access to the server, they need a user account on the server. It doesn't have to be, but usually it's the same credentials as the user logs in to their own Windows box. That's how I do it when adding users to give them access to a server.

What version of Windows? Also, be sure when searching use OpenSSH one word, not Open SSH two words. That won't match. That's why I suggest simply search for SSH and that usually finds it.

@@wc7 Windows 10 pro 1703, I tried to look for OpenSSH still nothing. Thank you very much for response

@@ylyaskudratullayev Your version of Windows is out of date. OpenSSH Server wasn't added until the October 2018 version 1809. You have Fall 2017 version. Run Windows Update.

@@wc7 Thank you very much!

Hard to say why from a distance. My first guess is the user trying to log in isn't an Administrator.

I have the same requirement to do ssh from linux to windows but with non admin user account. Can you please tell me how to do this. Admin account ssh is working fine as i tried that with your video.thanks in advance

Either the user doesn't exist on the host server, or the user has a different password. Also ensure the user on the host server is an administrator (user is in the Administrator group).

It's the password for the Windows user name you enter on the command line. If doing this like the video, on your local Windows machine, it's your regular Windows account user name, and the same password you use to log in to Windows. If the Windows box you're trying to contact is another machine, it's the user name password on that box. To SSH to Windows, the server needs an account defined that you use to log in with. The user name and password on the command line is that account's user name and password.

I choose not to make hour long videos, and can only fit so much. The topics I choose to cover are driven by viewer demand. If enough ask for the additional you describe, perhaps I'll make a video about that also. Thanks for watching.

I understand; perhaps you could include such references in the notes section.

Windows password is your Windows user password. Password on SSH server password for that user on the SSH server. Could be the same, that's up to you how you set up your network. Mine I make the same for Windows file sharing to work without having to put in a password every time.

@@wc7 that is problem because i didnt put any password

No I don't have any courses. Most of my tutorials are for Adobe Scripting using JavaScript. I don't do a lot of system admin videos. Just once in a while for things I had to figure out how to do myself, so I thought to share.

Works the same. Just substitute the Debian console with a Windows Terminal console.

@@wc7 Thank you. Can you make a Contabo VDS and SSH video?

@@cizgifilmkolikcizgifilm1963 I can only make videos about topics I know.

Use credentials for a user on the target server. If you don't yet have a user on the target server, add an account with password on the target server. Use those credentials.

The Windows user account password.

@@wc7 does not work here either... the windows user account password is just not accepted

@@jamilsonjunior284 Does the user have an account on the server? There must be a user account with admin permissions on the server hosting SSH server that matches the credentials trying to log in.

OK

Command line begins around 3:40 after the server is installed.