10 ms·
Wayland in Gnome: two progress reports
- darklajid 12y agoThere is also ongoing work to figure out how best to support taking screenshots of the whole desktop. Users expect the feature, but it has major security implications. If an application can take a screenshot unattended, it can also use that capability to record username/password combinations and other sensitive data. The straightforward solution is to force screenshot capture to require a user to verify the action; that would at least allow the user to detect if an unauthorized screenshot attempt is made. I know how this will come across, but .. sounds like UAC?
- aroman 12y agoAnd that is perfectly fine by me. There's a very limited subset of features which would require this kind of explicit authorization.
- adestefan 12y agoThere was never anything wrong with the idea of UAC; the problem was the implementation. When the feature was first introduced so many Windows programs did things that caused UAC pop-ups that it because nothing more than an annoying click-through that no one paid attention to. It became nothing more than a default "okay."
- vacri 12y agoThe problem wasn't the elevation request itself, it was the amount of requests for a single [user-perceived] action. My record was 5, but a friend managed to get 7 requests in early Win Vista... I wish I could remember what for.
- dethstar 12y agoyeah, something like that. I guess it'd be cool if you could just whitelist applications to do stuff, and have others pop out when requiring the permission.
- mercurial 12y agoSounds like a security hole: non-whitelisted malicious app launches whitelisted app as an external process, and then mayhem ensues.
- jhasse 12y agoUser permission should be required when launching external processes.
- wtallis 12y agoAnd whitelisted processes don't have to take input from anything other than the user himself; a command-line screenshot tool that can be run by any program and doesn't ask for interactive confirmation through a trusted channel (ie. keyboard events directed into its own window by the compositor itself) would be a pretty stupid thing to whitelist unless you've got proper sandboxing for any untrusted apps.
- itry 12y agoAn application can do all kinds of shit, can't it? It could probably replace your Browsers icon with an icon that starts a custom version of your Browser which uploads everything you type to some server.
- scrollaway 12y agoWhich is why we¹ are working on sandboxed apps. https://news.ycombinator.com/item?id=8219309 https://news.ycombinator.com/item?id=8219309 ¹I say "we" as in DE developers, I'm not a GNOME dev.
- e12e 12y agoI don't know... we've generally used suid binaries for this in the past? I suppose the display server will run as root, so the sane approach is to add a screenshot api, possibly writing the screenshot to a file/folder/socket with special permissions? ("special" because the gist here seems to be a wish to limit capabilities more finely than traditional unix user/group/others -- after all the user has access to the whole desktop (say with a digital camera) -- so the goal here is apparently to limit which applications can access other applications. At any rate, root should be able to read all process' memory, so taking a screenshot shouldn't be a problem... (I'm not saying take a screenshot by reading video memory, just that the level of access is equivalent).
- catern 12y agoSure, but UAC doesn't have to be as badly designed and implemented as it was in Windows. Allan Day has some great plans for adding this to GNOME: http://blogs.gnome.org/aday/2014/07/23/sandboxed-applications-for-gnome-part-2/ http://blogs.gnome.org/aday/2014/07/23/sandboxed-application...
- whoopdedo 12y agoCould another approach be to allow applications to flag a graphical element as secure and it will be excluded from any attempt by another process to read the screen? Don't even allow the superuser to take screenshots of passwords, credit cards, etc. They'll just show up as a black box.
- ansgri 12y agoDon't even talk about not allowing something to superuser. It could be nontrivial to enable though.
- hollerith 12y agoWriters (including the author of Wayland's home page) get enthusiastic about Gnome and KDE ports to Wayland, but what Wayland really needs is a port of either Firefox or Chrome/Chromium, and I've seen very little progress on that score.
- jmhain 12y agoReally? Chromium already has a fairly functional Wayland port [0] and Firefox just needs to upgrade to GTK 3, which is (admittedly optimistically) targeted for 32 [1]. [0] https://01.org/ozone-wayland/blogs/tiagovignatti/2013/chromium-browser-wayland-preview-release https://01.org/ozone-wayland/blogs/tiagovignatti/2013/chromi... [1] http://worldofgnome.org/optimistic-target-for-firefox-gtk3-is-firefox-32/ http://worldofgnome.org/optimistic-target-for-firefox-gtk3-i... EDIT: Now running the GTK 3 Firefox port in a GNOME Wayland session, and it's working great!
- kbrosnan 12y agoFirefox GTK3 builds are still pre-nightly. We won't uplift such major work, current nightly is 34 with the uplift to 35 on the day after labor day. I would say that 36 would be possible but obviously depends on the work load of Glandium and Emilio Pozuelo. If you want to test the builds the are available at ftp://ftp.mozilla.org/pub/firefox/tinderbox-builds/elm-linux64/ however there is no updater, so you would need to manually do that.
- jmhain 12y agoI admit I let my new-desktop-linux* evangelism get the better of me there, since I definitely knew that target was outdated. I should really put my money where my mouth is and try and help with the port. * There should really be a term for the new emerging desktop linux platform based around systemd and wayland.
- hollerith 12y ago>I should really put my money where my mouth is and try and help with the port. It's more fun to work together than to work by yourself. Maybe you and I should meet up and spend a day working together on the port. (Contact info in my profile.)
- jmhain 12y agoI'm typing this from a wayland session of the GNOME 3.14 beta (via Fedora 21 Branched). While there are still some serious bugs, I have to say I am very impressed. The synchronization problems and graphical glitches of X always made the Linux desktop feel second rate compared to Mac or Windows. With wayland, interactions with elements on the screen such as moving and resizing windows or dragging apps to the dash are perfectly in sync with the cursor. Not even Android has achieved this. In addition, GNOME 3.14 is looking outstanding. With the latest design refinements, I find the interface significantly more attractive than OS X (before or after redesign). It's not quite there yet, but if the community can deliver a system with fully functional wayland, portable sandboxed app containers, and a stable development target, the Linux desktop truly will stand a chance against the proprietary competitors.
- mixmastamyk 12y agoI've been using Linux for two decades and not experienced the graphical glitches you speak of. Moving and resizing windows? Nope. Some infuriating compiz bugs, sure.
- rayiner 12y agoYou didn't notice in two decades that moving and resizing windows in Linux was an ugly affair plagued by graphical artifacts? I wrote this almost a decade ago and as far as I can tell it's still true today unless you use Wayland: http://www.osnews.com/thread?93850 http://www.osnews.com/thread?93850. Obviously a lot of pieces (graphics drivers, etc) have fallen into place since then, but it seems like ditching X was a necessary step to getting a clean, artifact-free experience.
- based2 12y agohttps://github.com/walac/blender-wayland https://github.com/walac/blender-wayland
- e12e 12y agoSo, this is a "Wayland back-end for Blender". Does that mean it renders real-time to a window in wayland? I'd think what most would want is a front-end for Wayland? What am I missing?
- FreeFull 12y agoIt's a rendering backend for blender's frontend (The user interface is the same across Windows, Linux and OS X despite each of those using their own ways to draw things to the screen, after all).
- hyperion2010 12y agoLack of global keybindings would keep me off wayland for a long time. At this point I am completely dependent on my keybinds in fluxbox for doing everything from resizing windows to opening programs. If I can't specify real defaults that stupid programs cannot interfere with it will be useless.
- catern 12y agoNo, Wayland only makes it difficult for individual applications to define global keybindings - so, for example, a global Ctrl-Space to play/pause your music player would need some extra plumbing to be implemented. Your WM owns (well, is, in Wayland) the display server, so it can define whatever keybindings it wants.
- tinco 12y agoIt sounds like it's not Wayland making it difficult, but other systems making it way too easy. If I was a GUI application developer I would totally expect to have to interface with some WM API to register global key bindings. Being able to just listen to the keyboard even when the app is not in focus really does sound like a security problem waiting to happen.
- quotemstr 12y agoThe problem with putting everything in the now-unified compositor-windowmanager-desktop thing is that it creates a huge barrier to implementing desktop customizations. Instead of being able to swap out just the window manager, or just the dock, or just the keybindings, you have to either fork the standard implementation (and be constrained by its architecture) or implement all the interfaces expected of applications.
- wtallis 12y agoThat's not accurate. A wayland compositor can implement plugin support and delegate stuff to external processes; this is how weston works. You can swap out one shell for another, and if you want you can implement a shell that itself delegates out the dock, window decoration, etc. each to different processes. But the defaults will and should be that arbitrary apps cannot in any way snoop on or interfere with the user's interaction with other apps, so obviously any app that wants to do so will have to get authorization and use some interfaces that aren't part of the normal protocol for presenting an app to the user. You're not "being constrained by [the] architecture" of the standard implementation in any way that's not completely justified.
- kremlin 12y agooff-topic but genuine question: Is it not a bit ironic that this source of information about display technologies (among other things) uses tables for page layout?
- wmf 12y agoLWN is old school and it's all about the content.
- dredmorbius 12y agoSo does the site you're commenting about that from.
- renox 12y agoNot really: LWN is about Linux. Linux/Unix users care more about content than form (usually)..
- com2kid 12y agoThere seems to be a lot of limitations here. It is odd, sandboxing just the graphics stack. It isn't true sandboxing so all the benefits of sandboxing are not gained, but a lot of the disadvantages still come with it. It sounds like something as simple as a keyboard macro manager would not be doable, nor would the Windows utility AutoHotKey. I'd also hate to try and write UI test automation for Wayland apps. It seems like they've pretty much ruled that out all together. Heck what about services that do browser test renders? Would those be possible? And not allowing plug ins is just foolish. "I'm sorry, we dictate that you must divide your application up this way." Flash, for years, drove innovation on the web, billions of dollars of value were created by Flash, trying to say "That won't be allowed to happen again because I say so" is hubris of the worst sorts.
- wmf 12y agoIt is odd, sandboxing just the graphics stack. Since Wayland is a redesign of the graphics stack it looks like they decided to redesign it in a secure way rather than waiting for some system-wide security architecture to be designed. GNOME is working on full sandboxing: https://news.ycombinator.com/item?id=8219309 https://news.ycombinator.com/item?id=8219309 It sounds like something as simple as a keyboard macro manager would not be doable... That's doable in the compositor/window manager. I'd also hate to try and write UI test automation for Wayland apps. That's possible either through accessibility interfaces ( https://developer.gnome.org/accessibility-devel-guide/stable/gad-how-it-works.html.en https://developer.gnome.org/accessibility-devel-guide/stable... ) or the compositor/window manager. Note that many OS X "haxies" also use the accessibility API. Heck what about services that do browser test renders? That should be no problem using either a modified browser or modified compositor.
- stelonix 12y agoAutoHotKey-like behavior is already severely limited on X (can't send to non-active windows, same with XTEST). That is, if you want to use it for macros. For UI test automation it's fine I guess.
- audidude 12y agoui automation will have to be there, as accessibility toolkits require it (that's how atk works). it's just going to require an additional wayland interface.
- spain 12y agoAs interested as I am for Wayland, Gnome 3 is still Gnome 3.
- wirrbel 12y agoI have grown to really like Gnome 3.
- aruggirello 12y agoCan't wait to see it working in (or, under?) KDE...