News for hackers. Stuff that matters.

dvorak_typist

Re:Apple vs. Meta: The Illusion of Privacy on Sunday September 10, 2023 @01:48PM (#37458192)
Advertising (verb): Military Propaganda targeting a Civilian Population in order to get that population to spend money on products they would not otherwise purchase.
So the Zoom CEO doesn't want Zoom data going to ChatGPT, like he does with all customer data??? Signals...
Re:Show HN: Gemini web client in 100 lines of C on Wednesday July 19, 2023 @05:50PM (#36793960)
The way he seems to have written 'C' is to use the C preprocessor and Macros to create a domain specific language and then write the program in that! Mind Blown!
Re:No One in the U.S. Wants to Buy Electric Vehicles on Monday July 10, 2023 @04:16PM (#36672329)
Or perhaps between interest rates and working 4 jobs nobody can afford to give billionaires anymore of their future incomes?
Re:Threads reached 100M sign ups over the weekend on Monday July 10, 2023 @03:52PM (#36672031)
Hoorah. A bunch of slaves now owned by a different billionaire. such change.
InSecurityNow? Fuck'm with prejudice. Keep digging.

RCE as admin has been a problem for over a decade. _Globally_ sessions do not expire... This is just the tip of the shit architecture iceberg.

There are many ways attackers & hackers 'verify' black-box systems regularly. For example: Cause effect Graphing – This technique establishes a relationship between logical input called causes with corresponding actions called the effect. The causes and effects are represented using Boolean graphs. In fact it is precisely due to the desired side effects that allow attackers the ability to detect, and reverse engineer the system. This is not easy, but it is not at all undetectable, or irreversible.
You should never remove a fence that you do not know the purpose of. The code you don't understand was not created by an idiot! And fences do not grow spontaneously. That person was solving a problem, and that problem had requirements those requirements are what this code is at least a solution for.

If you don't understand the requirements, you likely don't understand the solution and potentially the problem either. In such circumstances it is best to either not intervene, or take the time to familiarize yourself with both the problem and the solution before you attempt to intervene.