I have a pair of manned GAU-19 turrets now. It's a good job I don't need new colonists because anyone who dares peek the entrance is immediately blended into nutrient paste.
CVSS is mostly fine (within the bounds of what you can reasonably achieve for a general metric) for the simple cases of network services and web apps and regular software, but really breaks down outside of that.
And unfortunately I do a lot of "outside of that".
if you keep everything in a single static view where the high-level system topology is what defines the position, then your CVSS vectors end up misaligned with the actual threat model of the component (e.g. the RoT/secp considers anything outside of it as untrusted), and the scores are wonky.
if you vary the meaning of attacker position depending on the context of the per-component threat model, the scores are more representative but the vectors almost always confuse people.
I think CVSS scores fundamentally failed by trying to apply one unified rubric to all systems and threat models.
consider the case where you're reviewing a SoC ASIC with a root of trust ROM, security processor, cryptographic accelerator, and main processor, with an internal AXI bus and external PCIe connection to a host, with each processor having internal security boundaries.
trying to maintain a coherent view of what "network", "adjacent network", and "local" mean is nearly impossible here.
anyone know if there's such a thing as a mechanical angle gauge (aka "two arm protractor") but with very short arms for measuring angles on small objects? needs to be able to measure both acute and obtuse angles.
the notch disc style ones are a perfect size, but only allow you to match fixed sets of angles so they're not very useful if the angle isn't a round number.
specifically looking for a mechanical tool - I don't want anything digital, I really hate needing batteries in stuff like this.
pet peeve: the help text for `ln` (for making symlinks and such) describes the two file path parameters as `source_file` and `target_file`, rather than `link_path` and `existing_file`.
@ryanc ... gonna have to remind myself if left and right shift operators on unsigned integers in c++ switch their numeric effect on values when running on big endian architectures.
if so, ohhhh I bet there are a ton of bugs out there.
@thomasfuchs we did one of the really tall, really wide ones with the sliding glass doors.
the instructions are *awful*. they get you to put the doors on, which is the most horrendously fiddly thing to have to do with a door that's made of glass coated aluminium, heavy as fuck, bigger than you, impossible to hold, and with a mechanism you can't see. then they refer you to the second manual. which tells you to TAKE THE DOORS BACK OFF. I almost fucking lost it.
@thomasfuchs also they get you to install the internals of the thing first (shelves, drawers, etc.) which I still maintain is a terrible order to do things in. getting the doors on the tracks properly and attaching the retaining screws requires standing inside it. so they get you to make it impossible / very awkward to stand inside, THEN put the doors on, then take them back off because fuck you
@thomasfuchs I later found out that there's an entire support group subreddit for PAX because it's the final boss of IKEA products and people need somewhere to vent after doing battle with the damn things.
@thomasfuchs I have never been so angry at furniture in my life.
no flat pack assembly process should take two people >6 hours and require me to have to go stand outside by myself for a while to calm down so I don't snap and throw the whole thing in the nearest canal.
@thomasfuchs@whitequark no that's way worse because then I have to fuck about flipping between tabs. and moving it out to a separate window messes up my window org (logical task separation for regions of my screens)