> refrain from setting background colors That's the thing though, setting bg color opens up a lot of options, and constraining to invert is not sufficient in my opinion.
[flagged]
Ah, okay. Thought you were talking about OOB heap write or something.
> though this would be a much more sophisticated exploit and is maybe a bit of a reach. Not necessarily. I have successfully exploited stack buffer overflows in major products despite stack canaries, ASLR, and DEP. It…
It depends on what mitigations are in place and the arrangement of the stack. Even with stack canaries, having an unfortunate value on the stack e.g. a function pointer can still be quite dangerous if it can be…
Assuming you're talking about a heap buffer overrun, it's still possible to exploit for EoP in some cases.
While there's some overlap in methodologies and back-and-forth with various escalations, so-called malware is distinct from software exploits. Malware can be delivered without an exploit and quite often is. Social…
I was hit by this. Could RDP into machines using the regular client, but could not access Dev Boxes via Windows App. Getting real sick of the low quality AI slop.
Seems quite predictable given the others in the bug report encountering the same.
For sure. When it's out I'll give it a go.
Thanks for taking the time to respond, and apologies for the contentiousness. I'm a jaded old man suffering from severe LLM fatigue, so I may have come off a bit harsh. Your write-up was a good read, and while I might…
The problem is hallucinations. It's incredibly frustrating to have an LLM describe an API or piece of functionality that fulfills all requirements perfectly, only to find it was a hallucination. They are impressive…
Oh come on, the fact that the author was able to pull this off is surely indicative of some expertise. If the story started had started off with, "I asked the LLM how to capture network traffic," then yeah, what I said…
Sure, but that is aside from my original point. If somebody: a) Has the knowledge to run tcpdump or similar from the command line b) Has the ambition to document and publish their effort on the internet c) Has the…
>Is that because wireshark can't do that just from packet captures? Well, not quite. I think it's more that nobody has taken the time to implement it. That's not to say such an implementation would automatically decrypt…
What are you even trying to say? I suppose I'll clarify for you: Yes, I'm confident I could have identified the cause of the mysterious packets quickly. No, I'm not going to go through the motions because I have no…
Not even remotely accurate. While the dissector is not as mature as I thought and there's no built-in decryption as there is for TLS, that doesn't matter much. Hint: every component of the system is attacker controlled…
Well, I spent a good part of my career reverse engineering network protocols for the purpose of developing exploits against closed source software, so I'm pretty sure I could do this quickly. Not that it matters unless…
What I suggested (mistakenly so, see my revised suggested approach in response to one of your siblings) is the exact opposite of gate keeping.
Interesting, I thought it was possible to decrypt SSH in Wireshark a la TLS, but it seems I'm mistaken. It still would have been my first goto, likely with encryption patched out as you stated. With well documented…
The reliance on LLMs is unfortunate. I bet this mystery could gave been solved much quicker by simply looking at the packet capture in Wireshark. The Wireshark dissectors are quite mature, SSH is covered fairly well.
>Current tests suggest it is not likely related to any other known psychedelic compound. For one, the trips it produces are unusually long, commonly lasting 12 to 24 hours, and in some cases even causing hospital stays…
At risk of being called out for my ignorance (I am still new to GPU development and have only limited experience with CUDA), it seems to come down to how appropriate the execution model is to the work e.g. SIMT vs SIMD…
Without disclosing too much, it was an app that stored text messages.
My brother's now ex-wife learned the hard way about the challenges of soft delete. Too bad about the contents of that SQLite database, but his knowing was for the better.
> refrain from setting background colors That's the thing though, setting bg color opens up a lot of options, and constraining to invert is not sufficient in my opinion.
[flagged]
Ah, okay. Thought you were talking about OOB heap write or something.
> though this would be a much more sophisticated exploit and is maybe a bit of a reach. Not necessarily. I have successfully exploited stack buffer overflows in major products despite stack canaries, ASLR, and DEP. It…
It depends on what mitigations are in place and the arrangement of the stack. Even with stack canaries, having an unfortunate value on the stack e.g. a function pointer can still be quite dangerous if it can be…
Assuming you're talking about a heap buffer overrun, it's still possible to exploit for EoP in some cases.
While there's some overlap in methodologies and back-and-forth with various escalations, so-called malware is distinct from software exploits. Malware can be delivered without an exploit and quite often is. Social…
I was hit by this. Could RDP into machines using the regular client, but could not access Dev Boxes via Windows App. Getting real sick of the low quality AI slop.
Seems quite predictable given the others in the bug report encountering the same.
For sure. When it's out I'll give it a go.
Thanks for taking the time to respond, and apologies for the contentiousness. I'm a jaded old man suffering from severe LLM fatigue, so I may have come off a bit harsh. Your write-up was a good read, and while I might…
The problem is hallucinations. It's incredibly frustrating to have an LLM describe an API or piece of functionality that fulfills all requirements perfectly, only to find it was a hallucination. They are impressive…
Oh come on, the fact that the author was able to pull this off is surely indicative of some expertise. If the story started had started off with, "I asked the LLM how to capture network traffic," then yeah, what I said…
Sure, but that is aside from my original point. If somebody: a) Has the knowledge to run tcpdump or similar from the command line b) Has the ambition to document and publish their effort on the internet c) Has the…
>Is that because wireshark can't do that just from packet captures? Well, not quite. I think it's more that nobody has taken the time to implement it. That's not to say such an implementation would automatically decrypt…
What are you even trying to say? I suppose I'll clarify for you: Yes, I'm confident I could have identified the cause of the mysterious packets quickly. No, I'm not going to go through the motions because I have no…
Not even remotely accurate. While the dissector is not as mature as I thought and there's no built-in decryption as there is for TLS, that doesn't matter much. Hint: every component of the system is attacker controlled…
Well, I spent a good part of my career reverse engineering network protocols for the purpose of developing exploits against closed source software, so I'm pretty sure I could do this quickly. Not that it matters unless…
What I suggested (mistakenly so, see my revised suggested approach in response to one of your siblings) is the exact opposite of gate keeping.
Interesting, I thought it was possible to decrypt SSH in Wireshark a la TLS, but it seems I'm mistaken. It still would have been my first goto, likely with encryption patched out as you stated. With well documented…
The reliance on LLMs is unfortunate. I bet this mystery could gave been solved much quicker by simply looking at the packet capture in Wireshark. The Wireshark dissectors are quite mature, SSH is covered fairly well.
>Current tests suggest it is not likely related to any other known psychedelic compound. For one, the trips it produces are unusually long, commonly lasting 12 to 24 hours, and in some cases even causing hospital stays…
At risk of being called out for my ignorance (I am still new to GPU development and have only limited experience with CUDA), it seems to come down to how appropriate the execution model is to the work e.g. SIMT vs SIMD…
Without disclosing too much, it was an app that stored text messages.
My brother's now ex-wife learned the hard way about the challenges of soft delete. Too bad about the contents of that SQLite database, but his knowing was for the better.