Re: [PATCH 2/2] proto, server: Add internal server error message. (v2)

On 20 November 2018 8:02:50 pm NZDT, Christopher James Halse Rogers wrote: >Many languages such as C++ or Rust have an unwinding error-reporting >mechanism. Code in these languages can (and must!) wrap request >handling >callbacks in unwind guards to avoid undefined behaviour. > >As a consequence

Re: Upcoming release

On Friday, January 18, 2019 5:20:40 PM EST Derek Foreman wrote: > Hi all, > > It's been quite some time since our last weston release, and there's > been some discussion of getting the next one out in the January to March > timeframe (this would be the last release to have an autotools build, btw)

Re: BSDs and wl_client_get_credentials

On Mon, 21 Jan 2019 at 14:40:23 +0200, Pekka Paalanen wrote: > On Mon, 21 Jan 2019 11:35:12 + > Simon McVittie wrote: > > On Mon, 21 Jan 2019 at 12:40:11 +0200, Pekka Paalanen wrote: > > > Currently I have no clear opinion on what might be best. PID, UID and > > > GID are quite poor for author

Re: BSDs and wl_client_get_credentials

On Mon, 21 Jan 2019 11:52:46 + Simon Ser wrote: > On Monday, January 21, 2019 11:40 AM, Pekka Paalanen > wrote: > > On Sun, 20 Jan 2019 13:51:42 + > > Simon Ser wrote: > > > > > Hi, > > > > > > I wanted to start discussing about wl_client_get_credentials support in > > > various BSDs

Re: BSDs and wl_client_get_credentials

On Monday, January 21, 2019 1:40 PM, Pekka Paalanen wrote: > That is enlightening. It makes me wonder what people are using > PID/UID/GID for. Yeah. Maybe we should add some big warning signs "even if you think it's safe, it isn't, don't use this for security" in wl_client_get_credentials docs. _

Re: BSDs and wl_client_get_credentials

On Mon, 21 Jan 2019 11:35:12 + Simon McVittie wrote: > On Mon, 21 Jan 2019 at 12:40:11 +0200, Pekka Paalanen wrote: > > I don't think we can fix wl_client_get_credentials(), the semantics are > > very explicitly tied to the SO_PEERCRED behaviour. What I think we > > should do instead is to lo

Re: BSDs and wl_client_get_credentials

On Monday, January 21, 2019 12:35 PM, Simon McVittie wrote: > Note that deriving information from the pid is easy to defeat if you have > access to a mechanism like setuid or filesystem capabilities, which > escalates capabilities while preserving the pid. > See

Re: HDR support in Wayland/Weston

On Fri, 18 Jan 2019 09:05:53 +0530 "Sharma, Shashank" wrote: > On 1/17/2019 5:33 PM, Pekka Paalanen wrote: > > On Wed, 16 Jan 2019 09:25:06 +0530 > > "Sharma, Shashank" wrote: > > > >> On 1/14/2019 6:51 PM, Pekka Paalanen wrote: > >>> On Thu, 10 Jan 2019 20:32:18 +0530 > >>> "Sharma, Shashan

Re: HDR support in Wayland/Weston

On Fri, 18 Jan 2019 19:02:01 +1100 Graeme Gill wrote: > Pekka Paalanen wrote: > > Hi, > > > If a wl_surface straddles multiple outputs simultaneously, then > > wl_surface.enter/leave events indicate the surface being on all those > > outputs at the same time. The client is expected to take all

Re: BSDs and wl_client_get_credentials

On Monday, January 21, 2019 11:40 AM, Pekka Paalanen wrote: > On Sun, 20 Jan 2019 13:51:42 + > Simon Ser wrote: > > > Hi, > > > > I wanted to start discussing about wl_client_get_credentials support in > > various BSDs. wl_client_get_credentials uses getsockopt() with > > SO_PEERCRED, which

Re: BSDs and wl_client_get_credentials

On Mon, 21 Jan 2019 at 12:40:11 +0200, Pekka Paalanen wrote: > I don't think we can fix wl_client_get_credentials(), the semantics are > very explicitly tied to the SO_PEERCRED behaviour. What I think we > should do instead is to look into making a new API using > SCM_CREDENTIALS. D-Bus uses (and

Re: BSDs and wl_client_get_credentials

On Sun, 20 Jan 2019 13:51:42 + Simon Ser wrote: > Hi, > > I wanted to start discussing about wl_client_get_credentials support in > various BSDs. wl_client_get_credentials uses getsockopt() with > SO_PEERCRED, which isn't supported on BSD. On the other hand, using > SCM_CREDENTIALS by passin