Originally posted by ssokolow
View Post
The point2 by Arcan developers is kind of on the right track with "If you try to force this on me, I'll implement WM-level cropping and a "hide/show" toggle button to get my SSD back."
Except this how SSD should be implemented if you want SSD done securely and be able to deal applications that have customised CSD decorations. So this should not be force to this should be how SSD is implemented.
Please note if a WM doesn't support undecorate flag applications under X11 using the right parts of the X11 protocol can render window by the X11 server without the windows manager knowing about it so CSD again.
It may seam horrible to make CSD the default but this requires those wanting to SSD to really consider the problem of how todo it properly with all the required functionality. Existing implementations of SSD on Windows X11 and Mac OS are all broken from a security point of view because you cannot tell what is SSD and what is CSD this is very important.
There is another side to CSD you miss that relates to data secruity. You do want applications at time to be able to resist the kill button on windows boarder. Think about it WM/compositor sees that you have sent kill to application and it decides its waiting long enough and kills it this may be too early. There is more than one right choice how long should you wait for a kill to process. So some applications having SSD for timed kill and CSD for as long as application takes todo the kill could be a great feature.
I will admit doing SSD in a secure way with proper support for applications that have to be CSD so they will not look absolutely horrible will have extra overhead.
SSD done for security should have supported cropping always.
CSD default of Wayland I don't see as wrong. SSD presumed to be there has resulted in Windows Managers not having the functionality to deal with CSD windows in either a secure way or a tidy way.
Comment