crackpot theory:
the current method of protecting paid nonfree software is to:
1. not release source
2. make reversing difficult by putting in a bunch of obfuscating garbage (that does actually execute) which is programmatically easy to deobfuscate using AI but difficult otherwise.
3. use tools like vmprotect (actual malware) or denuvo (also actual malware) to mess with syscalls using a micro virtual machine wrapping the binaries.
im not sure how easy it is for ai to reverse microvms/containers. i know they are the most difficult to get around.
with AI becoming so capable at reversing i suspect that paid software is going to change how they protect their code. i think these are the options
1. everything goes inside its own microvm.
this would suck because when denuvo is removed from games suddenly people see 20% increases in framerate and the filesize for the game gets a lot smaller. computers would run much slower and we would probably need new chips that are specifically designed to decode protected system calls, much like how the rise of encryption at rest in desktop computers necessitated dedicated aes decryption hardware inside cpus.
2. make the token cost of reversing too expensive. add a bunch of garbage nonexecuting code that looks legit and worm it into all of the other functions. configure the compiler to compile this anyways despite knowing full well that its junk that would otherwise never get compiled. the result is probably less secure code and harder to manage codebases. f
3. AI ethics based mitigations: include garbage code that should never reasonably execute that contains false but reasonable instructions on how to do things that generate hard refusals from frontier/non-obliterated/ non-vector activated models (such as how to build a nuke or use gene editing to create viral strains). malware already does this and it is funny.
this would force reversers to use less effective models that have had the ethics reasoning removed and doing this generally reduces response accuracy one way or another and would make reversing difficult until the offending code is removed.
4. cloud hosting: the software maintainer would need to buy compute space to host the program. when you run the software it just creates a VNC/remote desktop connection to the server and the code is executed remotely. privacy nightmare. not security compliant in any sensitive industry. expensive for both the user and software owner. probably laggy.
software is gonna suck so hard in 10 years. it already does
the current method of protecting paid nonfree software is to:
1. not release source
2. make reversing difficult by putting in a bunch of obfuscating garbage (that does actually execute) which is programmatically easy to deobfuscate using AI but difficult otherwise.
3. use tools like vmprotect (actual malware) or denuvo (also actual malware) to mess with syscalls using a micro virtual machine wrapping the binaries.
im not sure how easy it is for ai to reverse microvms/containers. i know they are the most difficult to get around.
with AI becoming so capable at reversing i suspect that paid software is going to change how they protect their code. i think these are the options
1. everything goes inside its own microvm.
this would suck because when denuvo is removed from games suddenly people see 20% increases in framerate and the filesize for the game gets a lot smaller. computers would run much slower and we would probably need new chips that are specifically designed to decode protected system calls, much like how the rise of encryption at rest in desktop computers necessitated dedicated aes decryption hardware inside cpus.
2. make the token cost of reversing too expensive. add a bunch of garbage nonexecuting code that looks legit and worm it into all of the other functions. configure the compiler to compile this anyways despite knowing full well that its junk that would otherwise never get compiled. the result is probably less secure code and harder to manage codebases. f
3. AI ethics based mitigations: include garbage code that should never reasonably execute that contains false but reasonable instructions on how to do things that generate hard refusals from frontier/non-obliterated/ non-vector activated models (such as how to build a nuke or use gene editing to create viral strains). malware already does this and it is funny.
this would force reversers to use less effective models that have had the ethics reasoning removed and doing this generally reduces response accuracy one way or another and would make reversing difficult until the offending code is removed.
4. cloud hosting: the software maintainer would need to buy compute space to host the program. when you run the software it just creates a VNC/remote desktop connection to the server and the code is executed remotely. privacy nightmare. not security compliant in any sensitive industry. expensive for both the user and software owner. probably laggy.
software is gonna suck so hard in 10 years. it already does
๐ค1
>sitting next to my boss at work
>coworker says something in group chat about the elections
>start typing a response to coworker
>boss says "skip if you are writing something about politics, please stop"
he fucking got me.
>coworker says something in group chat about the elections
>start typing a response to coworker
>boss says "skip if you are writing something about politics, please stop"
he fucking got me.
๐5๐ญ1
skipper's musings
https://fixupx.com/IntCyberDigest/status/2118343325770006690
>new ssh login bypass
didnt i tell you guys to chill out for a while? we've had too many vulns recently.
didnt i tell you guys to chill out for a while? we've had too many vulns recently.
๐พ2
yesterday microsoft 364 reported a global email outage
today microsoft 363 reported that the global email outage is still unresolved
today microsoft 363 reported that the global email outage is still unresolved
when protecting users from phishing attacks it is very important not only to provide robust training, but also to provide continual feedback when they receive phishing messages. users have the ability to report phishing messages which are then delivered to me. I look at them and congratulate the user for catching a malicious message. IMO, this is just as important as the actual structured training because frankly people like to be told "good job" and will look for opportunities to be praised. They will be vigilant for phishing mails because reporting one means being praised, even if only a little bit.
The downside is that for 20 minutes a day, every day, my outbox looks like this:
Thanks for reporting this. I reviewed the message and determined that it is phishing.
Thanks for reporting this. I reviewed the message and determined that it is phishing.
Thanks for reporting this. I reviewed the message and determined that it is phishing.
Thanks for reporting this. I reviewed the message and determined that it is phishing.
Thanks for reporting this. I reviewed the message and determined that it is phishing.
The downside is that for 20 minutes a day, every day, my outbox looks like this:
Thanks for reporting this. I reviewed the message and determined that it is phishing.
Thanks for reporting this. I reviewed the message and determined that it is phishing.
Thanks for reporting this. I reviewed the message and determined that it is phishing.
Thanks for reporting this. I reviewed the message and determined that it is phishing.
Thanks for reporting this. I reviewed the message and determined that it is phishing.