Avatar
Brunswick
c1e9ab3a56a2ab6ca4bebf44ea64b2fda40ac6311e886ba86b4652169cb56b43
GMβ˜• since [759233](https://mempool.space/block/000000000000000000023ab241141d6cd0d0ea2f41295a830a6724407d450211) [Free Chauvin](https://alphanews.org/exclusive-5-years-later-justice-after-george-floyd-the-dismissed-lawsuit-revealing-the-truth-and-derek-chauvins-response-2/) [WoT](https://npub.world/npub1c856kwjk524kef97hazw5e9jlkjq4333r6yxh2rtgefpd894ddpsmq6lkc) Jesus Christ is Lord

Because there are local offices that are more important

I'm going out to vote, but don't know who for yet. Not because I'm stupid, obviously I have an 80IQ, only that there aren't any choices that will make a difference.

Its designed to be a piece of shit. Sorry to break it to you. Spontaneous channel closures for no evidentiary reason is not acceptable.

Not many people are using self-custodial lnaddress ln nodes to recieve zaps, and for good reason. You can move them off a custodial ln node when the amount becomes concerning.

You can "custody" the token, and it is safe unless the sender rugs you, but you don't own the sats until you redeem them into your own personal lightning channel.

Love adding new terms and expecting it to be widely understood... must we revisit this again?

Self-custodial - you own it

Hardware wallet - you own it

Paper wallet - you own it

Offline wallet - you own it

Hot wallet - you own it for now

Custodial - you don't own it

Coinbase - you don't own it

Someone else's lightning node - you don't own it

Someone else's mint - you don't own it

Non-custodial - fuck if I know

Fully custodial - fuck if I know

Do you remember when a sat was a ten thousandth of a penny? F#*K!

#GrapheneOS: Google is publicly working on a fix for the factory reset vulnerability we reported:

You can see the work Google is doing here:

https://android-review.googlesource.com/c/platform/frameworks/base/+/3008138

Currently, apps using device admin API to wipe do not provide any security against a local attacker since you can interrupt them. Forensic companies are aware of this and take advantage of this.

We weren't sure if they would even consider this to be a valid vulnerability but it was accepted as a High severity issue with a $5000 bounty. We also reported what we consider a far more serious firmware vulnerability which received a $3000 bounty due to not having full info.

They're going to be shipping the mitigation we proposed for preventing obtaining data via exploiting vulnerabilities in firmware boot modes in the April security update. We also proposed software improvements which may ship soon. We aren't sure when factory reset will be fixed.

GrapheneOS provides substantial defenses against obtaining data from devices in the After First Unlock state. We recently made major improvements in this area including our new USB-C port control feature able to disable data lines at a hardware level, unlike the standard feature.

Our USB-C port control is set to "Charging-only when locked, except before first unlock" by default. New USB connections can only be made while unlocked, except BFU. After locking, new connections are blocked immediately and data lines are disabled when existing connections end. We encourage users to use "Changing-only when locked" if they don't need USB devices when the device boots or "Charging-only" if they don't use USB beyond charging. There's also an "Off" value disabling charging when OS is booted into the main OS boot mode for high threat models.

Our auto-reboot feature starts a timer after the device is locked which will reboot the device is it isn't unlocked successfully before the timer elapses. This is set to 18 hours by default but can be set between 10 minutes and 72 hours. It won't chain reboot the device anymore.

Our main defenses against this are our standard exploit protection features:

https://grapheneos.org/features#exploit-protection

Wiping freed memory in kernel/userspace also helps beyond exploit mitigation. We also added full compacting GC for core processes when locking and we're working on much more.

We've planned to support adding a PIN as a 2nd factor for fingerprint unlock since 2016. A new contributor has recently made a lot of progress on it. We'll get it done after duress PIN/password. It will allow using passphrase primary unlock with fingerprint+PIN secondary unlock.

Its badass that grapheneos publishes release notes on nostr

Nobody is ready to hear the truth.

When they do hear it, they twist it into insignificance.

The legislators argue over how much rape we will tolerate without killing them all

The slaves will hate you for not polishing your chains

Democracy is communism.

A republic is fascism.

Stop arguing over what kind of rape you prefer.