11-29-2009
Urgent Help...Pseudo-Device provides a Backdoor Entry to root.
Can Anybody help to create a pseudo-device and write a device driver for it. The pseudo-device provides a “backdoor” for gaining root access for a particular user. Instead of compiling the device driver into the kernel. Modules are object binaries that can be dynamically loaded into the kernel.
This pseudo-device gives root privileges to the task whose pid is written to the device. When the module is installed, the uid of the user who are allowed to use this device can be passed as module parameters. Any other user, including root, that tries to use this device will get an “access denied” error. When the correct user accesses the device for executing operations, the device driver finds the task associated with the pid and grants that task root privileges.
Requesting help from Amazing Programmers in this forum
Last edited by pludi; 11-29-2009 at 06:00 AM..
Reason: removed email
10 More Discussions You Might Find Interesting
1. Solaris
Hi I have a system that gave me some messages on bootup that I was not used to seeing:
pseudo: pseudo-device: vol0
genunix: vol0 is /pseudo/vol@0
these came with these:
Feb 13 17:42:17 system1 eri: SUNW,eri0 : 100 Mbps full duplex link up
Feb 13 17:42:21 system1sendmail: My unqualified... (0 Replies)
Discussion started by: mndavies
0 Replies
2. BSD
Hello there. I installed NetBSD yesterday on an older system to try it out. Everytime I boot, I have to enter in the root device (disk) manually wd0 which then proceeds into asking to define the dump device: is the default then, the sbin/init My question is where am I supposed to... (1 Reply)
Discussion started by: septima.pars
1 Replies
3. Homework & Coursework Questions
Problem statement.
In this part of the assignment, delegates will create a pseudo-device and write a device driver for it. The pseudo-device provides a “backdoor” for gaining root access for a particular user. Instead of compiling the device driver into the kernel, delegate will create a module.... (1 Reply)
Discussion started by: nyjilgeorge1
1 Replies
4. Emergency UNIX and Linux Support
Dear All,
I was having powerpath 5.2 on SUN server with SVM connected to CLARIION box.Please find the following output :
root # powermt display dev=all
Pseudo name=emcpower3a
CLARiiON ID=CK200073400372
Logical device ID=60060160685D1E004DD97FB647BFDC11
state=alive; policy=CLAROpt;... (1 Reply)
Discussion started by: Reboot
1 Replies
5. UNIX for Advanced & Expert Users
Yestoday, in order to analysis the core dump information which is a result of my bugged device driver, I configurate and make the kernel according to "Documentation/kdump/kdump.txt" in linux source code and today, I reboot the system with "crashkernel=64M@16M". The system cannot boot now and... (0 Replies)
Discussion started by: liklstar
0 Replies
6. Cybersecurity
Tails (LiveCD) is crap, and I'm being nice here. Bloated, contains HAMRADIO and PACKET RADIO modules which no one in their right mind would use on a distro aimed at Tor use, I don't even believe 1% of Linux users use them, yet they're generated right there in the directories. Google about ham radio... (0 Replies)
Discussion started by: chipinmybrain
0 Replies
7. Solaris
sometimes I see this message in dmesg:
what does it mean?
thanks. (5 Replies)
Discussion started by: orange47
5 Replies
8. Red Hat
Hello,
In linux /etc/rc.d/rc.sysinit mounts root File System as RW during the booting phase.
So why we have entry of it in /etc/fstab?
Thanks,
Nitin (1 Reply)
Discussion started by: Nitin Pradhan
1 Replies
9. AIX
greetings, just ran across a fun situation we had overlooked.
We have a backdoor user, no special privileges, which we put on every server so that anyone in the shop can get in (passwd in vault) if they need to, even if they don't have a local account on that server. The point of course is to... (3 Replies)
Discussion started by: maraixadm
3 Replies
10. UNIX for Advanced & Expert Users
did a big mistake, changing root entry of /etc/passwd to
root:x:0:0:root:/root:/usr/bin/tmux split-window -v \; attach
as expected, now I can't login as root anymore. sudo ed /etc/passwd etc. doesn't work.
Any idea?
Use code tags to increase readability and follow the rules. (4 Replies)
Discussion started by: dodona
4 Replies
PTM(4) BSD Kernel Interfaces Manual PTM(4)
NAME
ptm -- pseudo-terminal multiplexor device
SYNOPSIS
pseudo-device pty [count]
DESCRIPTION
The ptm driver is the backend for the /dev/ptm device. It supports three ioctl(2)s. The first is TIOCPTMGET, which allocates a free pseudo-
terminal device, sets its user ID to the calling user, revoke(2)s it, and returns the opened file descriptors for both the master and the
slave pseudo-terminal device to the caller in a struct ptmget. This struct has the following content:
struct ptmget {
int cfd;
int sfd;
char cn[16];
char sn[16];
};
where cfd and sfd contain the master resp. slave device's file descriptor and cn and sn the corresponding paths in the file system.
The /dev/ptmx device supports two more ioctl(2)s, TIOCGRANTPT, which is used by grantpt(3), TIOCPTSNAME, which is used by ptsname(3).
The ptm device is included with the pseudo-device pty(4). It can be disabled by adding ``options NO_DEV_PTM'' to the kernel configuration.
FILES
/dev/ptm ptm access device
/dev/ptmx ptm cloning device, used to implement Unix98 ptys
SEE ALSO
grantpt(3), openpty(3), posix_openpt(3), ptsname(3), unlockpt(3), pty(4)
HISTORY
The /dev/ptm device appeared in OpenBSD 3.5 and was ported to NetBSD 3.0.
BSD
November 12, 2005 BSD