Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kids find a security flaw in Linux Mint by mashing keys

github.com

Post reply on HN
Print view View original

291–300 of 340 posts

Re: Kids find a security flaw in Linux Mint by mashing keys

#291

Post by HDMI_Cable »

smnrchrds wrote: post #257
toyg wrote: post #247

Earlier quoted context omitted.

This is OT, but I can't resist. I've been around HN since 2011, and tone has definitely shifted in the last 5-6 years. I used to stumble on HN posts that infuriated me relatively often, it was part of the deal (i.e. understanding how the self-appointed entrepreneurial classes actually rationalize certain things). That doesn't really happen anymore. > those overlaps would probably translate to some overarching strains…

What I miss about the old HN is learning about all the cool new programming tools, libraries, frameworks, etc and participating in the discussions about them. These days, you rarely see posts about programming tools, unless it is one of the big ones like React, Qt, or TypeScript. I used to stumble upon so many great tools on HN, but that has become a rare experience these days. Is there still somewhere on the web, pe…

Honestly, I think that says something more about Javascript-ifying of the web rather than HN.

Re: Kids find a security flaw in Linux Mint by mashing keys

#292

Post by fao_ »

cycloptic wrote: post #250
GlitchMr wrote: post #183

I find interesting that GNOME Screensaver's security depends on it to not crash. Meanwhile, in KDE the lock screen is managed by KDE Session Management Server which ensures that lock screen cannot be bypassed by simply crashing its process. The way it works is follows: ksmserver draws a black rectangle over everything and spawns kscreenlocker. If kscreenlocker crashes, the black rectangle is still here, and ksmserver…

>I'm not sure why GNOME screensaver cannot do something like this. This actually is fixed in upstream GNOME because the screensaver is now built into the shell. The problem here is exclusively with cinnamon-screensaver and other components derived from gnome-screensaver, which is unmaintained and upstream GNOME considers it obsolete.

[counter-factual information produced by a misreading of what was stated in the github comments - deleted :)]

Re: Kids find a security flaw in Linux Mint by mashing keys

#293

Post by throwaway325 »

smnrchrds wrote: post #257
toyg wrote: post #247

Earlier quoted context omitted.

This is OT, but I can't resist. I've been around HN since 2011, and tone has definitely shifted in the last 5-6 years. I used to stumble on HN posts that infuriated me relatively often, it was part of the deal (i.e. understanding how the self-appointed entrepreneurial classes actually rationalize certain things). That doesn't really happen anymore. > those overlaps would probably translate to some overarching strains…

What I miss about the old HN is learning about all the cool new programming tools, libraries, frameworks, etc and participating in the discussions about them. These days, you rarely see posts about programming tools, unless it is one of the big ones like React, Qt, or TypeScript. I used to stumble upon so many great tools on HN, but that has become a rare experience these days. Is there still somewhere on the web, pe…

>Is there still somewhere on the web, perhaps on Reddit or another platform, where you can find such posts and discussions?

If they exist it would be wise not to link it here, or else the same fate would befall the new community. My advice is to search for a small community around a niche topic (say a specific text editor or programming language).

Re: Kids find a security flaw in Linux Mint by mashing keys

#294

Post by kevin_thibedeau »

canofbars wrote: post #63
krick wrote: post #44

Earlier quoted context omitted.

Oh, so Wayland is finally ready to replace X11?

Whether wayland is ready for you basically comes down to 2 questions: * Do you use a nvidia GPU * Do you need to screen share from electron or other x11 only applications (MS teams, etc) Its ready if you said no to both of those.

Won't it be ready when X11 apps can run inside without issue? X servers on Windows don't have these sort of problems.

Re: Kids find a security flaw in Linux Mint by mashing keys

#295

Post by casept »

canofbars wrote: post #63
krick wrote: post #44

Earlier quoted context omitted.

Oh, so Wayland is finally ready to replace X11?

Whether wayland is ready for you basically comes down to 2 questions: * Do you use a nvidia GPU * Do you need to screen share from electron or other x11 only applications (MS teams, etc) Its ready if you said no to both of those.

The screensharing can be worked around by building a somewhat hacky solution (recording the desktop to an XWayland window and sharing that, for example by using https://gitlab.com/lelgenio/dotfiles/-/blob/master/dotfiles/...).

Re: Kids find a security flaw in Linux Mint by mashing keys

#296

Post by rodgerd »

sbierwagen wrote: post #101
Qub3d wrote: post #94

For everyone linking the JWZ "I Told You So" post, the devs are aware of it and posted a response in the GitHub issue. I encourage everyone to read their side of the issue: https://github.com/linuxmint/cinnamon-screensaver/issues/354...

What context? Reading that issue, the content seems to be: 1: jwz says if you add accessibility features to a text box, make sure they don't have any bugs that can kill a process, since that will break screen lockers 2: Cinnamon adds a buggy accessibility feature to a text box that lets you crash the screen locker 3: Github user clefebvre says something along the lines of "why is jwz being so negative >:(" Well... yo…

> Don't be that guy.

Pretty rich from someone who starts with "I'll fight him in a cage match"

Re: Kids find a security flaw in Linux Mint by mashing keys

#297

Post by freebuju »

smnrchrds wrote: post #268
Naracion wrote: post #262

Earlier quoted context omitted.

I did not get redirected--would that be because I'm using Brave? Or because I'm on mobile?

The former. Brave has explained their referer policy here: https://brave.com/privacy-updates-5/ > When navigating to a new site, never send a referer header. JWZ wouldn't know you are visiting from HN if you use Brave.

Weird. Just tested this, Brave on PC redirected to the image but not on Brave mobile

Re: Kids find a security flaw in Linux Mint by mashing keys

#298

Post by moistbar »

stretchcat wrote: post #87
josefx wrote: post #73

Earlier quoted context omitted.

Given that python versions are incompatible by design you should probably explicitly refer to the version your code supports. At least that is my takeaway from this mess.

This whole situation is a bad trap for novices, given how many tutorials, class slides, etc ask students to copy/paste various invocations of pip and python that may or may not work verbatim on their distro.

Breaking stuff is the first step towards learning to fix stuff.

Re: Kids find a security flaw in Linux Mint by mashing keys

#299

Post by moistbar »

ballenf wrote: post #202
dd_roger wrote: post #145

Earlier quoted context omitted.

> https://discussions.apple.com/thread/7598463 Wow every new person who joins that thread misses the point more than the previous one. This was painful to read.

Here's the last reply before the thread was locked: > I don't see the point of pressing the wrong series of key combinations nine or more times in a row constitutes a "Login Window ScreenShot Problem" any more than dropping my MacBook from various heights until it breaks is a reliability problem. Why do people hold computers to such a lower standard than other complex devices in their life? (Serious question -- I don…

>Unless it happened to early Tesla, because they were held to the lower standard applied to computers and OSs. That doesn't seem to be as true anymore, thankfully.

I've definitely had my Model 3 not unlock when it should, but I've never had it go the other way around.

Re: Kids find a security flaw in Linux Mint by mashing keys

#300

Post by Alvarito050506 »

HDMI_Cable wrote: post #290
smnrchrds wrote: post #268

Earlier quoted context omitted.

The former. Brave has explained their referer policy here: https://brave.com/privacy-updates-5/ > When navigating to a new site, never send a referer header. JWZ wouldn't know you are visiting from HN if you use Brave.

What's the reason behind JWZ doing that anyways?

Because sometimes he behaves like what's in the image.
Post reply on HN