cypherpunks

joined 3 years ago
MODERATOR OF
[–] cypherpunks@lemmy.ml 11 points 3 weeks ago* (last edited 3 weeks ago) (2 children)

you can still use OpenRC instead if you want, and sxmo will continue to do so by default.

you can read here about why they added systemd.

[–] cypherpunks@lemmy.ml 49 points 3 weeks ago (1 children)

in this interview the guy behind the event (Mark Fitzpatrick) says this:

screencap with subtitle "In other words, we're b we're born a certain way with certain tendencies."

screencap with subtitle "and it's, it's um it is sinful, you know, to act out on that."

he's also a flat earther:

screencap of Mark Fitzpatrick wearing a t-shirt that says "fake space by NASA"

[–] cypherpunks@lemmy.ml 9 points 3 weeks ago (6 children)

The acquisition of wealth is no longer the driving force in our lives. We work to better ourselves and the rest of Humanity.

[–] cypherpunks@lemmy.ml 6 points 3 weeks ago* (last edited 3 weeks ago) (1 children)
[–] cypherpunks@lemmy.ml 10 points 4 weeks ago (1 children)

The w700ds/w701ds ("Dual Screen")

... was not Lenovo's last try at putting two screens on a laptop; see also the X1 Fold and Yoga 9i

[–] cypherpunks@lemmy.ml 5 points 4 weeks ago (1 children)

I’m planning on revitalizing and bringing this old Itautec to the 21st century

I think it was born in the 21st century? From this it looks like the first Celeron M was in 2004, and the first at that clockspeed was 2005.

Also, 2GB of RAM is plenty for many purposes - that's more than any Raspberry Pi before the Pi 4 had!

[–] cypherpunks@lemmy.ml 20 points 1 month ago* (last edited 1 month ago) (1 children)

The rest of me is all, “It’s still 2025!! If we have the Bell Riots now we’re still on-pace for a Star Trek future!!”

The Bell Riots were in September 2024.

Our universe's lack of Eugenics Wars in the 90s was already pretty strong evidence that we're not living in the prime timeline.

[–] cypherpunks@lemmy.ml 6 points 1 month ago* (last edited 1 month ago)

Are forks like Librewolf also affected?

Yes

And have they been updated?

Librewolf is in the process of updating; perhaps some distributions of it have released new binaries already but the flathub release is still 139.0.1. In git you can see they bumped the version to get 139.0.4 (the version with the fix) here, 18 hours ago; presumably flathub will get that in the near future.

[–] cypherpunks@lemmy.ml 6 points 1 month ago* (last edited 1 month ago) (1 children)

were you careful to be sure to get the parts that have the key’s name and email address?

It should be if there is chunks missing its unusable. At least thats my thinking, since gpg is usually a binary and ascii armor makes it human readable. As long as a person cannot guess the blacked out parts, there shouldnt be any data.

you are mistaken. A PGP key is a binary structure which includes the metadata. PGP's "ascii-armor" means base64-encoding that binary structure (and putting the BEGIN and END header lines around it). One can decode fragments of a base64-encoded string without having the whole thing. To confirm this, you can use a tool like xxd (or hexdump) - try pasting half of your ascii-armored key in to base64 -d | xxd (and hit enter and ctrl-D to terminate the input) and you will see the binary structure as hex and ascii - including the key metadata. i think either half will do, as PGP keys typically have their metadata in there at least twice.

 

At one point in the wide-ranging, nearly two-hour conversation, Lutnick also said that if Social Security “didn’t send out their checks this month,” his “mother-in-law, who’s 94, she wouldn’t call and complain.”

“She’d think something got messed up, and she’ll get it next month. A fraudster always makes the loudest noise, screaming, yelling and complaining,” the billionaire businessman said.

“Anybody who’s been in the payment system and the processes, who knows the easiest way to find the fraudster is to stop payments and listen, because whoever screams is the one stealing,” he said. “Because my mother-in-law’s not calling, come on, your mother, 80-year-olds, 90-year-olds, they trust the government.”

 

repost, but it's been a while

 

The latest version of Sync for Lemmy (released March 2024) has a bug where attempts to report Private Messages create reports for random comments instead - it creates a report for whatever comment has the same database ID as the private message you're trying to report (which on most instances will be a very old comment, since there are many more comments than private messages).

So: if you're using Sync for Lemmy, unless/until there is a new release of it, please refrain from reporting PMs while using it, to avoid filling instance admins' report queues with spurious reports.

There has been a bit of PM spam lately; please do report PM spam using other clients, so that admins can ban those accounts asap.

If you're interested in trying other Lemmy apps which hopefully get updates more frequently, there is a list of them here: https://join-lemmy.org/apps/

 

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

from the OpenSSH 9.9p2 release announcement:


This release fixes two security bugs.

Security
========

* Fix CVE-2025-26465 - ssh(1) in OpenSSH versions 6.8p1 to 9.9p1
  (inclusive) contained a logic error that allowed an on-path
  attacker (a.k.a MITM) to impersonate any server when the
  VerifyHostKeyDNS option is enabled. This option is off by default.

* Fix CVE-2025-26466 - sshd(8) in OpenSSH versions 9.5p1 to 9.9p1
  (inclusive) is vulnerable to a memory/CPU denial-of-service related
  to the handling of SSH2_MSG_PING packets. This condition may be
  mitigated using the existing PerSourcePenalties feature.

Both vulnerabilities were discovered and demonstrated to be exploitable
by the Qualys Security Advisory team. We thank them for their detailed
review of OpenSSH.
view more: ‹ prev next ›