Fedora Hardware :: Sudo Does Not Work With Fingerprint (SU Still Do)
Jan 20, 2010
Since yesterday my sudo doesn't work with my fingerprintreader anymore. su and GDM still do. sudo just asks me for the password instead of asking for a finger-swipe. AFAIR I changed nothing, but I accidentally forwarded the USB-Port on which the scanner is connected to VMware. I disconnected it, but maybe there could be the problem.
Fedora 12 x64, Thinkpad T61 integrated Fingerreader.
How to get a built in fingerprint scanner to work with linux? the device was installed on my laptop when i initially ordered it, i have a dell studio 1735 (i think its 1735) and i would like to use it with my linux. by the way im running mandriva.
Does any one know about fingerprint in HP dv4 to work.
fprint is installed but didnot detect the reader.
Code: lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I'm running into an issue on my fedora installations getting sudo insults to work. I'm fairly new to the distro, but in other distros, I just had to add insults to the Defaults line within visudo. Then I could sudo -K to reset my sudo session and it worked.
Since I installed sudo from yum, I suppose it's possible that insult support is not built into the rpm. I'm sure others got it working and I was hoping not to have to manually compile sudo with insults support as I don't want to break yum for updates/upgrades. If that's the only option, I'm more than happy to go that route, just would like it as a last resort.
I am working on a project that requires fingerprint reader support. So, I installed the libfprint and libfprint-devel packages on my Fedora 14 system, to support my Authentec AES 2501 fingerprint reader. I know that my device is alright because it is working fine on the Windows 7 installed on the same system. In fedora, the fingerprint reader is recognized, when I run the fprintd-enroll command. The prompt to enroll the fingerprint is displayed on terminal. But, it just stands when I swipe my finger. I have tried everything but cannot resolve the issue. The output of usb-devices command shows "Driver=none" under fingerprint sensor usb device. But, I have the libfprint installed.
Are there any possible options to archive this w/ the 2.6.34 kernel? I know windows can do this w/ a button and BSD can drop packets when connected to closed ports...is IP personality usable in 2.6? Do I need work-arounds? any more options??Currently I've managed to @%#$ my OS fingerprints so results won't show as Linux.4/2.6...etc, but the problem is.. instead it's got the word "Redhat" in it (which is well... worse... because now.. if someone looks at my machine he/she'll know I am on either RHEL/Fedora )
I have a DigitalPersona U.are.U 4000 Fingerprint Reader. I can run fprintd-enroll, and the device turns on, but it does not recognise anything that touches it. 'yum install *fprint*'
A day ago I finally got around to upgrading the PackageKit installation that had been sitting for a week and a half, so I found a new upgrade for sudo available - the one that gives the sudoreplay command, I forget which version number it is exactly. When I try to use the sudo command I get this notice in my terminal:Code:Can't open /var/db/sudo/me/1: Permission deniedI didn't get it before. What do I have to do to make it open? I'm using SELinux in enforcing mode if that helps.
Digital Persona Fingerprint reader is not working on dell 1535. I am using fedora 13 64 bit edition. I have tried using lsusb |grep -i finger but nothing has come up. I have installed all the fprintd packages but still no luck.
I am new to fedora (been using debian based distro's for the longest time). With the new release I decided to give FC13 (The kde 64 bit spin) a try. I told it to wipe my entire hdd and encrypt the partitions. The partition manager made a few LVM partitions which I assume are encrypted.
The problem I am having is that if I attempt to use an application that would normally need root access to run, I am not prompted to enter my root password. Instead, I am required to logout and log back in as root. Is there a way to make it so that FC13 will prompt me to enter in my root password so I do not need to log in and out? Or is there something Different I should have done during the install process? Also, what is the terminal equivalent of "sudo" in fedora, or is it still sudo/KDEsudo
I also have not used SE Linux before. Do I need to manually enforce the permissions for my applications and generate my own profiles for it, or is that done automatically?
Code: bahie@bahie-laptop:~$ sudo apt-get install screenlets python-rsvg [sudo] password for bahie: Reading package lists... Done Building dependency tree Reading state information... Done python-rsvg is already the newest version.
I was attempting to install the fglrx driver on my new ubuntu insallation, following a guide I found from google. At one point it says I need to login as super user, so I tried and no matter how many times I try it just keeps saying authentication failed. I even tried typing in my password with 1 finger, multiple times, every single time, authentication failed. So I decided to try the sudo command with fdisk -l, worked flawlessly. Tried the su command again, authentication failed, I have no idea what in heck is causing this but it just won't stop happening.
When I use sudo, command does not auto-complete with 'tab'. Perhaps its some sort of security measure? I'd like to turn it off, because its just annoying. Older versions of debian didn't have such problem. Using debian_testing_amd64.
I want to install some software using sudo apt-get command,but it dosen't work.(my network works well) how to handle it? below is the output of terminal:
@ubuntu:~/Downloads$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 Reading package lists... Done Building dependency tree
I have ubuntu server 8.x which works Ok but the other day I changed the owner of some files "the directory /etc" from root me. Now a lot commands do not work like reboot and such. So I tried to put ownership back to root and I can't. I say I dont have proper privilege. Sudo also doesn't work. I conect to the server using ssh with putty. What could I do to fix the problem? Update to the new version? This server has been working really well for a few years. The reason I changed the owner of the directory to myself is so I could edit some config files from my windows machine using a FTP client like WinSCP.
I'm a totally new Linxu/Ubuntu user and terrified of command prompt/terminal. But I'm trying to get my Keebox W150nu to work with 11.04 and following Chili's suggestion on doing so, but ran into an early problem:
robert@lawsonbox:~$ ndiswrapper -1 The program 'ndiswrapper' is currently not installed. You can install it by typing: sudo apt-get install ndiswrapper-common robert@lawsonbox:~$ "sudo apt-get install ndiswrapper-common" [sudo] password for robert:
At that last line I am stumped. I can't input anything, no matter what key I press nothing is showing up there. If I knew the password I wouldn't be able to put it in! Do I hit an F key or what at this stage?
I can make aliases fine by editing the .bashrc file in my home directory, but the first thing I do when I open a terminal window is sudo su so I don't have to type sudo in front of every command. The problem is, I am then not able to use my aliases. How can I make aliases that work after I run the sudo su command?
I've set up a low cost box with Ubuntu Lucid Lynx at home behind a router, and managed to get remote access running. My goal is to be able to host a small website and work on it remotely, so I isntalled ftp (vsftpd). When I tried to edit the vsftpd.conf file in Vinagre from work, I could only open it read-only, no surprise. When I tried 'sudo gedit' or 'sudo gedit /etc/vsftpd.conf' from terminal in Vinagre, I received the prompt for the password to elevate privileges (again, expected); however, after I hit Enter, nothing happens. I've tried a bunch of different things, but I can't get it to work. I can stop & start my ftp service with 'sudo service vsftpd stop/start' and it seems to work fine.
I've setup the .ssh/authorized_keys and am able to login with the new "user" using the pub/private key ... I have also added "user" to the sudoers list ... the problem I have now is when I try to execute a sudo command, something simple like:
$ sudo cd /root
it will prompt me for my password, which I enter, but it doesn't work (I am using the private key password I set)Also, ive disabled the users password using
$ passwd -l user
I am trying to harden my system ... the ultimate goal is to use pub/private keys to do logins versus simple password authentication. I've figured out how to set all that up via the authorized_keys file.Additionally I will ultimately prevent server logins through the root account. But before I do that I need sudo to work for a second user (the user which I will be login into the system with all the time).
For this second user I want to prevent regular password logins and force only pub/private key logins, if I don't lock the user via" passwd -l user ... then if i dont use a key, i can still get into the server with a regular password.But more importantly I need to get sudo to work with a pub/private key setup with a user whos had his/her password disabled.
1) I've adjusted /etc/ssh/sshd_config and set PasswordAuthentication no This will prevent ssh password logins (be sure to have a working public/private key setup prior to doing this
2) I've adjusted the sudoers list visudo and added
root ALL=(ALL) ALL dimas ALL=(ALL) NOPASSWD: ALL
3) root is the only user account that will have a password, I am testing with two user accounts "dimas" and "sherry" which do not have a password set (passwords are blank, passwd -d user)
The above essentially prevents everyone from logging into the system with passwords (a public/private key must be setup). Additionally users in the sudoers list have admin abilities. They can also su to different accounts. So basically "dimas" can sudo su sherry, however "dimas can NOT do su sherry. Similarly any user NOT in the sudoers list can NOT do su user or sudo su user.
I had some bash scripts on Ubuntu 09.10 (mint version) that fail to work on Ubuntu 10.04. The line that fails is the following:
Code: # cat file_with_my-password.txt > sudo -S something cat: invalid option -- 'S' Try `cat --help' for more information. In my case "something" mounts some filesystems (that fail to load from fstab - bios "fake" raid 10), but I get the same error for any sudo command. It is the same script that used to work under 09.04 :-/
I'm having some trouble using sudo - it did work fine, but now when I try to use it, I have the following error:
I understand that I have to modify /etc/sudoers but need to have root access to do this. I am using a bootable USB (lucid) with persistent changes and am unable to login as root, because I don't know the default root password, and am unable to use sudo to change it.
The problem occurred after I had some corruption to the casper file system, so I booted into Windows, moved the casper-rw file to another location on my flashdrive, and used a 1GB backup filesystem to repair the corrupt one using fsck.
After booting up from the restored filesystem, sudo would no longer work.
Trying to install e4rat that was on LifeHacker on Friday and have zero idea what I am doing. I have the e4rat extracted to a directory in /usr/local/src The README says that there are dependencies including boost library components. I am fine installing the whole boost library but sudo apt-get install libboost* did not work.
[Code]...
I tried to bang around a little to try to learn something with this but can't get any further.
A fresh installation of ubuntu 9.10 stopped my DSL internet connection. sudo pppoeconf solved the problem of net, but NetworkManager applet in panel now not working. it says wired networks, device not managed.
I just installed openSUSE 11.2 KDE when I tried to enable fingerprint authentication yast didn't ask me to swipe my finger it was working properly on GNOME.