Vandyke Vshell Download

[Shantelle Wenske]

ALBUQUERQUEN.M., Feb. 18, 2021 /PRNewswire/ -- VanDyke Software, a developer of multi-platform secure file transfer and secure terminal emulation software, today announced the official release of VShell 4.6 server.

Options for renaming files and folders include the insertion of parameters such as dates, timestamps, session IDs, protocols, and more. Summaries with the number and list of files transferred can be created when a user logs out, then used in commands that are executed automatically. On Windows, notifications with file transfer summaries can be automatically generated and sent via email.

"Single Sign On makes managing user accounts even easier," said Danielle Argiro, Product Manager for VShell. "With SSO, Windows users can log on to the VShell HTTPS server without entering a username or password. This improves the user experience and also increases IT productivity."

Fully-functional evaluation copies of VShell 4.6 can be downloaded from the company's website: VShell evaluators have full access to VanDyke Software's expert technical support to assist with installation, configuration, and testing during the 60-day VShell evaluation period.

Argiro said, "Our multi-protocol file transfer server combines security with convenience and flexibility. And, it's backed by real people who will be there to help when needed. With VShell, you can offer a wide range of file transfer capabilities to your organization and external partners with confidence."

Busy IT professionals depend on VanDyke Software to deliver rock-solid, easy-to-configure software for secure remote access, secure file transfer, terminal emulation, and remote administration. VanDyke Software offers a fully-supported evaluation of its products prior to purchase, providing both evaluators and customers with a higher level of service.

The company's product offerings include the SecureCRT Secure Shell terminal emulator, the SecureFX secure file transfer client, the VanDyke ClientPack, and the VShell secure file transfer server. The company also offers a mobile app, SecureCRT for iOS, which is available for purchase from the Apple App store. For more information about VanDyke Software, visit the company's website at www.vandyke.com.

SSH offers a highly secure channel for remote access. However, if you face an audit for regulatory or business requirements, such as Visa/Mastercard PCI, you need to be aware of some potential authentication related short-comings that may cause headaches in an audit. For example:

The WiKID Strong Authentication System is an inexpensive, easy to use, extensible and highly secure two-factor authentication system. It is software-based with token support for Windows, Mac, Linux, Blackberry, Palm, Windows Mobile and J2ME devices. The server is simple to install and configure as is adding new users. In fact, users can optionally validate themselves based on existing trusted credentials. It is extremely well-suited for companies seeking PCI compliance or that often have non-employees who need secure access, such as customers or contractors. In this tip, we will show you how simple it is to add support for WiKID one-time passcodes to the VShell server on Linux.

These settings require both an account on the server (the second line) and a valid response from the WiKID server (the first line). Now, edit the /etc/raddb/server file to point to the WiKID Strong Authentition server:

A WiKID domain manages the relationship with WiKID users and specifies security parameters such as minimum PIN length, passcode lifetime, maximimum bad PIN and passcode attempts, etc. The server can handle an unlimited number of domains. Because WiKID uses public key pairs instead of shared secrets like most one-time password systems, the token clients can also handle an unlimited number of domains accross multiple WiKID servers - even across different companies - with no loss of security.

To add the domain, log into the WiKIDAdmin web interface, click on the Domains Tab and select Create New Domain. Enter in the required information (leave the registered URL box blank - it is only for mutual authentication of https sites). Also, leave TACACS+ and Password Reset Domain boxes unchecked. The domain identifier is the zero-padded IP address of the WiKID server.

Next we set up the VShell Server as a Network Client on the WiKID server. Click on the Network Clients Tab and select "Create A New Network Client. Enter a name for it, the IP address of the VShell server, select Radius as the protocol and select the domain you just created. Clicking Add will bring up the Radius parameters. Enter the shared secret you used in the /etc/raddb/server file. Leave the return attributes box empty (unless you really know what you're doing). Click Add to complete. Now, you need to restart the WiKID server so the network client can be loaded into the WiKID server's firewall settings.

Start the WiKID token client. Select Actions/New Domain and enter the 12 digit identifier used in the domain creation. You will be asked to set your PIN and you will get a registration code back from the server. To manually validate this token, go the WiKIDAdmin web interface, click the Users tab and Manually Validate a user. You will see the registration code. Click it and enter your desired username - remember the user should also have an account on the Vshell server as specified in the /etc/pam.d/vshelld file. Now the server will accept one-time passcodes from this token. On the token client, select Get Passcode and enter your PIN. The returned one-time passcode is automatically copied into the clipboard. Start up an ssh client, such as SecureCRT, and log into the VShell server. When prompted for a password, hit Control-V and enter. If all goes well, you should be in!

Hi,

I have a stitution in which I am initiating an sftp session from my HPUX machine to a windows server 2008, in which I have an ssh server installed(vandyke vShell). So everything is working fine and I am able to establish the connection and do the transfer.

The issue comes when I check the logs in my windows server. There I have some entries like:

I am having issue wiht this particular line "none for user User rejected because it is unavailable". What I want to do is to avoid this message from coming into logs. So after some research of my own I came to know that this was coming because ssh is using the initial athentication method as "none" and my server is rejecting it. I also came to know that this is a default behaviour of ssh and it uses the "none" auth method to know which all auhtentication methods are supported by the server.

So what I want to do is somehow use "password" as the initial auhtentication method instead of "none".

I tried giving the command line parameter ssh -o PreferredAuthentications=password -o PasswordAuthentication=yes, but it did not solved the issue. I was still getting the message in logs.

I have considered not logging the authentication event in the vShell logs as a last resort, but I would not like to come to that.

Is there any way that I can avoid taking "none" as the initial auhthentication method?

Thanks

Job for vshell.service failed because the control process exited with error code.

See "systemctl status vshell.service" and "journalctl -xe" for details.

Job for vshell-ftps.service failed because the control process exited with error code.

See "systemctl status vshell-ftps.service" and "journalctl -xe" for details.

dpkg: error processing package vshell (--configure):

installed vshell package post-installation script subprocess returned error exit status 1

Errors were encountered while processing:

vshell

3a8082e126