You may now find Operating System Release Information for VOS and OpenVOS Systems on the Stratus web site. Look for it in the left navigation bar on many of the pages.
Read More
Paul Green and I were discussing a new command he’s working on called check_module_security. The subject of unnecessary commands available at the login prompt came up. Jon Schmidt of Transaction Design recommends in an article about Locking the Barn Door.
When system log messages (all of them: hardware, security, syserr, etc) are generated in OpenVOS, they are sent to the syserr partition, and an event is notified. A process named TheOverseer is waiting on that event, along with a lot of other events.
Starting in release 13.2 VOS has offered the ability to configure a fault tolerant IP interface by configuring active/standby Ethernet adapters.
An SSH tunnel can be used to secure communication between a client and server that cannot otherwise be secured.
When people think of IPsec they think of data encryption but it can also be used to drop packets or allow them without any encryption.
Something that people moving from TCP_OS to STCP notice right off the bat is that the set of TCP statistics displayed by the TCP_OS netstat command is quite a bit richer than that displayed by STCP.
Sometimes netstat will show a socket that appears to be stuck. The remote application has been terminated, sometimes even the OpenVOS application has been terminated but netstat is still showing the socket. This article will explain why this happens and what you can do about it.
Every now and then someone asks the following question “We added our application port to the services file and now some other application is using it – why”. The answer is because the services file does not reserve port numbers.
More and more security and network administrators are prohibiting the use of telnet. Unfortunately, the Stratus RSN requires that the Stratus module run a telnet server.