Almost everything was web based. Being in computer science i did have to write code and compile executables that my TAs running Windows could run; so it wasn’t perfectly smooth. There was also Respondus Lockdown, but I could borrow a laptop from the library to use it.
For what it’s worth my i9-13900 was experiencing serious instability issues. Disabling turbo helped a lot but Intel offered to replace it under warranty and I’m going through that now. Customer support on the issue seems to be pretty good from my experience.
So you have a product that you’ve made into a system for getting answers. And then you couldn’t be bothered to try and sanitize training data enough to get your answer system’s new headline feature from spreading blatantly incorrect information? If it doesn’t work, maybe don’t ship it.
Seen a concerningly large amount of companies calling things they don’t like “unconstitutional” lately.
It’s so easy to think that it can’t happen to you. Then it happens. Happened to me, happened to cyber security majors at my college. I’m so glad he got the channel back. I love Son of a Glitch and seeing now that YouTube casually didn’t recommend his videos for months just means I’ve got more to binge I guess!
I’m not saying incomprehensible build scripts are good here, my mistake for making it seem that way. I’m not confident that hiding it elsewhere would have been strictly more obvious but it absolutely could have been.
I’ve done some pretty complex C projects and haven’t had build scripts nearly that large. This one seems particularly unwieldy and certainly helped the attacker.
I’m going to be honest, I’m getting a little tired of hearing everyone’s thoughts on the xz backdoor. It’s discouraging and sucks when every detail of the project which, keep in mind, was maintained by one person who fell victim to a social engineering attack, is scrutinized. It makes me concerned about anyone depending on any of my projects.
Especially the comments on things such as the build scripts, which this kind of article seems to gravitate towards. If the build scripts were tiny and checked then the attack vector would have just been different, I’m not even too sure the language mattered. The attack was social engineering, after that it was pretty much project agnostic. xz was targeted cause the maintainer was done working on it and it was heavily depended on.
Had to re-read the title more times than I’d like to admit to recognize that “sick” didn’t mean the flowers were really awesome.
I tried for about a week: reading documentation, viewing and modifying example programs, using a Rust IDE with warnings for all my silly mistakes, the works. I couldn’t manage to wrap my head around it. It’s so different from what I’m used to. If I could dedicate like a month to learn it I would, but I don’t have the time :/