Hi everyone,
Just a quick word to remind you that the X.Org Foundation got accepted
to the Google Summer of Code 2018!
As a potential mentor, if you have a project falling under the
foundation's (large) umbrella that you would like to kick start or get
help finishing, please add it to the list on
inquiries/questions, please send them to Stéphane Marchesin (please also
CC: board at foundation.x.org).
Martin Peres
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
On 12/05/17 02:46, Manasi Navare wrote:
> Hi Daniel,
>
> Is Call for Papers opened yet for XDC? When do they usually start accepting
> proposals?
Hey Manasi,
Our call for paper is usually sent around June with a deadline for
mid-August. Here is the call for paper from last year, we do expect it
On 03/08/16 12:36, Peter Hutterer wrote:
This timeout is there to switch to scrolling when the fingers rest on the
touchpad unmoving and thus avoids the initial scroll threshold for slow
scrolls.
Since the only other gestures we support are swipe (usually a fast movement)
and pinch-and-rotate (a
On 13/05/16 01:56, Martin Peres wrote:
Hello,
I have the pleasure to announce that the X.org Developer Conference 2016
will be held in Helsinki from September 21 to September 23. The venue is
located at Haaga-Helia university[0], next to the Pasila station.
The official page for the event is
On 13/06/16 12:32, Martin Peres wrote:
This discussion has been going on for years (not this thread, the general
discussion).
Pekka made me realize on IRC that I was not specific enough
about what I mean here.
By discussion here, I am talking about sharing buffers
across blocks/drivers
On 21/03/16 18:28, Miguel Angel Vico wrote:
Hi all,
First of all, I'd like to introduce myself to the Wayland community: My
name is Miguel A. Vico, and I've been working as a Software Engineer
for NVIDIA for some time now, more specifically, in the Linux drivers
team. Although I've never spoken
if you are
attending please add your name as early as possible.
I am looking forward to seeing you there, if you have any
inquiries/questions, please send them to me (please also CC: board at
foundation.x.org).
Martin Peres
[0]
https://www.google.fi/maps/place/Ratapihantie+13,+0052
On 30/03/16 09:33, Jasper St. Pierre wrote:
I really hope that distributions don't see security policies as a
differentiator. This is how we got SELinux vs. AppArmor and real-world
apps having to ship both kinds of policies (or Fedora flat out
ignoring any idea of third-parties and such and inclu
On 30/03/16 01:12, Olav Vitters wrote:
On Mon, Mar 28, 2016 at 10:50:23PM +0300, Martin Peres wrote:
We thus wanted to let distros take care of most of the policies (which
does not amount to much and will likely come with the application
anyway). However, some distros or devices come with a
On 28/03/16 23:47, Drew DeVault wrote:
On 2016-03-28 10:50 PM, Martin Peres wrote:
Client->Server: What features do you support?
Server->Client: These privledged features are available.
Client->Server: I want this feature (nonblocking)
[compositor prompts user to agree]
Server->Cl
On 28/03/16 16:04, Drew DeVault wrote:
On 2016-03-28 9:08 AM, Giulio Camuffo wrote:
On this, see
https://lists.freedesktop.org/archives/wayland-devel/2015-November/025734.html
I have not been able to continue on that, but if you want to feel free
to grab that proposal.
I looked through this p
On 28/03/16 16:03, Drew DeVault wrote:
On 2016-03-27 10:21 PM, Jasper St. Pierre wrote:
I would rather the effort be spent making secure interfaces, exactly
as you've described.
Agreed. I think it should be pretty straightforward:
Client->Server: What features do you support?
Server->Client: T
On 28/03/16 02:41, Jasper St. Pierre wrote:
You're probably referring to my response when you say "GNOME does not
care about cross-platform apps doing privileged operations". My
response wasn't meant to be speaking on behalf of GNOME. These are my
opinions and mine alone.
I must have mis-rememb
On 27/03/16 23:34, Drew DeVault wrote:
Greetings! I am the maintainer of the Sway Wayland compositor.
http://swaywm.org
It's almost the Year of Wayland on the Desktop(tm), and I have
reached out to each of the projects this message is addressed to (GNOME,
Kwin, and wayland-devel) to collaborate
Hello everyone,
We are 1.5 months away from XDC and 20 days away from the proposals
deadline[1]!
If you did not manage to secure funding from your company but still
think you could benefit the community by giving a talk, we encourage you
to send an email to the board of X.Org with your talk
wever
would still advice you to show your interest by providing patches or
participating to our discussions.
Finally, I would like to thank Google again this year for giving us the
opportunity to get new blood to the projects under the X.Org
Foundation's umbrella!
Martin Peres, on beh
Le 02/05/2014 00:52, Martin Peres a écrit :
Hello,
I have the pleasure to announce that the X.org Developer Conference 2014
will
be held in Bordeaux, France from October 8th to October 10th. The venue is
located in the campus of the University of Bordeaux 1, in the computer
science
research lab
possible and do so no later
than September 5th!
Thanks,
Martin Peres - On behalf of the board of directors
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Le 04/07/2014 09:58, Pekka Paalanen a écrit :
On Thu, 3 Jul 2014 22:38:34 +0200
Fabrice Rey wrote:
Hi all,
This topic came up in my previous one about window placement, and I'd like
to go further.
So currently there is no such thing as Global shortkeys and keyboard focus,
Have you tried sear
st to
make badges and plan for the catering.
I am looking forward to seeing you there, if you have any
inquiries/questions,
please send them to me (please also CC: bo...@foundation.x.org).
Martin Peres
___
wayland-devel mailing list
way
On 27/02/2014 18:01, Jasper St. Pierre wrote:
On Wed, Feb 26, 2014 at 10:02 PM, Sebastian Wick
mailto:sebast...@sebastianwick.net>> wrote:
Hey Jasper,
maybe I didn't understand what you're saying but why can't you use
the application authorization mechanism you're talking about in
Le 19/02/2014 17:11, Martin Peres a écrit :
Wayland Security Modules
As seen earlier, granting access to a restricted interface or not
depends on the context of the client (how it was launched, previous
actions). The expected behaviour should be defined by a security policy.
As no
find a mentor yourself. You can also have a look at the summer of code
ideas wiki page[1] for interesting projects.
Looking forward to seeing which projects will happen for this 2014 edition!
Martin Peres
[1] http://www.x.org/wiki/SummerOfCodeIdeas/
[2] https://www.google-melange.com/gsoc/homepage
Le 20/02/2014 21:26, Thiago Macieira a écrit :
Em qui 20 fev 2014, às 19:56:08, Martin Peres escreveu:
Le 20/02/2014 18:42, Thiago Macieira a écrit :
Unless you meant that the WAYLAND_SOCKET variable can contain a file
descriptor number. Is that the case? In that case, how should the
Le 20/02/2014 20:43, Sebastian Wick a écrit :
Am 2014-02-20 20:02, schrieb Martin Peres:
Le 20/02/2014 13:04, Pekka Paalanen a écrit :
snip
It can be done, but with a little more effort than implied here.
Binding to an interace means wl_registry.bind request, and failing that
is always a
Le 20/02/2014 13:04, Pekka Paalanen a écrit :
On Wed, 19 Feb 2014 17:11:03 +0100
Martin Peres wrote:
Hi Guys,
Following to the giant and impossible to read "Authorized clients"
thread, I said I would take the time and write everything we talked
about down, for convenience and to ch
Le 20/02/2014 18:42, Thiago Macieira a écrit :
Unless you meant that the WAYLAND_SOCKET variable can contain a file descriptor
number. Is that the case? In that case, how should the privileged process
clear the environment to allow child processes to be launched?
Yes, it takes an FD as a paramete
hown interest in this and
I'm sure his experience can benefit all of us.
Hope something close to this proposal will be satisfactory to everyone
and work can begin in this direction!
Cheers,
Martin Peres
[1]
http://mupuf.org/blog/2014/02/19/wayland-com
Re-send to include the wayland and mesa mailing lists.
Sorry for the noise
Original Message
Subject:[GSoC2014] Call for projects ideas and mentors
Date: Thu, 06 Feb 2014 01:03:05 +0100
From: Martin Peres
To: dri-de...@lists.freedesktop.org ,
xorg-de
Le 09/01/2014 22:14, Martin Peres a écrit :
Le 09/01/2014 21:47, Maarten Baert a écrit :
On 09/01/14 10:00, Pekka Paalanen wrote:
Those are some reasons why screen recording (video) is easier to do as
a compositor plugin, like it is currently in Weston. A separate client
would need a non
, Martin Peres, Peter Hutterer and Stuart Kreitman.
They will continue to serve until their term ends in 2015. Current
directors whose term expires in 2014 are Matthias Hopf, Keith Packard,
Matt Dew, and Alex Deucher.
A director is expected to participate in the bi-weekly IRC meeting to
discuss
Le 10/01/2014 19:39, Jasper St. Pierre a écrit :
On Fri, Jan 10, 2014 at 12:13 PM, Martin Peres <mailto:martin.pe...@free.fr>> wrote:
Le 10/01/2014 16:44, Maarten Baert a écrit :
On 10/01/14 14:56, Martin Peres wrote:
Please provide a detailed explanation
Le 10/01/2014 19:37, Maarten Baert a écrit :
On 10/01/14 18:13, Martin Peres wrote:
And who would manage the sandboxes? Systemd won't be able to because
it is user applications.
I don't know how this will be done in the future, I can't predict that.
I suppose there will be some
Le 10/01/2014 16:44, Maarten Baert a écrit :
On 10/01/14 14:56, Martin Peres wrote:
Please provide a detailed explanation for that and tell me how likely
it is to ever end up upstream.
If by 'upstream' you mean the kernel: I don't think anything new is
needed, actually. Cr
Le 10/01/2014 04:32, Jasper St. Pierre a écrit :
On Thu, Jan 9, 2014 at 7:05 PM, Martin Peres <mailto:martin.pe...@free.fr>> wrote:
On 09/01/2014 23:57, Maarten Baert wrote:
On 09/01/14 21:54, Martin Peres wrote:
The worse thing that can happen is an ap
Le 10/01/2014 03:27, Maarten Baert a écrit :
On 10/01/14 01:05, Martin Peres wrote:
Let me help:
- The attacker has installed a Firefox plugin that sends him a copy
of all forms that you fill out.
- The attacker has messed with your PATH and has installed an
infected Firefox binary in a
Le 10/01/2014 02:37, Sebastian Wick a écrit :
Am 2014-01-10 01:05, schrieb Martin Peres:
Hey, don't twist his question and my answer ;) The question was IF our
protocol is wrong. Remember, we aren't addressing the security of
desktop here. We are looking for a way to provide
requirements coming from
the compositor ;).
Martin Peres wrote:
The video capture API concerns me more.
I realize that many people will never use it, so I think it's okay to
have it disabled by default and require that the user explicitly
enables it (once!). But just because something /can/ be a
On 09/01/2014 22:16, Jasper St. Pierre wrote:
On Thu, Jan 9, 2014 at 3:54 PM, Martin Peres <mailto:martin.pe...@free.fr>> wrote:
Le 09/01/2014 20:36, Jasper St. Pierre a écrit :
Security is based on trust. If you trust nothing, the computer
won't do very muc
On 09/01/2014 23:57, Maarten Baert wrote:
On 09/01/14 21:54, Martin Peres wrote:
The worse thing that can happen is an application running with the
user's uid grabbing and sending periodical screenshots to a distant
server running OCR and waiting for you to enter your bank detai
Le 09/01/2014 21:47, Maarten Baert a écrit :
On 09/01/14 10:00, Pekka Paalanen wrote:
Those are some reasons why screen recording (video) is easier to do as
a compositor plugin, like it is currently in Weston. A separate client
would need a non-trivial amount of new Wayland protocol to work well
Le 09/01/2014 20:36, Jasper St. Pierre a écrit :
Security is based on trust. If you trust nothing, the computer won't
do very much for you. You can't even trust it to compute correctly.
Security is based on access control. Every program that exposes a
service should think about how can it be a
Le 09/01/2014 20:14, Bill Spitzak a écrit :
Pekka Paalanen wrote:
Right... so that'd be a framerate hint, which the compositor only uses
if it needs to do a significant amount of work for each sent frame. We
probably want to keep most of the rate control still in the encoding
program, so it can
Le 09/01/2014 20:25, Bill Spitzak a écrit :
Martin Peres wrote:
We don't need to trust the client much if we limit the number of
screenshots to 1. This way, the worse thing that could happen for
your privacy would be if your cat sits on the keyboard and presses
"print screen&quo
Le 09/01/2014 14:41, Pekka Paalanen a écrit :
On Thu, 09 Jan 2014 13:05:28 +0100
Martin Peres wrote:
There is a way to limit the memory consumption of apps that don't
consume buffers. We could have a small ring buffer of wl_buffer or
dma-buf (if we want 0 copy) on the compositor side.
is is indeed something that needs to be discussed independently
of any security concern.
On Wed, 8 Jan 2014 23:30:29 +0100
Maarten Baert wrote:
On 08/01/14 13:52, Martin Peres wrote:
I think the screenshot API and the video recording one should be
separate.
Ideally that's true, but it cre
Le 08/01/2014 21:20, Sebastian Wick a écrit :
Am 2014-01-08 19:53, schrieb Martin Peres:
Le 08/01/2014 17:20, Sebastian Wick a écrit :
Am 2014-01-07 15:07, schrieb Martin Peres:
Those are extremely rare cases. Users wanting to do that should agree
they give up
confidentiality and should thus
Le 08/01/2014 20:20, Jasper St. Pierre a écrit :
If the user installed an app that takes screenshots of the screen
periodically and dumps them to a disk, I'd imagine that's
functionality he wanted. Why would we prompt him?
What if it is installed by default? And just because I sometimes want t
Le 08/01/2014 19:47, Jasper St. Pierre a écrit :
Prompting the user "are you *sure* you really meant to take a
screenshot? Yes/No" when he presses Print Screen is just a way to piss
her off.
Please don't mix everything and read carefully what I said.
Pressing "Print screen" IS the event that p
Le 08/01/2014 17:20, Sebastian Wick a écrit :
Am 2014-01-07 15:07, schrieb Martin Peres:
Those are extremely rare cases. Users wanting to do that should agree
they give up
confidentiality and should thus be administrators in order to tell the
compositor that.
Why should those people have
Le 08/01/2014 15:04, Sebastian Wick a écrit :
Am 2014-01-08 13:02, schrieb Martin Peres:
On 07/01/2014 20:26, Jasper St. Pierre wrote:
Would it be ok for you if the compositor asked the user to agree
for the program to
do the operation? If so, we can guarantee that this is really
On 07/01/2014 20:43, Pekka Paalanen wrote:
On Tue, 7 Jan 2014 14:26:36 -0500
"Jasper St. Pierre" wrote:
On Tue, Jan 7, 2014 at 9:07 AM, Martin Peres
wrote:
Would it be ok for you if the compositor asked the user to
agree for the program to
do the operation? If so, we can guar
On 07/01/2014 20:26, Jasper St. Pierre wrote:
Would it be ok for you if the compositor asked the user to agree
for the program to
do the operation? If so, we can guarantee that this is really the
user's intent and
allow the application. We can also add a security warning with
On 07/01/2014 20:53, Daniel Stone wrote:
Hi,
On 7 January 2014 19:22, Maarten Baert wrote:
@Martin Peres: Your ideas are nice in theory, but as Sebastian Wick already
said, it is just not practical.
If you want a specific example, I have one:
https://github.com/MaartenBaert/ssr
The sole
Le 07/01/2014 01:45, Sebastian Wick a écrit :
Am 2014-01-06 19:33, schrieb Martin Peres:
Le 06/01/2014 19:10, Sebastian Wick a écrit :
Am 2014-01-06 16:05, schrieb Martin Peres:
As I said before, I think trusting applications is taking the problem
the wrong way.
What we want is that a
Le 06/01/2014 19:10, Sebastian Wick a écrit :
Am 2014-01-06 16:05, schrieb Martin Peres:
As I said before, I think trusting applications is taking the problem
the wrong way.
What we want is that a screenshot can only happen when the *user*
wants it.
This is why I think it is the desktop
Le 04/01/2014 11:01, Martin Graesslin a écrit :
On Tuesday 31 December 2013 05:02:30 Sebastian Wick wrote:
I'm currently working on a system which allows specific clients to use
restricted interfaces [1]. This is needed for applications like
screenhooters,
desktop recorders outside of the compos
On 15/12/2013 01:09, Sebastian Wick wrote:
Am 2013-12-13 16:12, schrieb Martin Peres:
What prevents other applications from modifying this setting to true
if they want to
spy on applications?
Nothing. But then again if you can write to the ini file you can make
the compositor load any code
Le 13/12/2013 18:57, Maarten Baert a écrit :
On 13/12/13 16:01, Martin Peres wrote:
I may be wrong, but other unix users shouldn't be able to
communicate with another user's compositor unless this
user specifically allowed that by adding him to his/her group.
Okay, then that'
Le 04/12/2013 17:38, Sebastian Wick a écrit :
diff --git a/weston.ini.in b/weston.ini.in
index 5181a9e..bc32567 100644
--- a/weston.ini.in
+++ b/weston.ini.in
@@ -65,3 +65,6 @@ path=@libexecdir@/weston-keyboard
#constant_accel_factor = 50
#min_accel_factor = 0.16
#max_accel_factor = 1.0
+
+
s and those (or the
compositor) should at least make it obvious to the user that
screenshots are being taken.
It doesn't mean that I disagree that there should be a good screenshot
interface for compositors, I actually think you are fully right on this!
Martin Peres
Le 20/09/2011 12:32, Luc Verhaegen a écrit :
So far, only Martin Peres has stepped up and stated "yes! I will be
there!", and he will be happy to give FOSDEM visitors a talk about
Nouveau.
Yep, count me in. I'm really looking forward to it!
Living in France and never attend
63 matches
Mail list logo
