cypherpunks

joined 3 years ago
MODERATOR OF
[–] cypherpunks@lemmy.ml 12 points 9 months ago

The headline should mention that they're breaking 22-bit RSA, but then it would get a lot less clicks.

A different group of Chinese researchers set what I think is the current record when they factored a 48-bit number with a quantum computer two years ago: https://arxiv.org/abs/2212.12372

I guess the news here is that now they've reached 22 bits using the quantum annealing technique which works on D-Wave's commercially-available quantum computers? That approach was previously able to factor an 18-bit number in 2018.

🥂 to the researchers, but 👎 to the clickbait headline writers. This is still nowhere near being a CRQC (cryptanalytically-relevant quantum computer).

[–] cypherpunks@lemmy.ml 9 points 9 months ago* (last edited 9 months ago)

i think the bottom text has it wrong.

this is probably a stronger argument to get people to vote for her:

"Kombucha Girl" meme, disgusted face what she'll do

"Kombucha Girl" meme, reconsidering face what her opponent won't be able to do if she wins.

[–] cypherpunks@lemmy.ml 7 points 9 months ago

headline was more exciting before i read the last four words of it

[–] cypherpunks@lemmy.ml 30 points 9 months ago* (last edited 9 months ago) (2 children)
[–] cypherpunks@lemmy.ml 20 points 9 months ago* (last edited 9 months ago) (6 children)

i can't help but wonder if there isn't some more useful science that these scientists could be doing (i write, while reading garbage on the internet)

[–] cypherpunks@lemmy.ml 10 points 9 months ago (1 children)
[–] cypherpunks@lemmy.ml 2 points 9 months ago

I don’t think any of his stuff would seem shocking by today’s standards.

See this example earlier in the thread.

[–] cypherpunks@lemmy.ml 2 points 10 months ago (3 children)

Or you could just… learn to use the modern internet that 60% of internet traffic uses? Not everyone has a dedicated IPv4 anymore, we are in the days of mobile networks and CGNAT. IPv4 exhaustion is here today.

Where are you getting 60%? Google's IPv6 Adoption page has it under 50% still:

Screenshot of Google saying "IPv6 Adoption / We are continuously measuring the availability of IPv6 connectivity among Google users. The graph shows the percentage of users that access Google over IPv6." with a graph climbing from near 0% in 2008 to 45% in September 2024

(while other stats pages from big CDNs show even less)

[–] cypherpunks@lemmy.ml 1 points 10 months ago

If you have ::/0 in your AllowedIPs and v6 connections are bypassing your VPN, that is strange.

What does ip route get 2a00:1450:400f:801::200e (an IPv6 address for google) say?

I haven't used wireguard with NetworkManager, but using wg-quick it certainly adds a default v6 route when you have ::/0 in AllowedIPs.

[–] cypherpunks@lemmy.ml 2 points 10 months ago* (last edited 10 months ago) (2 children)

You could edit your configuration to change the wireguard connection's AllowedIPs from 0.0.0.0/0 to 0.0.0.0/0,::/0 so that IPv6 traffic is routed over it. Regardless of if your wireguard endpoint actually supports it, this will at least stop IPv6 traffic from leaking.

 

cross-posted from: https://hexbear.net/post/3613920

https://archive.ph/tR7s6

Get fuuuuuuuuuuuuuucked

“This isn’t going to stop,” Allen told the New York Times. “Art is dead, dude. It’s over. A.I. won. Humans lost.”

"But I still want to get paid for it."

 

edit: after 20 comments, i'm adding a post description here, since most of the commenters so far appear not to be reading the article:

This is about how surprisingly cheap it is (eg $15,000) to buy a complete production line to be able to manufacture batteries with a layer of nearly-undetectable explosives inside of them, which can be triggered by off-the-shelf devices with only their firmware modified.

screenshot of paragraph from the article saying "The process to build such batteries is well understood and documented. Here is an excerpt from one vendor’s site promising to sell the equipment to build batteries in limited quantities (tens-to-hundreds per batch) for as little as $15,000:" followed by a screenshot of "Flow-chart of Pouch Cell Lab-scale Fabrication" showing a 20 step process

 

cross-posted from: https://lemmy.ml/post/20502769

here is the talk description, from its page on the schedule for KubeCon + CloudNativeCon + Open Source Summit China 2024 (which Linux Foundation somehow neglected to put in their youtube upload's description):

In Febuary the Linux kernel community took charge of issuing CVEs for any found vulnerability in their codebase. By doing this, they took away the ability for any random company to assign CVEs in order to make their engineering processes run smoother, and instead have set up a structure for everyone to participate equally.

This talk will go into how the Linux CVE team works, how CVEs are assigned, and how you can properly handle the huge number of new CVEs happening in a simple and secure way.

今年二月,Linux内核社区开始负责为其代码库中发现的任何漏洞发布CVE编号。通过这样做,他们剥夺了任何随机公司分配 CVE 的能力,以便使他们的工程流程更顺畅,取而代之的是建立了一个人人平等参与的结构。

本次演讲将介绍 Linux CVE 团队的工作方式,CVE 的分配过程,以及如何以简单且安全的方式妥善处理大量新出现的 CVE。

Here is a PDF of the slides from Greg's git repo for this talk.

 

here is the talk description, from its page on the schedule for KubeCon + CloudNativeCon + Open Source Summit China 2024 (which Linux Foundation somehow neglected to put in their youtube upload's description):

In Febuary the Linux kernel community took charge of issuing CVEs for any found vulnerability in their codebase. By doing this, they took away the ability for any random company to assign CVEs in order to make their engineering processes run smoother, and instead have set up a structure for everyone to participate equally.

This talk will go into how the Linux CVE team works, how CVEs are assigned, and how you can properly handle the huge number of new CVEs happening in a simple and secure way.

今年二月,Linux内核社区开始负责为其代码库中发现的任何漏洞发布CVE编号。通过这样做,他们剥夺了任何随机公司分配 CVE 的能力,以便使他们的工程流程更顺畅,取而代之的是建立了一个人人平等参与的结构。

本次演讲将介绍 Linux CVE 团队的工作方式,CVE 的分配过程,以及如何以简单且安全的方式妥善处理大量新出现的 CVE。

Here is a PDF of the slides from Greg's git repo for this talk.

view more: ‹ prev next ›