About 18 months ago I wrote a blog talking about changes in how accept works in OpenVOS release 17.1.
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.
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.
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?
When you are fixing bugs in existing code, it is easy to fall into the habit of finding the “mistake” in the code and adjusting the code to avoid the mistake.
Today, a customer asked me how much disk storage a single VOS module can address. Here is my response.
I was recently asked why Stratus was not providing security updates for customers running OpenSSL on releases of VOS prior to 17.0, when we are still providing updates to customers running OpenSSL on VOS 14.7 on Continuum.
Starting in OpenVOS Release 18.0, VOS System Administrators will be able to select one of 3 new password encryption algorithms. This post provides an overview of these changes.
Recently, a customer wrote to Stratus Customer Service to ask whether we could recommend an “atomic clock” for use with his OpenVOS system.