g-b-r

6 ms·

91.
From Proton to Posteo: Embracing the Underdog(moonwriting.blog)
1 points by g-b-r 3mo ago|0 comments
92.
by g-b-r 3mo ago
Maybe it was quite significant in your news bubble?
93.
by g-b-r 3mo ago
Most of the current comments here are in favor of Örebro, when did tech become so disgusting?
94.
by g-b-r 3mo ago
What a blogpost about Mullvad has to do with tech? When easily half of all HN submissions have no relation whatsoever to tech?
95.
by g-b-r 3mo ago
Ok, I forgot about it, that was with dark mode enabled. Without it it's much better.
96.
by g-b-r 3mo ago
I personally hate the colors; I don't know if it was vibe coded, but it resembles the browns that GPT loves a lot. I'm looking at it from a crappy screen, though.
97.
by g-b-r 3mo ago
> without stomping on freedoms Despite the f. up American idea that people have no expectation of any privacy in public, recording others on behalf of Meta is stomping on freedoms
98.
by g-b-r 3mo ago
Ok, let's not assume (1), plenty of cameras are connected to law enforcement, upload everything to a random cloud service, are trivially accessible by others online, or are made by sketchy Chinese companies.
99.
by g-b-r 3mo ago
"the download of these apps will be completed through Google Play" ( https://support.google.com/googleplay/android-developer/answ... ) So you'll still need to have that installed, and probably to have
100.
by g-b-r 3mo ago
What would this be applied to? Let's check the freshly printed report by the "Special Panel on child safety online and potential age restrictions for social media" ( https://commission.europa.eu/document/d
101.
by g-b-r 3mo ago
It should be stressed that Play Integrity also requires having a Google account and logging in to it on the phone.
102.
by g-b-r 3mo ago
Yeah, sure > hardware and software engineering So, it's firmware or embedded stuff what you had worked on? And maybe you're an electronic engineer? That could make things a bit more understandable, I would be less surprised tha
103.
by g-b-r 3mo ago
> and have been successful in hardware and software engineering for almost 30 years now. as shown by your one day old account
104.
by g-b-r 3mo ago
No, it should be short when there's little to say, and long when there's lots to say about things best written in a commit message
105.
by g-b-r 4mo ago
and that you'd be considered a creep and probably questioned by the police if found with one of those, while we're on a path to be forced to accept people with smart glasses
106.
by g-b-r 4mo ago
There were a lot of concerns about the phones' cameras when they began to spread. Had they been framed like this, and those concerns expressed more loudly, we'd probably have camera covers integrated in all phones now. Instead we&
107.
Reframing smart glasses as 'pervert glasses'(this.weekinsecurity.com)
45 points by g-b-r 4mo ago|16 comments
108.
by g-b-r 4mo ago
To those who say that approving or not this RFC won't make any difference: « - Liaisons: We received liaison statements from multiple SDOs including O-RAN[2], IEEE 802.11[4] and from 3GPP[3] expressing support for the publication of
109.
by g-b-r 4mo ago
Ok, yes, replace "cypher" with cryptographic primitive. Maybe I said cypher for the AES+Serpent mention (and because I like cyberpunk xD)
110.
by g-b-r 4mo ago
> nothing that's happening here has really anything to do with NSA How can you say that??? It seems to be literally only for their claim to need it that pure MLKEM is being requested..! A summary at https://blog.cr.yp.to
111.
by g-b-r 4mo ago
They publish what become standards, you can't just support any existing option in an encryption protocol (if you want to have a secure one).
112.
by g-b-r 4mo ago
> The more cryptography-literate you are, the more likely it is you think hybrids are silly You are if you're considering a cypher that's extremely likely to be secure. In this case we're ok to introduce something with a c
113.
by g-b-r 4mo ago
Was FFDH considered safe? > the implementation history of ECC is godawful You do know that new cryptographic code can be godawful, then?
114.
by g-b-r 4mo ago
> is going around the encryption by hacking endpoints Because they weren't (supposedly) able to break the encryption > than to attack the algorithms You have an opportunity to introduce new, broken, algorithms; they exploited it
115.
by g-b-r 4mo ago
> Perhaps they know something we don't Perhaps https://blog.cr.yp.to/20260704-bugs.html#damage
116.
by g-b-r 4mo ago
We do all have ECC in our cryptosystems right now, and given how long it's been there, we can rely on its security much more than something new.
117.
by g-b-r 4mo ago
Can you (or someone else) please give some example of those environments?
118.
by g-b-r 4mo ago
"two timing leaks, KyberSlash1 and KyberSlash2, in every official reference Kyber implementation from 2017 through late 2023" Cryptographers can be good, bad, be more or less knowledgeable about applied cryptography, and possibly
119.
by g-b-r 4mo ago
If it's documented it will be implemented by many more libraries and applications, that's the argument
120.
by g-b-r 4mo ago
If it's supported it will be used, e.g. by vendors which decide for some reason to use it Null encryption used to be supported as well, and no one was forced to use it. But when something insecure is supported by a protocol it will l

More ›