HN user

genr8

11 karma
Posts0
Comments35
View on HN
No posts found.

the Gentoo Wiki is also high on my list, actually first because Gentoo is my preferred choice, equal in terms of useful content, only second in userbase - to Arch. Gentoo also implemented a policy prohibiting people from contributing LLM output. Theres not a culty rule-following edit-sanitization mod team, and the wiki doesnt require special permission, just the honor system, but so far its enough to make me like contributing to it is a form of charity to help future mankind.

The Coming Soon columns make it hard to see the two main price and name columns on mobile small screen at the same time. I wish to hide those. But nice idea.

"At 10% threshold, assuming a 10-μs code cycle and non-local connections, one key can be generated every 10 minutes using 6000 modules with 1152 physical qubits each."

1152 qubits sounds like the D-Wave chips. So does that mean 6000 D-wave chips ?

Even if you reverse the calculation, that would be 60000 minutes on 1 chip, which is about 42 days only, so. Quantum Too Good

now here we have "X considered harmful" - a common Trope. This seems more like a "First!" to title their paper this, as a meme of the whitepaper meta, that title came first, then the arguments came. I say this because I joked about a paper being released with this name about a week ago and now here it is, but Its a bit lower quality than expected. We might need another one later...

a similar situation just happened between Nvidia and EVGA. NVidia makes the chips, And So, holds all the bargaining chips so to speak, and EVGA is just the board partner that has to find some way to make the price work. At some point it becomes impossible and they have to actually walk away in order to not be taken advantage of. We know this much, and I'm going to assume the situation was similar here with Apple and Wistron.

I can't believe [What do they have to hide?] was even seriously spoken here. Im not the only one who believes this glows exactly like a state-sanctioned hitjob. This was cyber-warfare. https://www.youtube.com/watch?v=f5a42XuzPLk An average fair video on the hack - but Read the comments.

Anonymous is not bashing the fash, they now do the bidding of the far-left Establishment, enforce state-approved Censorship and Cancel Culture of any dissidents against the monoculture cathedral regime - who now just are your average regular independents, libertarians, and freedom loving populists.

Anyone who still falls for "but they're nazis and fascism is bad mmk" is either dishonest or not following this subject matter. Just because you don't like someone doesnt mean they're nazis.

I doubt this is even Anonymous. The real Anonymous would not be hacking companies providing free speech (no matter how bad the security).

One step closer to anarcho-tyranny. Anonymous has become the Antifa of the Internet. Basically a far-left strike force, cloaked but public, with enough plausible deniability that the 3 letter agencies allow to exist because they can do things beyond the law - as long as they dont go after the gov... One has to wonder why they are so focused on [Combating far right extremism and misinformation] when it's clearly designed to benefit the overall establishment system status-quo. Even _if_ this whole Operation Jane anti anti-abortion-law texas hacktivism politics made sense to someone, it now has a much larger effect on the internet as a whole. Epik - one of the last hosting providers on the internet in favor of absolute free speech (within the law) that still exists. The risk/reward equation doesnt add up. More innocent rights are being violated with this hack alone compared to saving womens abortion rights.

I havent confused them. Its phrased like that to alert people they can't change the key strength by bit-ness, but they can change the KDF password-strength, on GENERATION, which is peoples first gateway into Ed25519. And X448 opens another can of worms, ssh-keygen still does not support that algo. OpenSSL 1.1.1 does, with: openssl genpkey -algorithm Ed448 but that doesn't relate to this discussion of use for SSH public keys. The support is very bare bones and only allows C code access meant for use in TLS servers, not SSH command line tools. They recently added EVP_PKEY_get_raw_public_key() relating to Ed25519/Ed448 but that doesnt help in actually running a command to generate these X448 algo Curve keys yourself for use in SSH keys.

So if you know how to use X448/Ed448 public/private keypairs with SSH, do tell.

4096 _does_ take a lot of extra CPU resources, and it _is_ diminishing returns. But anyone who prioritizes this above all else is arguing either from a vantage point of distributed scaling across servers that cost money to handle millions of extra cycles per key times millions of keys, or from a place of defending the status quo just for the sake of defending their past choices, which I hate. Their motives for defending it have to be questioned. The page says you gain very little, because by this point we are moving away from RSA to elliptic curves, from which you gain A LOT. Section 11.5 states: "If you need more security than RSA-2048 offers, the way to go would be to switch to elliptical curve cryptography — not to continue using RSA." This is the entire point of this HN Thread. A lot of smartcard and hardware vendors have a vested interest in the status quo 2048-bit RSA because they are stingy with embedded CPU resources or monetary resources in the cost of switching algos. And theres specifically an issue with GNUPG and Elliptic Curves and license compatibility https://www.yubico.com/blog/big-debate-2048-4096-yubicos-sta... If you are an end-user with personal keys only, and fast computers, switching to a 3072 or 4096 bit key is a no brainer. The largest overhead of additional CPU cycles is only consumed on generation, not on verification. Interoperability is nearly always ensured, and you gain some 16% percent security (which is NOT "almost nothing"). Beyond that, you should switch to Ed25519 (which uses less CPU resources anyway). Continuing to argue this point is beyond the scope of this discussion. You can research yourself why RSA-2048 is being deprecated, and everyone who can switch is switching Ed25519. Or maybe the OP will write another blog post better than I can, since nobody listens to me anyway. The point was to get you to switch away from RSA, not continue using it with 4096.

