From: Alessandro Sappia <a.sappia@ngi.it>
To: linux-kernel@vger.kernel.org
Subject: chvt issue
Date: Mon, 24 Jan 2005 01:34:56 +0100 [thread overview]
Message-ID: <41F442B0.80900@ngi.it> (raw)
HI all
I was reading vt driver
and I saw
/*
* To have permissions to do most of the vt ioctls, we either have
* to be the owner of the tty, or have CAP_SYS_TTY_CONFIG.
*/
perm = 0;
if (current->signal->tty == tty || capable(CAP_SYS_TTY_CONFIG))
perm = 1;
(lines 382-388 - drivers/char/vt_ioctl.c)
After reading the comment I thinked I can change vt
from one of my own to another one of mine.
so I opened vc/2 and vc/3 and a pts/0
$ w
01:26:45 up 1:33, 5 users, load average: 0,84, 0,66, 0,97
USER TTY LOGIN@ IDLE JCPU PCPU WHAT
alx vc/2 01:07 18:51 0.00s 0.00s -bash
alx vc/3 01:25 48.00s 0.00s 0.00s -bash
alx :0 23:55 ?xdm? 4:21 0.84s gnome-session
alx pts/0 01:22 0.00s 0.08s 0.00s w
I went to vc/3 and I did
$ tty
/dev/vc/3
$ chvt 2
as i expected I changed my tty to 2
after that I tryied to do the same from pts/0
and
$ tty
/dev/pts/0
$ chvt 2
chvt: VT_ACTIVATE: Operation not permitted
$
After that I went in vc/2
and I did
$ chvt 12
after that i was watching at my syslog writing messages...
I tryed the same from pts/0
and
$ chvt 12
Couldnt get a file descriptor referring to the console
So, there are some things I couldn't get about virtual terminal ioctls
and fd...
please note that use chvt having CAP_SYS_TTY_CONFIG (root) works fine.
Is it possible to change terminal from an unprivileged user ?
THanks in advance
for the time you'll spend answering me.
Alessandro
next reply other threads:[~2005-01-24 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 0:34 Alessandro Sappia [this message]
2005-01-24 8:14 ` chvt issue Andries Brouwer
2005-01-24 10:56 ` Toon van der Pas
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=41F442B0.80900@ngi.it \
--to=a.sappia@ngi.it \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.