Sorry but you missed it completely. Both this question and my answer were not about gdb internals at all. Its you keep bringing up ptrace over and over again.

I'm not sure ptrace is relevant here at all. If what you quoted about ptrace above was correct, one would be unable to run SUID programs under gdb at all. This is not the case however - they start fine, just under your userid.

I'm not really sure how your comment applies to my answer, honestly. OP didn't ask about ptrace at all. And ptrace is Linux-specific while the logic is not (nor OP seem to ask about Linux as its only mentioned in tags)

Of course you unscramble them back when you need to access or index them.

You have much better control on your infrastructure. For example, you can detect and ban the offender relatively easily, while on S3 it is not really possible.

So if someone doesn't like you or your project, all they need to run a lot of those GET requests to present you with a nice bill?

Let's see how it works for them.

@ycomp There's difference between detecting ransomware binaries (this is what AV engine is doing), and preventing ransomware from encrypting files (this may be an additional component).

@TomášZato you can scan most clean executables without reading the whole file from disk. Obviously you need to read some data.

@ycomp it is not necessary. All major AV vendors detect adware, spyware and other malware - not just viruses. And separate anti-ransomware is not necessary either.