On Wednesday, May 23, 2012 01:16:29 Claudio Freire wrote:
On Tue, May 22, 2012 at 9:48 AM, Andreas Jaeger
wrote: * Are there any use cases missing? * Is there any thing missing in the specific use cases?
From personal experience, handling of external storage[0] in multiuser (and I mean multiple concurrent sessions) desktops is very poorly handled.
It's probably more a bug than anything else, but I thought I'd mention since the wiki shows it as "OK" when it still could use some love.
What exactly is the problem? Please describe in more detail.
GPU for calculation, for another item, is a very tricky business. GPU threading is very coarse, especially on not-so-high-end hardware, so while ACL management and all that is possible, isolation between GPU-enabled users would not be so easy. User with access to the GPU would be able to deny use of the resource to other users simply by running misbehaving code without any extra privileges.
Exactly, GPU-enablement can only be for one user at a time.
It's also quite easy to leak out sensitive information (ie: even passwords) by inspecting uninitialized video memory, since drivers tend not to clear buffers on (de)allocation, so previous video content is easily visible in newly created buffers. This would be a serious security issue if *any* user were to be given access to the GPU in concurrency with any other user.
Network access, also, needs some consideration for VPNs, which are rather common both in single-user laptops and enterprise environments.
I consider that handled via NetworkManager for the single-user laptop, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org