HackerTrans
トップ新着トレンドコメント過去質問紹介求人

_rdvw

no profile record

投稿

Notes on Geiger Counters

divested.dev
10 ポイント·投稿者 _rdvw·10 か月前·1 コメント

Google Aiming for Gold

divested.dev
4 ポイント·投稿者 _rdvw·11 か月前·0 コメント

Show HN: Simple TTS augmentative and alternative communication app

udderance.app
2 ポイント·投稿者 _rdvw·昨年·0 コメント

Show HN: Client side mental health screeners

kairoscope.org
1 ポイント·投稿者 _rdvw·昨年·0 コメント

Chrome for Android and Friends: Version History, Security Fix, and Payout Counts

divestos.org
1 ポイント·投稿者 _rdvw·2 年前·1 コメント

コメント

_rdvw
·11 か月前·議論
Please note that their GitHub releases are not libre and contain proprietary Google Play Services libraries.
_rdvw
·昨年·議論
Having to click "Verify you are a human" every single time is still awful.
_rdvw
·昨年·議論
/e/OS ranks poorly and is consistently months behind security updates: https://eylenburg.github.io/android_comparison.htm

Also visual voicemail should actually work just fine on select carriers.
_rdvw
·昨年·議論
Back when I was developing my DivestOS project, test calling 911 was actually a thing I tried to do each month for this reason.

There was one time where I did ship an update that broke select calls but I had it fixed on all devices in under 24 hours.
_rdvw
·昨年·議論
The oneplus3 cannot be relocked as it wrongly trusts test-keys. It also has public EDL firehose files available allowing anyone to flash it arbitrarily even when locked or further dump ram or userdata.

I previously documented this here: https://web.archive.org/web/20250120181249/https://divestos....
_rdvw
·昨年·議論
Briar started in 2011: https://sourceforge.net/p/briar/mailman/message/27393146/
_rdvw
·昨年·議論
Briar is actually even older than that!

2011: https://sourceforge.net/p/briar/mailman/message/27393146/
_rdvw
·昨年·議論
interesting!

I suppose a sufficiently older agesa may actually load the newer microcode then if that was a recent addition in preparation for this
_rdvw
·昨年·議論
recent microcode appears to be rejected by older agesa in my testing, so it is very possible it is more than an implementation issue

under agesa 1.2.0.2b

> microcode: CPU1: update failed for patch_level=0x0a60120c

under agesa 1.2.0.3a PatchA (which asus leaked that it fixes this issue)

> microcode: Updated early from: 0x0a60120c
_rdvw
·昨年·議論
Reminder that AMD has stopped providing microcode updates for consumer platforms via linux-firmware.

index of linux-firmware, 41 cpus supported: https://github.com/divestedcg/real-ucode/blob/master/index-a...

index of my real-ucode project, 106 cpus supported: https://github.com/divestedcg/real-ucode/blob/master/index-a...

sadly, unless you have this recent agesa update you can no longer load recent microcodes due to this fix

which very well means quite a substantial amount of models whose vendors don't provide a bios update for this (since it goes back to zen1) will not be able to load any future fixes via microcode
_rdvw
·2 年前·議論
the updates were all on time: https://divestos.org/misc/ffa-dates.txt
_rdvw
·2 年前·議論
the 21 port was actually largely complete: https://github.com/Divested-Mobile/DivestOS-Build/blob/maste...
_rdvw
·2 年前·議論
it did https://divestos.org/pages/faq#microgEnable
_rdvw
·2 年前·議論
ECH can be used regardless of DoT, DoH, dnscrypt, or plain as long as your resolver passes HTTPS queries.

You can easily test this: dig @8.8.8.8 https pq.cloudflareresearch.com
_rdvw
·2 年前·議論
Please see https://eylenburg.github.io/android_comparison.htm
_rdvw
·2 年前·議論
Firefox 128.0.3 and higher has this globally disabled for Android.
_rdvw
·2 年前·議論
I added payout counts after seeing a comment on a recent thread here.

Script here: https://github.com/Divested-Mobile/DivestOS-Website/blob/mas...

There is also a Firefox version here: https://divestos.org/misc/ffa-dates.txt
_rdvw
·2 年前·議論
Also if you don't have a bios update available for that newer microcode, give my real-ucode package a try: https://github.com/divestedcg/real-ucode

The linux-firmware repo does not provide AMD microcode updates to consumer platforms unlike Intel.
_rdvw
·2 年前·議論
KPTI won't be default enabled on Linux on AMD CPUs is the issue here.

Yet it provides valuable separation between kernel and userspace address ranges.

iirc the predecessor to KPTI was made before these hw flaws were announced as a general enhancement to ASLR.

AMD aside, Spectre V2 isn't even default mitigated for userspace across the board, you must specify spectre_v2=on for userspace to be protected.

https://www.kernel.org/doc/html/latest/admin-guide/kernel-pa...
_rdvw
·2 年前·議論
That row covers whether or not the opt-in/out is provided during setup wizard, not post install.

If there is such an option then you can report it here: https://github.com/eylenburg/eylenburg.github.io/issues