My FUDforum

Home »  » SocketServer and NS-Link » NS-Link versus SocketServer security
Re: NS-Link versus SocketServer security [message #1059 is a reply to message #1056] Mon, 22 October 2018 10:56 Go to previous messageGo to previous message
BobF is currently offline  BobF
Messages: 10
Registered: October 2018
Location: Grand Forks, ND
Thanks for the information. The first reply you gave about the driver raises a few questions that I need answers on so I can better understand the security:
I assume the driver you are referring to is one in the Devicemaster (DM) itself? Or is it something on the computer that is being used to connect to the DM? I was using the same computer to log into all of my Devicemasters when some showed NS-Link and others showed SocketServer. I like how on the DM's that showed SocketServer, it asked for the user and password. In your replies above, it almost seems as if I had the correct driver, it should show up as NS-Link and there would be no prompt for a password?

My concern is if someone had the IP address of my DM and they tried connecting, that they could then immediately see my config and port info if they had the "correct driver". I don't want to assume the ones that are prompting me for a username and password are secure if I am only being prompted because of a lack of a proper driver. The ones that are not prompting for a password are apparently using the proper driver since they show NS-Link.

In the end I am hoping that there is a way to make the DM prompt for a user/password no matter the way you choose to connect to it. Using PuTTY via Telnet does prompt for a password on the ones I set up that way, but over a common web browser there is no password for those same DM's with the driver that allows it to show NS-Link.

Bob F
Minnkota Power Cooperative
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Older Versions
Next Topic: SocketServer and NS-Link Firmware Combined
Goto Forum:

Current Time: Fri Jan 22 06:01:58 CST 2021

Total time taken to generate the page: 0.01229 seconds