Rafael Skodlar wrote: >[snip] > >It's safer to use more secure methods for communicating between the >systems on the network from the beginning rather than trying to fix it >later. You newer know when next newbie will put your code on the system >and then bad things might happen. Just my experience. CNC machines are >production grade after all and one would not want to end up with broken >parts. > > While I usually agree with this, I think I disagree in this case.
The most common usage for this type of connection will be a headless EMC2 machine connected to a machine in the same building, possibly in the same cabinet. Although it would be possible to use a more secure connection, it's unnecessary for the majority of users. Anyone who wants to connect their machine or their local network to the internet needs to use one or more of the many available tools to secure their machine (external firewall), or the connection (use an ssh-encrypted socket, or whatever). Putting the complexity of authentication and security into emcrsh seems like a duplication of effort, since there are already tools to secure machines from the single socket/port level up to entire networks. Again, the simplest way to eliminate this problem is just to not connect the EMC2 machine to the internet. - Steve ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
