I'm using putty to access linux bash. I have overwritten the "Default Settings" with some modification.
How can I set the defaults back to the original?
I found a solution with regedit.
All sessions are in the registry under:
Computer\HKEY_CURRENT_USER\SOFTWARE\SimonTatham\PuTTY\Sessions
There I delete the session "default%20settings".
Locate where putty.exe is installed. Open command prompt. Type putty.exe -cleanup
Thats it
Related
I'm facing strange issue with WinSCP: It works well and I'm able to connect to remote hosts. But when I try to use the "Open session in PuTTY", instead of logging me directly with same credentials, PuTTY gets "stuck", prompting me to "login as".
I've checked the config in WinSCP and it looks fine: "Remember session password and pass it to PuTTY" is ticked.
What else should I check?
I'm using WinSCP 4.2.7 and PuTTY 0.60.3.
As documented:
By default, WinSCP creates temporary site settings for PuTTY (under the name "WinSCP temporary session"). The site settings will contain only the options known by WinSCP, mostly connection options. It will particularly lack any terminal options, so the defaults (Default Settings profile) will apply.
If you want to configure your own options, you can save PuTTY site settings with the same name as a WinSCP site. WinSCP will then instruct PuTTY to open that session (It will not export any settings, nor a connection options).
So if you have an invalid stored session in PuTTY with the same name as your WinSCP stored site, the "Open in PuTTY" function won't work, as it tries to open that invalid site.
Side note: You are using an obsolete and insecure versions of WinSCP and PuTTY. You urgently need to upgrade!
WinSCP is somehow looking into PuTTY saved sessions that are configured. I had a saved session in PuTTY with same name as in WinSCP ("myApplication - integration"). Somehow, when the session already exist in PuTTY, WinSCP is not able to log me in directly to PuTTY.
I deleted the saved session from PuTTY, and it worked: now WinSCP logs me in directly in PuTTY. And now I see a "WinSCP temporary session" in the list of saved session in PuTTY.
We need provide putty path
Right click the putty icon in WinSCP then go to Queue -> Customize -> Application
then provide your putty.exe path using browse button
then click ok
Now click the putty icon button from WinSCP, Putty will open automatically :)
In WinSCP Go to :
preferencce - > integration -> application
under "putty/terminal client path" add this line :
%ProgramFiles%\PuTTY\putty.exe -t -m "%TEMP%\putty.txt" !cmd.exe /c echo cd '!/' ; /bin/bash -login > "%TEMP%\putty.txt"
I have installed Microsoft Remote Desktop 8.0.5 For MAC OSX 10.8.5 and added new remote connection in the list which works fine.
Now i export same connection to .rdp file but when i execute it mstsc opens remote os login screen and asks for user password to login (which is already in keychain store).
how can i launch .rdp file so that it will not ask remote user password?
where/how to store password?
------- .RDP File ----------
screen mode id:i:0
use multimon:i:1
session bpp:i:32
full address:s:192.168.1.130
audiomode:i:0
username:s:mylabs\administrator
disable wallpaper:i:0
disable full window drag:i:0
disable menu anims:i:0
disable themes:i:0
alternate shell:s:
shell working directory:s:
authentication level:i:0
connect to console:i:0
gatewayusagemethod:i:0
disable cursor setting:i:0
allow font smoothing:i:1
allow desktop composition:i:1
bookmarktype:i:3
use redirection server name:i:0
Thanks in advance
This article helped me
https://serverfault.com/questions/962628/failure-connecting-to-a-cyberark-managed-server-using-macos
Use Microsoft RDP Client for Mac starting from version 10.2.2
Run the following command on the Mac Terminal
defaults write com.microsoft.rdc.macos ClientSettings.EnforceCredSSPSupport 0
Close terminal and try to connect
I can't seem to get the NppFTP plugin to connect to my localhost (via XAMPP) for local development using Notepad++.
According to the http://localhost/xampp/ docs, the default username and password are 'newuser' and 'wampp' accordingly.
I'm using these settings:
host: 127.0.0.1
port: 21
username: newuser
password: wampp
initial remote directory: C:/xampp/htdocs/myrootdirectory
The console just says 'Quit' right after I try and connect.
Anyone know what I'm doing wrong? And if it's because localhost is not a remote directory, how do I configure Notepad++ to browse my local files without relying on Windows Explorer?
If you're running on windows, make sure you're running your xampp control (xampp ui ) as admin. Then, you have yo check SVC checkbox before filezilla then click start. A pop-up will prompt and click Yes to install it as a service.
after that, click admin then click Yes. set you password then you're good to go.
In you're notepadd++, the settings are the same with the one you posted above.
Hope that helps.
Raul
Actually, it doesn't make sense to Filezilla into your localhost, you should just use the Notepad Plugin, Explorer.
I'm setting up a "data analysis on the cloud" class and most of the students will probably be using Windows.
The students will have to set up EC2 Ubuntu instances and connect to them.
What is the easiest way to set up SSH for Windows XP-7?
I've tried PuTTY but Puttygen can only convert the public key to putty format if I manually add newlines in a text editor. This is too involved for the class of 80.
I've tried OpenSSH but I can't seem to find the correct permissions for the public key file. On Mac OS/Linux it's just chmod 600.
Is there a decent SSH client that supports Amazon's key format that I can set up easily?
The .pem file Amazon Web Services gives you is supported by the openssh client implementations, but for a Windows-based client that works directly with the .pem file without converting it with puttygen.exe, look into Bitvise Tunnelier.
If anybody's looking for windows 10 solution.
In Windows 10, you can use powershell.
Use below command.
ssh -i \..\location-to-pem-file.pem ubuntu#X.X.XXX.XXX
If ssh is not supported in your windows 10 machine, follow this url for installation.
I used it and suggested the same.
Another possible solution is to use PuTTY but follow Amazon's guide for doing so. I found some other guide's that weren't as clear in the steps but I was able to get PuTTYgen to work correctly when I used their guide.
Install PuTTY.
Follow Amazon's guide for converting your PEM file to the PuTTY PPK format.
Connect to your server!
As for newlines, maybe you need to run unix2dos or some other program that will fix that for you?
Step1: Download the keypair
The download will create a .pem file on your local system. It contains a private key that you can use to connect to the EC2 instance via SSH
Step 2: Launch your linux instance
Copy the public ip address for the future use to connect the linux instance
Step 3: Download puttyGen from https://the.earth.li/~sgtatham/putty/latest/w32/puttygen.exe
Step 4: Execute the PuttyGen exe and load the private key(the pem file you have downloaded while launching the instance)
Step 5: Save the private key, it will give the .ppk file which will be used to connect the linux instance
Step 6: Download and install the Putty software, open the putty, and paste the public ip address which you copied from the linux instance
Step 7: Now load the .PPK file which we have saved
Step 8: Choose yes from the alert window
Step 9: Login as ec-user
I borrowed the method giving in this video. https://youtu.be/P1erVo5X3Bs
Open power shell and run below commands. You can open power shell at any location by print powershell in the nevigation bar and press enter.
enter image description here
1.reset premission:
icals.exe key.pem /reset
2.check the current user id
whoami
3.add permision to specific user id
icacls.exe key.pem /grant:r "YOUR USER ID GIVEN BY WHOAMI"
4.remove permission of other user
icacls.exe .\ec2.pem /inheritance:r
Now it should work.
If anybody's looking for windows 10 solution.
icacls.exe .\Desktop\xxxx.pem /reset
icacls.exe .\Desktop\xxxx.pem /grant:r "$($env:USERNAME):(r)"
icacls.exe .\Desktop\xxxx.pem /inheritance:r
ssh -i .\Desktop\xxxx.pem ec2-user#54.229.xxx.x
So on my friends local Windows machine we are trying to setup GIT.
Basically, we've been following this guide which has been great. The problem we are facing is as follows:
All works until we get to Using Gitosis
When we use the command
git clone
git#INSERT_IP_HERE:gitosis-admin.git
We keep getting
Initialized empty Git repository in
/home/Thomas/gitosis-admin/.git
Connection closed by IP_HERE fatal:
The remote end hung up unexpectedly
When we try simply
ssh git#IP_HERE
We get "Connection closed by IP_HERE"
If we login as
runas /user:git C:/cygwin/cygwin.bat
And run > ssh git#IP_HERE
We at least get asked for a password then
Last Login: Connection to IP_HERE
closed.
Would anyone be able to help ?
The error does indeed indicate that authentication is failing.
Firstly, open gitosis.conf on the server and check that you are a member of the group containing gitosis-admin repository. It should show something like.
[gitosis]
[group gitosis-admin]
writable = gitosis-admin
members = user1 user2
The member name must match with a public key in /keydir before access can be made.
Secondly, you do not say how you are connecting from the Windows machines. If you are using Git under Cygwin, make sure you are correctly loading the private key. If you are using MsysGit with Putty, be sure to load the private key before connecting as well.
There is a small gotcha if PuttyGen is used to generate key pairs, and that is the default format is different from OpenSSH which you are probably using. Copy and paste from the top window, or alternatively edit the multiline public key file to read like this.
ssh-rsa AAAABB...KEYBODY...ONLkQ== user1
Lastly, make sure port 22 is open in any firewalls if that is indeed the port you are using.
A more comprehensive description of how to set up a Git server with Gitosis on Windows, can be found at here
I recommend the use of MsysGit from windows, as it gives better integration into the Windows environment. TortoiseGit and GitExtensions both use MsysGit as the backend, and provide nice Gui's and explorer shell extensions. GitExtensions full installer will provide the windows user with everything they need.
Did you get past runnig the gitosis-init < /tmp/id_rsa.pub command?
That error indicates to me that the public key isn't set up properly. The command above initializes gitosis with the first key.