11 ms·
Jwz: I told you so, 2021 edition
- rcarmo 6y agoArchive org link because Jamie has strong feelings about being linked from HN (even down to blocking the folk on Twitter who do so).
- MonkeyIsNull 6y agoThanks, I was wondering what in the world was up with that.
- u801e 6y agoThis is what happens if you link to his website from HN. Arguably NSFW: https://www.jwz.org/blog/2021/01/i-told-you-so-2021-edition/ https://www.jwz.org/blog/2021/01/i-told-you-so-2021-edition/
- higerordermap 6y agoI Got the proper page?
- u801e 6y agoI found when using Firefox, it did take me to the proper page. When using Google chrome, was redirected to the landing page I was referring to. Which browser did you use? Testing it again in Firefox took me to the landing page. Maybe it doesn't redirect every single time.
- pritambaral 6y agoIt works by detecting the HTTP Referer header. Under certain circumstances of privacy, Firefox strips the header. For example: https://blog.mozilla.org/security/2018/01/31/preventing-data-leaks-by-stripping-path-information-in-http-referrers/ https://blog.mozilla.org/security/2018/01/31/preventing-data... It is plainly obvious why Google's browser might not want to do something like that.
- bzb6 6y agoLinux still not ready as a desktop operating system, news at eleven.
- shrimp_emoji 6y agoWell, more like the Cinnamon DE isn't. And, yeah, if you stray from the two superpower DEs with the most dev polish (KDE and GNOME), you're asking for jank and bugs.
- eqvinox 6y agoDid you even read the article? "Hold enter, unlock Gnome-screensaver." https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308572 https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308572 If you go back to an older GNOME version you can probably also find the current Cinnamon bug in there, it is in libcaribou after all.
- noir_lord 6y agoI switched from XFCE to Cinnamon after I couldn't get on with Gnome, Cinnamon is (for my use case) way less "janky" than Gnome since the only way to get close to what I consider a pleasant productive desktop on Gnome is to install a bunch of very buggy plugins. Cinnamon at least makes operating like a classic DE a first order priority and it works nice across multiple screens. KDE does the same but aesthetically KDE drives me crazy for some reason starting with the complete lack of standardisation on padding and going down hill from there.
- yongjik 6y agoWell, as someone who recently switched from Cinnamon to Gnome: - There's no hibernate button. You can hibernate... by running "sudo pm-hinernate" on terminal. - There's no session save, like, really. - pm-hibernate sometimes fails without a single error message. Turns out it would refuse to run when the kernel was updated, OK fine that makes sense, except that the error message is redirected to /var/log/something and hidden beneath hundreds of lines of noise. The only nice thing about it is that fractional scaling mostly works, which is nice, because I happen to have one 1080 and one 4K monitor. I'm sorely tempted to move to KDE but then I couldn't figure out how to make fractional scaling work there. It's a total mess.
- mindslight 6y agoAnother approach to splitting out the lock dialog would be to fire up another whole X server. That would be so bloated, the desktop environment developers might just go for it.
- eqvinox 6y agoThe bloat isn't in the X server, it's in the DE itself. You can start an X server and an xterm (without even a window manager) on pretty much an empty tank.
- captainmuon 6y agoI think Ubuntu already runs a separate X or Wayland instance for the login screen. If you press Ctrl+Alt+F2 / F3, you can switch between the login screen and the current desktop. I don't know if this is the default or if I did something to enable it, though. It could be this only happens if you use the "switch user without logging out" function. Coincidentially, Windows does something similar a lot. UAC prompts run on a different Desktop which is completely separate, the log in screen is separate, as well as the secure attention screen (what you get when you press Ctrl-Alt-Del).
- muth02446 6y agoAlternative for screen locking on Linux https://github.com/google/xsecurelock https://github.com/google/xsecurelock
- hedora 6y agoWhy use this instead of xscreensaver? The security architecture looks similar.
- Liskni_si 6y agoSimilar, but taken further. xscreensaver still does input and PAM auth in the main process, xsecurelock does not, so the attack surface is smaller.
- lrossi 6y agoNo thanks. There is no reason to have apache, mplayer and mpv as a dependency for a screensaver “designed for security”.
- protomyth 6y agoXScreenSaver was released under the BSD license, one of the oldest and most permissive of the free software licenses. It turns out, the Gnome-screensaver authors copied large parts of XScreenSaver into their program, removed the BSD license and slapped a GPL license on my code instead -- and also removed my name. Rude. That's troubling. How do people expect the GPL to be respected when distributions don't respect other people's licenses?
- u801e 6y agoThe commit message [1] removing JWZ from the AUTHORS file isn't very informative. [1] https://web.archive.org/web/20210116154429/https://gitlab.gnome.org/Archive/gnome-screensaver/-/commit/a92d2415810723eb394558ba1aa61f7a6d62611d https://web.archive.org/web/20210116154429/https://gitlab.gn...
- hedora 6y agoThat’s… not how derivative works and copyright work.
- athms 6y agoLots of GPL advocates think they can re-license BSD as GPL because BSD is permissive. Of course, there is nothing in the BSD license allowing this, only the copyright holder can re-license.
- protomyth 6y agoThis isn't relicensing it's removed of a person's copyright. That would not go well if it was done to them.
- athms 6y agoThe code in question was re-licensed under GPL without the author's permission. And according to the BSD license, the copyright must remain intact. A person can use BSD licensed code in a larger work under GPL or they can put the modifications under GPL, but they have no authority to change the original BSD license. The belief of being able to re-license BSD code is quite prevalent in the Linux community and is often espoused here on Hacker News.
- dmm 6y agoI'm really starting to understand why jwz left software and bought a nightclub. swaylocker, the wayland screen locker I'm currently using has the exact same architectural flaw: crash the dialog and get access to the desktop. https://github.com/swaywm/swaylock/issues/162 https://github.com/swaywm/swaylock/issues/162 https://github.com/swaywm/swaylock/issues/158 https://github.com/swaywm/swaylock/issues/158 https://github.com/swaywm/swaylock/issues/10 https://github.com/swaywm/swaylock/issues/10
- hedora 6y agoHeh. I’ve seen Wayland proponents cite the “impossibility” of screen locking in X11 as a reason to rewrite the entire thing from scratch. I’ve also seen this argument from the systemd crowd (spoiler alert: the logind ecosystem is also unreliable).
- dmm 6y ago> Heh. I’ve seen Wayland proponents cite the “impossibility” of screen locking in X11 as a reason to rewrite the entire thing from scratch. Supposedly Gnome is better but I have no idea. EDIT: I also found this looking through github issues. It's not only a know issue, it's a WONTFIX: >> This also brings up a good point. If sway detects that swaylock (or whatever locking process is used) didn't exit cleanly, it should try and recreate it, so we don't just end up giving the a malicious user access to the session. > I don't think this is worth it https://github.com/swaywm/sway/issues/2031#issuecomment-392038949 https://github.com/swaywm/sway/issues/2031#issuecomment-3920...
- mscarborough 6y agoDirectly below the supposedly juicy "I don't think this is worth it" comment is a merged PR linked to this issue. In that PR they changed the render loop rather than implement the "not worth it" suggested solution. At no point was it marked as WONTFIX.
- hpfr 6y ago
- Jkvngt 6y agoThe GNOME / IBM / Red Hat crew (all the same money pumping them) have often relicensed things when they see fit, without asking the original authors if it's OK. But I think we are all starting to understand the large difference between a company-driven and nominally "open" project, governed by a commercial entity, and a true community project. WONTFIX
- lrossi 6y agoSee also: https://github.com/dstat-real/dstat/issues/170 https://github.com/dstat-real/dstat/issues/170
- tekacs 6y agoThis thread expands quite a bit more on the above topic: https://github.com/dstat-real/dstat/issues/156 https://github.com/dstat-real/dstat/issues/156 For anyone who (like me) hadn’t come across this before, it might be interesting to read.
- a0-prw 6y agoIf you're using a de, the bug is in you
- captainmuon 6y agoI don't know, I would not expect any Linux lock screen to be secure secure. More like a padlock to keep honest people honest. If somebody is "good with computers" the'll probably be able to break it. There has been discussion of actually locking the PC when the lock screen is enabled. When you use full disc encryption, it would evict the key from memory when the lock screen goes up. Then, with your password it will unlock the disc and the screen. For this, you'd need to move the login manager to the unencrypted partition and tie the user accounts to the hard disc encryption - I think Windows' BitLocker already does that. In the Linux world, you encrypt the disc before much of the OS loads (from a framebuffer or command line prompt).
- Macha 6y ago> I think Windows' BitLocker already does that. And one day later, it appears the answer is apparently not: https://secret.club/2021/01/15/bitlocker-bypass.html https://secret.club/2021/01/15/bitlocker-bypass.html
- raverbashing 6y agoSo, the way I see it is: if XSS has to be uncrasheable, sandbox it. Wrap it in something that's actually uncrasheable, and that will reload it unless XSS exits with code 0 or something Or have a syscall to "freeze" the user (this is why Windows required Ctrl-Alt-Del to login - so that the login input was gatekept), but yeah, X11 is a mess
- Liskni_si 6y ago> that will reload it unless XSS exits with code 0 or something Sort of what https://github.com/google/xsecurelock https://github.com/google/xsecurelock recommends doing. Also, xsecurelock doesn't run the input and PAM auth in the same process as the lock, making input bugs (https://news.ycombinator.com/item?id=21224179 https://news.ycombinator.com/item?id=21224179) harmless as well.
- lrossi 6y agohttps://tools.suckless.org/slock/ https://tools.suckless.org/slock/ Orders of magnitude smaller than xscreensaver. You can easily read the code and understand what it does.
- merlinscholz 6y agoSadly, this does not help people who just want to replace their Windows machines with Linux, or even more professional Linux users, who haven't even heard of this bug. After all, most people stick to the defaults. Also, the suckless community os one of the more toxic ones out there...
- mechEpleb 6y agoIf you just want to use their software, the community doesn't matter at all.