#grapheneos

190 posts · Last used 5d

Back to Timeline
eteryu @eteryu@infosec.exchange · 6d ago
Często powtarzanym mitem w świecie cyfrowej higieny jest przekonanie o magicznej prywatności prosto z pudełka. W nowym wpisie na blogu rozkładam na czynniki pierwsze architekturę microG oraz obietnice popularnych systemów. Wyjaśniam zjawisko teatru prywatności oraz dlaczego poleganie na domyślnych ustawieniach to pułapka. Prawdziwe bezpieczeństwo to nawyki, a nie tylko zmiana oprogramowania. Pełny tekst znajdziecie tutaj: https://eteryu.space/zudzenie-prywatnosci-z-pudeka-dlaczego-podejscie-set-and-forget-to-puapka/ #infosec #prywatnosc #cyberbezpieczenstwo #grapheneos #android #degoogle #cyberhigiena #opsec
8
9
5
eteryu @eteryu@infosec.exchange · Aug 07, 2026
Używacie Obtainium na GrapheneOS z włączonym Mullvadem lub innym VPN i ciągle wyskakuje wam błąd "Too Many Requests"? To efekt uboczny współdzielonego IP, przez co błyskawicznie wyczerpuje się limit anonimowych zapytań do API GitHuba. Da się to naprawić w minutę. Musicie tylko mieć lub założyć darmowe konto na GitHubie. Następnie wchodzicie tam w ustawienia konta, w sekcji Developer Settings otwieracie dokładnie zakładkę Tokens (classic) i generujecie nowy Personal Access Token. Co kluczowe, przy jego tworzeniu nie zaznaczacie absolutnie żadnych uprawnień. Taki pusty token wklejacie w ustawieniach dostawców w Obtainium. Wasz limit skacze z 60 do 5000 zapytań na godzinę i aktualizacje z powrotem śmigają bez zająknięcia. #grapheneos #obtainium #vpn #github #foss
0
0
0
GrapheneOS @GrapheneOS@grapheneos.social · Aug 06, 2026
GrapheneOS version 2026080500 released: https://grapheneos.org/releases#2026080500 See the linked release notes for a summary of the improvements over the previous release. Forum discussion thread: https://discuss.grapheneos.org/d/40968-grapheneos-version-2026080500-released #GrapheneOS #privacy #security
4
0
1
Red @r3dr3clus3@infosec.exchange · Aug 05, 2026
Is Seedvault still the way to backup GrapheneOS? If so, is Seedvault still hit or miss? My attention has been elsewhere for a bit and I've heard rumors a better way was in the works; is that here/still in the works? @GrapheneOS@grapheneos.social #grapheneos #graphene_os
1
1
0
Oscar @oscaractual@infosec.exchange · Aug 04, 2026
First known US federal prosecution over a phone's duress PIN: a traveler at Atlanta airport hands border agents a passcode, the device (GrapheneOS, per the indictment) irreversibly wipes itself - and he's now charged with destruction of property to prevent seizure. Up to 5 years. He's pleaded not guilty; a court decides this fall whether destroyed key material counts as "property." The operational lesson isn't about the tool. The tech did its job - the keys are unrecoverable, exactly as designed. Owning it is legal - triggering it during an active search is what produced the charge. A safeguard became a legal problem at the exact moment it was supposed to protect. After 30 years in security ops, my travel rule is simpler: the best defense isn't a wipe button, it's a device with nothing on it. Clean device or clean work profile · only what the trip needs · mail in the browser, nothing offline · company access and VPN after arrival · backups stay home. What you don't carry can't be seized - and nothing gets destroyed. Not just a US thing: under Schedule 7 in the UK, port officers can demand device passwords with no prior suspicion, and refusing can itself be an offence. Source: https://techcrunch.com/2026/07/24/us-accuses-american-of-allegedly-wiping-his-phone-using-a-duress-password-during-border-search/ #opsec #privacy #infosec #grapheneos
0
0
0
samurro @samurro@fosstodon.org · Aug 04, 2026
Can somebody remind me when #GrapheneOS is finally properly supporting non-Pixel #google devices?? I hope my current devices lasts until then...
0
2
0
six_grandfathers_mountain @six_grandfathers_mountain@mastodon.social · Aug 01, 2026
Replying to @pierre_pebble@mastodon.ie
@pierre_pebble@mastodon.ie @404mediaco@mastodon.social Re normalize #privacy. The more people use #GrapheneOS But, only a few #smartphones can use that OS, still it's a good choice for _some_ of the billions of users 404Media has an audio podcast, they mentioned, the guy at the airport, maybe it was the #TSA agent who typed in the 4 number PIN? So, who bricked the phone? The TSA or the guy speaking the PIN? What I recommend is to (stupidly) have the (brick) PIN written on the case, maybe vertically to "hide" it🤣
3
1
0
RaymondPierreL3 @RaymondPierreL3@aus.social · Jul 31, 2026
Replying to @Hyperlynx@aus.social
@Hyperlynx@aus.social Have you looked at #Pixel mobiles running #GrapheneOS ?
0
1
0
GrapheneOS @GrapheneOS@grapheneos.social · Jul 30, 2026
GrapheneOS Camera app version 91 released: https://github.com/GrapheneOS/Camera/releases/tag/91 See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog. Forum discussion thread: https://discuss.grapheneos.org/d/40836-grapheneos-camera-app-version-91-released #GrapheneOS #privacy #security #camera #android
23
3
8
GrapheneOS @GrapheneOS@grapheneos.social · Jul 30, 2026
Secure PDF Viewer app version 33 released: https://github.com/GrapheneOS/PdfViewer/releases/tag/33 See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog. Forum discussion thread: https://discuss.grapheneos.org/d/40835-secure-pdf-viewer-app-version-33-released #GrapheneOS #privacy #security #pdf #android
7
0
2
Sudo Sudo Sudo ⒶⒺⓋ @Prometheus@infosec.exchange · Jul 30, 2026
josh@sideofburritos just uploaded a great take on the incident with the activist that used the distress pin on the boarder patrol gestapo. Not up publicly yet, but this has made me ponder on the new threat model of what we face as activists in the US and other repressive regimes. And for the fine fellows at #grapheneos of which I have been on for a few years now. Could the distress pin trigger a profile(s) deletion and open a honeypot user profile? That would be a nice touch eh?
0
1
0
Paepke @paepke@chaos.social · Jul 30, 2026
Business Apps des Arbeitgebers wurden wieder von meinem nicht rooted #GrapheneOS geworfen (weil es angeblich rooted wär). Gibt viele Artikel dazu wie #microsoft es einfach nicht kapiert. Also kümmert man sich offensichtlich um meine #workLifeBalance #SarcasmButOnyHalf
3
4
0
GrapheneOS @GrapheneOS@grapheneos.social · Jul 30, 2026
Vanadium version 151.0.7922.71.0 released: https://github.com/GrapheneOS/Vanadium/releases/tag/151.0.7922.71.0 See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog. Forum discussion thread: https://discuss.grapheneos.org/d/40822-vanadium-version-15107922710-released #GrapheneOS #privacy #security #browser
4
0
6
Okuna @Okuna@social.tchncs.de · Jul 30, 2026
Ich habe eine Frage an die @GrapheneOS@grapheneos.social #grapheneos Benutzer. Ich habe eine neue Telefonnummer, aber keine neue SIM-Karte. In GrapheneOS an allen Stellen, wo Telefon oder mein SIM-Kartenanbieter stehen, steht immer noch die alte Telefonnummer. Wenn ich aber anrufe oder SMS verschicke, kommt sie von der neuen. Das heißt, die Anzeige wurde nicht aktualisiert. Ich habe das Handy ausgeschaltet, ich habe die SIM-Karte rausgenommen und wieder eingesetzt. Das macht alles keinen Unterschied. Woran liegt das?
0
2
0