Posts
2505
Following
575
Followers
1284
A drunken debugger

Heretek of Silent Signal
repeated

Science for the People poster from 1971 - " workers - join with other workers; make computers serve the people!"

1
8
0
@floyd Precious jailbreakable phones on different versions. Corellium is nice but doesn't support some important I/O like NFC.
1
0
0
repeated
It's one thing that educated people think that using parrots on acid to generate headlines is a good idea. What's terrifying is that people try to spare the work of writing 3 short sentences.

https://www.bbc.com/news/articles/cd0elzk24dno
1
1
2
Why every app icon has to be blue?
0
0
1
repeated
repeated
repeated

Looking at legacy NeXT source:

https://github.com/johnsonjh/NeXTSrc/blob/ff846608a76ab2fbbb86e8a14c52ac85332f9786/libc-34.1/libc/gen/execvp.c#L34

Quoting from the OS X man page for execvp():

"Historically, the default path for the execlp() and execvp() functions was ``:/bin:/usr/bin''. This was changed to place the current directory last to enhance system security."

, , ,

0
3
0
- There are lots of things worse than movies: politicians, wars, forest fires, famine, plague, sickness, pain, warts, politicians...
- You already mentioned them.
- I know I did. They are twice as bad as anything else.

https://m.imdb.com/title/tt0107362/?ref_=ttqu_ov
1
1
4
repeated

JOURNALISM 101 RULE: If someone says it’s raining, and another person says it’s dry, it’s not your job to quote them both. Your job is to look out of the fucking window and find out which is true. — Now more than ever.

7
16
0
repeated
repeated

Important reminder, if you own a domain name and don't use it for sending email.

There is nothing to stop scammers from sending email claiming to be coming from your domain. And the older it gets, the more valuable it is for spoofing. It could eventually damage your domain's reputation and maybe get it blacklisted, unless you take the steps to notify email servers that any email received claiming to come from your domain should be trashed.

Just add these two TXT records to the DNS for your domain:
TXT v=spf1 -all
TXT v=DMARC1; p=reject;

The first says there is not a single SMTP server on earth authorized to send email on behalf of your domain. The second says that any email that says otherwise should be trashed.

If you do use your domain for sending email, be sure to add 3 records:
SPF record to indicate which SMTP server(s) are allowed to send your email.
DKIM record so the receiving email server can confirm the FROM addresses are valid.
DMARC record that tells the receiving email server how to handle email that fails either check.

You cannot stop scammers from sending email claiming to be from your domain, any more than you can prevent people from using your home address as a return address on a mailed letter. But, you can protect both your domain and intended scam victims by adding appropriate DNS records.

26
26
1
repeated

It costs around $50 million every year to ensure Signal is robust and available all over the world for anyone whenever they need it.

And as a nonprofit, that money comes from all of you; the people who believe that we all deserve a place to speak freely.

https://signal.org/donate/

6
28
0
Edited 10 days ago
[RSS] Ghidra Ctrl+P - quick search and command palette plugin.

https://github.com/msm-code/GhidraCtrlP

#Ghidra
0
2
3
repeated
repeated

CISA just took CVE-2024-11053 from 9.1 all the way down to 3.4!

https://github.com/cisagov/vulnrichment/blob/develop/2024/11xxx/CVE-2024-11053.json

2
2
0
repeated

@harrysintonen
This has been updated.

FTR, *anybody* can provide feedback to a vulnrichment entry that's not accurate.
https://github.com/cisagov/vulnrichment/issues

Now, whether this route will get the attention that it may need on a Sunday afternoon is perhaps another story. 😂

1
2
0
repeated

Apparently has rated as v3 Base Score 9.1 "critical". This is wrong, and will lead to automation triggering unnecessary warnings and blocking use of perfectly fine systems until an update is installed (which can take months). https://nvd.nist.gov/vuln/detail/CVE-2024-11053

3
8
0
Show older