Why is it that from my home directory I can use SSH with public key authentication to log into another host without being prompted for a password?
Read More
I’m pleased to announce that OpenVOS Release 17.2.0, GNU Tools Release 4.0.0 and Kona for OpenVOS Release 1.1.0 are now generally available.
Last week (well it was last week when I started writing this) we had an issue come into the CAC where someone wanted to write a command macro that ran telnet to log into a system and execute some commands, for example the command macro test.cm logins into a remote host and executes the foo.cm command macro.
About 18 months ago I wrote a blog talking about changes in how accept works in OpenVOS release 17.1.
If you have ever tried to use POSIX-based programs to process VOS structured files, you may have encountered some restrictions or seen some behavior that you didn’t understand.
The maintenance network is used by OpenVOS for monitoring several devices including the RAID and SAN disk arrays.
In this post I wish to discuss a common coding error that can result in a module running out of or at least seriously depleting the available number of stcp device clones for use in creating TCP sockets.
A lot of locations are mandating that you stop connecting to the system with Telnet, and use SSH instead.
There has been a fair amount of confusion over the difference between the host file and hosts (plural) file.
Don’t worry, despite the title I haven’t reverted to math nerd mode. The topic is not number theory but socket programming and a coding mistake that I have seen way too often.