I didnt say it wasn't enough. I said you should upgrade to elliptic curve crypto, or if you have to stay on RSA, re-generate with 4096 because it's better. A 2048 bit RSA key only provides 112 bits of security - claimed to be suitable until the year 2030. RSA-2048 is still techncially ALLOWED by NIST, but that is the literal cutoff mark, below which is disallowed. The spec dates back to 2012 with "NIST Special Publication 800-57 Part1". This specification is up to Revision 5 now, the most recent of which is named "NIST Special Publication 800-57 Part 1 rev 5" published May 2020. https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.S... . There is no new news regarding the 2048 length since 2012. This estimate also does not factor in CLASSIFIED quantum cryptography thats hidden from the public. I personally don't trust them after the Snowden documents either. Plenty of sites are still using 2048 for compatibility and speed, but if you are re-generating your key now, its advised to upgrade to elliptic curve, or if you must stick on RSA, 3072 or 4096, because 2048 is the literal cutoff point. This document also describes the migration process. NIST SP 800-131A Rev. 2 - Transitioning the Use of Cryptographic Algorithms and Key Lengths https://csrc.nist.gov/publications/detail/sp/800-131a/rev-2/...

Exactly, I was trying to point this out, that they were seperate. I only mention increasing the rounds of your passphrase in the same sentence because you do this when generating the key to increase security, and if you don't specify it, it gets overlooked. You don't have to specify any additional bits in the key strength, but you should specify additional rounds in the passphrase. Agreed they are unrelated reasons internally, but its a good way to add an additional level of protection.

There is a good reason, its just buried in complex crypto math and I won't be the one to explain it for you. If you are still using RSA, you should have upgraded to 4096 bit RSA by now. If not, you should be regenerating and changing your keys and not using one 5 or 10 year old 2048-bit RSA key because "2048 should be enough for anyone" and not thinking "I reused this key all over the place and im lazy and i'm sentimental and don't like change". People's key practices are just as bad as their password practices. His personal blog post was not meant to be a comprehensive lesson. But you can do what you want.

If this is the first time you're hearing about RSA starting to be phased out, and the new Ed25519, look into it. Or click this if you're lazy. https://medium.com/risan/upgrade-your-ssh-key-to-ed25519-c6e...

Also of note, is Ed25519 does not harden itself with additional "bits" in the normal RSA sense, it relies on "rounds" of KDF to apply more brute-force protection to the passphrase (you did set a passphrase on your key right?). I would suggest using the -a option with 1000 or more rounds. If you pick 50,000 rounds you might be waiting 5 minutes to log in though.

Also of note, ECDSA (the other one) has had curve trust concerns due to NIST possibly being subverted by the NSA. You can read for days on this, but bottom line is we've all agreed to move on. https://security.stackexchange.com/a/227771 / https://safecurves.cr.yp.to/

Yea. But that was added later, and theres still important JSON build-system files that you need to edit manually to this day. JSON isnt descriptive enough to auto-translate the raw files into a functional GUI. They seem to think its better off as text, but that goes against everything else on Windows mentality, and its not documented properly.

Microsoft is so large, and so disjointed, its not as simple as you make it out to be. The corporate culture prevents it. You forgot all the bureaucratic middle managers whos sole job is to enforce IT Silo'ing and gatekeep other teams from intruding into their area. I hate to say it like this, but the boomers created this mentality on purpose. Its rampant in incumbent tech/IT/dev, and fundamentally opposed to freedom of information and open source, because its focused on maintaining control and power and keeping people in their pre-designated place. If it was only a tech problem, we could absolutely solve this, but its a socio-political one first.

MS is so large, one hand doesn't know what any other division is doing, and their community interaction is horrible because they make more money when people are ill informed and just go with the flow. So even if 10% of the company is "new blood" and was pushing open source out the back door for the past 5 years, the upper management is just now catching on that "hey maybe they were right".

M$ will only open source things that don't make them their money, while at the same time, tricking developers that they care by appropriating the communities work and extracting as much value out of Linux for free as possible, for their own benefit. Providing second rate hybrids masquerading as innovations, is all they can really do, to keep people locked into Windows. I stayed on Windows desktop for 20 years even while using linux for servers, and just gave it up this year. Linux has its own problems but if I disagree with the status quo of programs, I can either switch to another distro, mod the open source code myself, or file a bug report so a real person actually does something about it. This is too little, too late, from Microsoft, and accepting it now will just lead to the demise of Linux.

This is a warning sign that we have 0 agency over hard drives we think we own. The corporations control the actual tech being pushed, to pull a bait and switch. They also control the firmware, which is super proprietary and hidden, and can be subverted and controlled without your knowledge. The end goal is to push consumers to end up storing all their data in the cloud.

THE TAXONOMY OF PRIVACY: by Daniel J. Solove (84 Pages Posted: 16 Feb 2005) Table of Contents:

A. Information Collection -1. Surveillance -2. Interrogation

B. Information Processing -1. Aggregation -2. Identification -3. Insecurity -4. Secondary Use -5. Exclusion

C. Information Dissemination -1. Breach of Confidentiality -2. Disclosure -3. Exposure -4. Increased Accessibility -5. Blackmail -6. Appropriation -7. Distortion

D. Invasion -1. Intrusion -2. Decisional Interference