Will or funding. Replacement of a system that initially cost 5mil to install and configure in 2009 is gonna cost 2x that at least to replace.
Will or funding. Replacement of a system that initially cost 5mil to install and configure in 2009 is gonna cost 2x that at least to replace.
Kinda have mixed feelings about this. Those who are innocent know that they are on the list at the cost of their SSN or national ID. Bit of a mixed blessing there.
Also, a bunch of truly bad actors will be compromised. Maybe that’s good?
Hmm. Dunno how to feel.
Best part is it’s still up.
Check that you’ve fully configured your webstore templates folks.
I understood the answer, not the meme. I guess I wasn’t clear. Sorry internet friend. Clearly GPT was lacking some nuance too, as evidenced by some discussion ITT.
Did I say that? It’s obvious that it’s a fairly nuanced as topics go, and GPT is not great at nuance. It doesn’t seem like it’s totally wrong though.
Anyhow I don’t rust, so it’s kinda irrelevant, just an interesting topic.
GPT is fairly useful but I definitely don’t trust it implicitly. Lol
A Rust procedural macro (proc macro) is a metaprogramming feature in Rust that allows you to define custom syntax extensions and code transformations. They operate on the abstract syntax tree (AST) of Rust code during compilation and can generate or modify code based on annotations or custom syntax.
Sandboxing a Rust proc macro refers to restricting the capabilities of the macro to improve security and prevent potentially harmful code execution. There are several reasons why someone might want to sandbox a proc macro:
Security: Untrusted code can be executed during the macro expansion process. To prevent malicious code execution or code that could access sensitive information, sandboxing techniques are employed.
Preventing unintended side effects: Some proc macros might inadvertently introduce side effects like file I/O or network requests. Sandboxing can limit these actions to ensure the macro only performs intended transformations.
Resource control: To manage system resources, a sandboxed proc macro can be configured to run within resource limits, preventing excessive memory or CPU usage.
Isolation: Sandboxing helps keep the macro’s execution isolated from the rest of the compilation process, reducing the risk of interfering with other parts of the code.
Sandboxing a Rust proc macro typically involves using crates like sandbox
or cap-std
to restrict the macro’s capabilities and limit its access to the system. This ensures that the macro operates within a controlled environment, enhancing the overall safety of code compilation and execution.
-GPT
I didn’t get it either.
Seems to me if your code will be this unpredictable, you should only run it on an air gapped machine
Wait, Trump was the 58th president? I smell an AI article.