From Newsgroup: rec.sport.rowing

<div>If you cannot authenticate to the server and use Windows 10 Developer mode, make sure that your OpenSSH server does not conflict with an internal SSH server used by the Developer mode. You may need to turn off the SSH Server Broker and SSH Server Proxy Windows services. Or run your OpenSSH server on a different port than 22.</div><div></div><div></div><div></div><div></div><div></div><div>download winscp for windows server 2008 r2</div><div></div><div>Download File: https://t.co/B8nIjCV0PQ </div><div></div><div></div><div>I created the key on the local machine using PuTTYgen (RSA 2048) and added it to the server's authorized_keys file (I used the feature in WinSCP to do this automatically) for my user (not a local admin) in the same location as specified in the sshd_config file (C:\Users\\.ssh).</div><div></div><div></div><div>I removed all permissions for all other accounts on this folder and the authorized_keys file. I tried setting the logging to verbose on the server but there doesn't seem to be much to go on, just "Failed none" followed by "Failed publickey".</div><div></div><div></div><div>Using WinSCP, you can connect to an SSH (Secure Shell) server with SFTP (SSH File Transfer Protocol) or SCP (Secure Copy Protocol) service, to an FTP (File Transfer Protocol) server, HTTP server with WebDAV service or store system with S3 protocol support.</div><div></div><div></div><div>SFTP is a standard file transfer protocol supported by most SSH servers. SCP is legacy protocol, supported mostly by OpenSSH and some other servers. For authentication, you can use user name and password or public key. Other authorization types include Keyboard-interactive, and Kerberos.</div><div></div><div></div><div></div><div></div><div></div><div></div><div>As the SCP protocol implements file transfers only, WinSCP must use other means to implement the additional functionality (like directory listing). WinSCP uses Unix-like shell commands to do that. This in turn means that when using the SCP protocol, it can connect to servers that run Unix-like or its emulation only.</div><div></div><div></div><div>To transfer files, scp1 is used (it is called from within scp). If only scp2 is allowed on your server, check the Use scp2 with scp1 compatibility option on the SCP/Shell page on the Advanced Site Settings dialog.</div><div></div><div></div><div>Another precondition is that the output of all commands be in English. This mostly concerns names of months in directory listings (ls -la). Because of this, WinSCP clears all user variables that govern command output after login. If command output also reflects some other server settings, it may be necessary to change this before WinSCP can be used.</div><div></div><div></div><div>WinSCP runs on Microsoft Windows XP SP2/Windows Server 2003 SP1 and newer, up to Windows 11 and Windows Server 2022. WinSCP runs both on client and server editions of Microsoft Windows. We know of no reason why WinSCP should not continue to work on future versions of Microsoft Windows.</div><div></div><div></div><div>WinSCP is an open-source, free Secure File Transfer Protocol (sftp) and File Transfer Protocol (ftp) client for Microsoft Windows. You can use WinSCP to securely transfer files between your local Microsoft Windows machine and a remote server.</div><div></div><div></div><div>I am going to assume that your screen images are from some client machine. On the destination server, you do not need to install WinSCP, you need to install the OpenSSH feature and configure it for access. WinSCP can see FTP on port 21 but does not see SFTP on port 22.</div><div></div><div></div><div>I was recently trying to install and use the SFTP server but I have ran into a problem. When trying to start the application my Windows 10 UAC is blocking the program. To be clear, it runs once when installed, but after closing the program and trying to launch it again Windows is blocking it.</div><div></div><div></div><div>We heard back from MS that indeed its "SmartScreen" (related to Windows Defender) that's blocking execution of the scpservertray.exe executable, and Windows User Account Control (UAC) that's just presenting the '"This app has been blocked for your protection" message when launching the SFTP/SCP server is attempted.</div><div></div><div></div><div>The guidance from MS is that Solarwinds needs to contact them to clarify if the SFTP/SCP server (scpservertray.exe) is to be considered trusted (not vulnerable) and until that occurs, Windows SmartScreen will continue to block any attempts to launch the file or even allow uninstall of the product already installed.</div><div></div><div></div><div>If you are using Amazon S3 for your server's storage, and if your client contains an option to use multiple connections for a single transfer, make sure to disable the option. Otherwise, large file uploads can fail in unpredictable ways. Note that if you are using Amazon EFS as your storage backend, EFS does support multiple connections for a single transfer.</div><div></div><div></div><div>If the endpoint type for your Transfer Family server is VPC, identifying the endpoint to use for transferring files is not straightforward. In this case, use the following procedure to find your Amazon VPC endpoint.</div><div></div><div></div><div>In the preceding command, sftp_user is the username and transfer-key is the SSH private key. Here, service_endpoint is the server's endpoint as shown in the AWS Transfer Family console for the selected server.</div><div></div><div></div><div>To upload a file from your file system to the Transfer Family server, use the put command. For example, to upload hello.txt (assuming that file is in your current directory on your file system), run the following command at the sftp prompt:</div><div></div><div></div><div>For Host name, enter the protocol that you are using, followed by your server endpoint. The server endpoint is located on the Server details page. For more information, see View server details.</div><div></div><div></div><div>As a part of your object's metadata you see a key called x-amz-meta-user-agent whose value is AWSTransfer and x-amz-meta-user-agent-id whose value is username server-id. The username is the Transfer Family user who uploaded the file and server-id is the server used for the upload. This information can be accessed using the HeadObject operation on the S3 object inside your Lambda function.</div><div></div><div></div><div>When an object is uploaded to your S3 bucket using Transfer Family, RoleSessionName is contained in the Requester field in the S3 event notification structure as [AWS:Role Unique Identifier]/username.sessionid server-id. For example, the following are the contents for a sample Requester field from an S3 access log for a file that was copied to the S3 bucket.</div><div></div><div></div><div>Before you can make the transfer, you must know the IP address or fully-qualified domain name of the destination computer. Assuming it's a computer on your same network, and that you're not running a DNS server to resolve computer names, you can find the destination IP address using the ip command on the Linux machine:</div><div></div><div></div><div>With the power of the open source WinSCP application, you have access to any computer in your house or workplace, to servers you have accounts on, and even mobile, edge, and Internet of Things devices. Use this great tool to transfer files as easily as you would copy a file from one local directory to another!</div><div></div><div></div><div>Greetings. Now that Windows 10 has native SSH and SCP I decided to try SCP between two windows machines. However I was unable to establish a connection. The following is an example of how I tried to copy files with SCP and just connect using SSH.</div><div></div><div></div><div>P.S., I realize that saying "just install this fabulous tool" is kind of atone-deaf answer. But I've found ansible to be super useful for administering remote servers, so installing it will surely bring you other benefits beyond deploying files.</div><div></div><div></div><div>If you use the OpenSSH tools instead of PuTTY, you can accomplish this by initiating the scp file transfer on the server with sudo. Make sure you have an sshd daemon running on your local machine. With ssh -R you can give the server a way to contact your machine.</div><div></div><div></div><div>You can combine ssh, sudo and e.g tar to transfer files between servers without being able to log in as root and not having the permission to access the files with your user. This is slightly fiddly, so I've written a script to help this. You can find the script here:</div><div></div><div></div><div>Again, depending on the authentication method of your server you may or may not be prompted for a password/passphrase. Regardless of your authentication method, sudo will prompt you for user's password. Unless, of course you have disable requirement for password when user runs chown mv and rmdir. See this question for guidance on how to do that.</div><div></div><div></div><div>You can omit && sudo rmdir /wwwtemp from the end of the final ssh command string if you would like to continue using the temporary repository in future. Doing so also means that you can omit the first ssh command each time you desire to transfer files to your server in this manner.</div><div></div><div></div><div>It is much more expedient just to reconfigure WinSCP and leave the VCSA the way it is! In order to use WinSCP, you will need to change where WinSCP looks for the sftp-server binaries.</div><div></div><div></div><div>Awesome stuff. Thanks!</div><div></div><div>You might consider say to TYPE the SFTP server protocol options as opposed to SPECIFY. (shell /usr/libexec/sftp-server) I thought it was in a dropdown and not requiring my manual entry. Took a few minutes to sort that out.</div><div></div><div></div><div>I have a windows server which I also log into via putty. On the windows server, i have winscp with saved and working logins. From winscp > Generate Session URL, I can get a specific accounts login details (username, password, server, etc.). Now when i try to manually execute an sftp command from the putty session, i can get to the password part of the command but it wont accept the login. Here is the command I use on the command line:</div><div></div><div></div><div>As things stand, the most likely explanation based on the log messages you're showing is that the username or password being provided is not the correct one. However, it would also be helpful to see the SSH server logs and authentication logs from the server side. What do you see being logged on the server when the client tries to connect, but fails ?</div><div></div><div></div><div>Nevertheless, something is clearly not right somewhere. Checking the server logs might perhaps give you a clue as to what that something might be. Something is causing some aspect of the SFTP connection to fail, and without looking at the server logs, it's going to be hard to tell what that something is.</div><div></div><div></div><div>You'd be wanting to look at the SSH server logs and authentication logs on the server that the SSH/SFTP client is trying to connect to. They should hopefully shed some more light on why the login is failing, or on what else might be going wrong.</div><div></div><div> df19127ead</div>
--- Synchronet 3.21a-Linux NewsLink 1.2