First, confirm the following basic points.

  • Authentification is by using SSH key not by password.
  • A private key is pair of a public key registered in a D-way submission account.
  • A private key file has read permission.
  • A private key file permission is set as others cannot access. For example, rw——-.
  • A passphrase for private key is correctly entered.

When transferring data files by using a private key generated in the other operating system, please check format of a private key. Convert private key

In Unix/Mac OS X: Convert a key in the Windows PuTTY file format into the OpenSSH.

In Windows WinSCP: Convert a key in the Unix/Mac OS X OpenSSH file format into the Windows PuTTY format.

When these are correct, because we do not support technical details regarding use of third-party softwares, please refer to websites of softwares or confirm your system administrators whether scp (port 22) is allowed or not.

Windows PowerShell

If the private key access permission is too open, following error will be shown.

Permissions for './private-key-for-auth' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
Load key "./private-key-for-auth": bad permissions Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
lost connection

Right-click the private key file and select the property.
file property

Select detailed setting of the security tab.
detailed setting of security

Disable access permission entry inheritance to enable permission deletion.
Disable access permission entry inheritance

Convert explicit access permission.
Convert explicit access permission

Delete all permissions.
Delete all permissions

Add access permission.
Add access permission

Add a Windows user (example, test07). Add a Windows user

Allow full control to the Windows user.
Allow full control

Change the file permission.
Change the file permission

Run scp.