• 2 Posts
  • 56 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • Do a search for you server OS + STIG

    Then, for each service you’re hosting on that server, do a search for:

    Service/Program name + STIG/Benchmark

    There’s tons of work already done by the vendors in conjunction with the DoD (and CIS) to create lists of potential vulnerable settings that can be corrected before deploying the server.

    Along with this, you can usually find scripts and/or Ansible playbooks that will do most of the hardening for you. Though it’s a good Idea to understand what you do and do not need done.








  • True on the digit by digit code decryption. That I can forgive in the name of building tension and “counting down” in a visible way for the movie viewer. “When will it have the launch code?!” “In either 7 nano seconds or 12 years…”

    If they had been more accurate, it would have looked like the Bender xmas execution scene from Futurama:

    https://www.youtube.com/v/aRdRZ6TKo4s?t=25s

    I did like the fact that they showed war-dialing and doing research to find a way into the system. It’s also interesting that they showed some secure practices, like the fact there was no banner identifying the system or OS, giving less info to a would be hacker. Granted, now a days it would have the official DoD banner identifying it as a DoD system.

    I remember with Windows 95, LAN Manager passwords were hashed in two 7 digit sections which made extracting user password from the password hash file trivial:

    https://techgenix.com/how-cracked-windows-password-part1/

    Looks like it was worse than I remember. The passwords were first converted to all upper case first!



  • Frametimes is the specific measure.

    <11.1ms for 90Hz or <8.33ms for 120Hz

    If the game, experience, or whatever breaches that minimum frame time frequently, then you can experience nausea just from moving your head around.

    It does require some sacrifices like turning shadows down a notch or two in some game engines and choosing additional visual effects carefully. Some visual effects require additional computation passes and can add the the frame time.

    A low latency CPU (like the AMD 3D cache CPUs) or a normal mid to high end CPU with fast memory with good timings helps quite a bit.

    The GPU should be capable of pushing the pixels and shading for the target resolution. Even with a 6900xt I’ve been able to comfortably push over 4500x3000 per eye rendering (enough to get a nice anti-aliasimg effect on my Pimax 8kX at the “normal” 150 degree H.FoV) in most games.

    Surprisingly, fidelity FX can help as well (the non-temporal version).



  • Would be nice if the author had done a bit of research on the specific things that had been done in VR since he tried his DK2 to prevent nausea:

    An Oculus DK2, a PC that couldn’t quite run a rollercoaster demo at a high-enough framerate, and a slightly-too-hot office full of people watching me as I put on the headset. Before I’d completed the second loop-de-loop, it was clear that VR and I were not going to be good friends.

    The study the author quotes dates to August 2019!

    https://insidescience.org/news/cybersickness-why-people-experience-motion-sickness-during-virtual-reality

    For one, non-persistent displays have become the norm. These only show (strobe) the image for a fraction of the frame time and go black in between. Valve discovered that the full 1/90th of a second an image is displayed is enough to induce nausea if the head is moving during that time. So the Vive (and the Oculus Rift) had non-persistent displays.

    The stobing effect is so fast you don’t notice it.

    Elimination of artificial movement is another. The reason Valve focused on games with teleport movement and made a big deal of “room scale” early on was to eliminate the nausea triggers you encounter in other types of experiences.

    Valve had an early version of Half Life 2 VR during the days of the DK2, but they removed it as the artificial motion made people sick (myself included).

    For many, sims work as long as there is a frame in their field of vision to let their brains lock into that non-moving frame of reference (ex car A-pillars, roof line, dash board, outline of view screen on a ship interior, etc). Note the frame still moves when you move your head, so it’s not a static element in your field of view.

    Also it helps if your PC can render frames under the critical 11.1ms frame time (for 90Hz displays). Coincidentally, 90Hz is the minimum Valve determined is needed to experience “presence”. Many folks don’t want to turn down graphic options to get to this. It’s doable in most games even if it won’t be as detailed as it would on a flat screen. Shadows is a big offender here.

    Resolution isn’t as big of a factor in frametimes as detailed shadows and other effects. I have run games at well over 4k x 2.5k resolution per eye and been able to keep 11.1ms frame times.

    Lastly, it has been noted that any movement or vibration to the inner ear can for many stave off nausea. This includes jogging in place while having the game world move forward. For many years we’ve had a free solution that integrates into Steam VR:

    https://github.com/pottedmeat7/OpenVR-WalkInPlace

    Jog in place to make your character move forward in the direction you’re facing. Walk normally to experience 1-to-1 roomscale.

    I’ve use the above to play Skyrim VR without any nausea. Good workout too!

    For car, flight, spaceflight simulators, a tactile transducer on your chair (looks like a speaker magnet without the cone - or basically a subwoofer without the cone) can transfer the games sound vibrations directly to you and therefore your inner ear and prevent nausea.

    I’ve literally played over 1,000 hours of Elite:Dangerous this way as well as Battlezone VR and Vector 36. All games that involve tons of fast artificial movement.

    The main issue is too many people tried out VR cardboard or old DK2 demos with low and laggy framerate, persistent displays, and poorly designed VR experiences and simply write off all VR as bad and nausea inducing.

    Edit: added links and trailers to the games mentioned so folks can see the motion involved. The “study” wasn’t a proper study. It was a quote from a scientist. No data was given about what headsets or which experiences caused nausea.









  • It is fact:

    https://www.cs.cmu.edu/~dst/Cowen/essays/irs.html

    On 1 October 1993, the Church of Scientology obtained tax exemption from the United States Internal Revenue Service (IRS). This ended 26 years of what the Church itself has described as a “war” against the IRS, in which it used extraordinary and in many cases illegal tactics - bugging of government offices, theft of mountains of classified files, private detectives pursuing senior government officials, thousands of lawsuits, full-page attack adverts in US daily newspapers, and so on.

    So perhaps it is not such a great surprise that the settlement itself came about in some very unusual circumstances, raising questions about the actions of both the Church of Scientology and the IRS. Neither party has been willing to provide answers, with the IRS refusing to disclose the terms of the exemption agreement in defiance of a court order and US taxation law. But with the leak in December 1997 of the secret agreement, the relationship between Scientology and the IRS is under greater scrutiny now than ever before.