<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Add an API for taking screenshots and recording screencasts"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98894#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Add an API for taking screenshots and recording screencasts"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98894">bug 98894</a>
from <span class="vcard"><a class="email" href="mailto:StV5303@bk.ru" title="Vladimir Stoiakin <StV5303@bk.ru>"> <span class="fn">Vladimir Stoiakin</span></a>
</span></b>
<pre>I am not a developer, so my suggestion can be naive.
What about to use simple password authentication for apps?
For example, some user wants to record a screencast. He sends a request to a
compositor with a public API. The compositor allows to do it (if configured
so), generates a one-time secret password, and draws it in the final screen
buffer. The user reads the password on the screen, and enters it in the program
which is going to do the job. With this password the program can start
recording.
In this scenario the user knows exactly which program will get access to the
screen (he relies on the shell which starts user programs), and the process of
recording can be fully controlled by the compositor.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>