From: Gerd Hoffmann <kraxel@redhat.com>
To: Michal Privoznik <mprivozn@redhat.com>
Cc: qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3] SPICE/VNC: Allow ticketing on the fly
Date: Wed, 18 Feb 2015 09:29:04 +0100 [thread overview]
Message-ID: <1424248144.6014.50.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <cover.1424190993.git.mprivozn@redhat.com>
On Di, 2015-02-17 at 17:40 +0100, Michal Privoznik wrote:
> Currently, if the ticketing (password) is not set at the command
> line, there's no way how to set it afterwards. Or vice versa -
> disable previously set password. I think it's worth allowing
> users to do that. The use case may be a teacher, who wants to
> share a graphical session with students, but has to set up the
> environment firstly. So he starts with a password, and then
> remove it and let students in.
No. Changing auth scheme as side effect of setting the password is
not going to happen. It's calling for trouble security-wise.
If anything, then we might add an explicit set-authscheme, although I
suspect for your use case it would be more useful to somehow enforce
view-only access for the students.
cheers,
Gerd
prev parent reply other threads:[~2015-02-18 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 16:40 [Qemu-devel] [PATCH 0/3] SPICE/VNC: Allow ticketing on the fly Michal Privoznik
2015-02-17 16:40 ` [Qemu-devel] [PATCH 1/3] qapi-schema: Make @password in set_password optional Michal Privoznik
2015-02-17 16:53 ` Daniel P. Berrange
2015-02-17 17:05 ` Eric Blake
2015-02-17 16:40 ` [Qemu-devel] [PATCH 2/3] spice: Implement set_password without password Michal Privoznik
2015-02-17 16:40 ` [Qemu-devel] [PATCH 3/3] vnc: " Michal Privoznik
2015-02-18 8:29 ` Gerd Hoffmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1424248144.6014.50.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=mprivozn@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).