SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to get vlock to work. I use that laptop at work alot... at an ISP... around a bunch of people that know linux. So needless to say just using the lock in KDE isn't going to stop them from going to the shell connections. In mandrake, it had vlock already compiled and I just had to install the package and I was good to go. Here, I think the shadow passwords is what's messing me up. I found a precompiled version, but for an old distro at http://homepages.paradise.net.nz/~ca.../packages.html I tried to run that and it said it couldn't do it for mine, probably because it was trying to read the regular password and not the shadow file. So I tried to compile it on my own. Found the distro at http://linux.maruhn.com/sec/vlock.html (went for one of the .tar.gz files) and then tried to compile it and it couldn't find the crypt() function, again because I am using shadow files instead. I also had to disable PAM options in it. What is PAM used for? Has anyone ever gotten it compiled and can just link to it or say how you did it? thanks.
From my understanding PAM still isn't part
of Slackware, PAM is the "pluggable authentication
module" that would allow you to for instance authen-
ticate against a user-database in PostgreSQL, or
OpenLDAP ...
I can't say anything about 9.1, but it compiles
fine in 8.1, with no modifications (and I use the
shadow-password suite, too) ...
ok, here's the entire session from me trying to compile it (sorry for it being a little long). also, that time I edited the make file, I removed the PAM references. I can post the makefile here too if that would help.
Code:
root@oriana /tmp$ wget --passive-ftp ftp://ftp.nnov.net/pub/software/linu...ock-1.3.tar.gz
--17:33:17-- ftp://ftp.nnov.net/pub/software/linu...ock-1.3.tar.gz
=> `vlock-1.3.tar.gz'
Resolving ftp.nnov.net... done.
Connecting to ftp.nnov.net[81.18.128.209]:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD /pub/software/linux/console ... done.
==> PASV ... done. ==> RETR vlock-1.3.tar.gz ... done.
Length: 17,188 (unauthoritative)
100%[====================================>] 17,188 9.66K/s ETA 00:00
17:33:22 (9.66 KB/s) - `vlock-1.3.tar.gz' saved [17188]
root@oriana /tmp$ ls
kde-todd ksocket-todd mcop-todd vlock-1.3.tar.gz xmms_todd.0
root@oriana /tmp$ tar xvzf vlock-1.3.tar.gz
vlock-1.3/
vlock-1.3/Makefile
vlock-1.3/COPYING
vlock-1.3/signals.c
vlock-1.3/README
vlock-1.3/help.c
vlock-1.3/input.c
vlock-1.3/terminal.c
vlock-1.3/version.h
vlock-1.3/vlock.1
vlock-1.3/vlock.c
vlock-1.3/vlock.h
vlock-1.3/vlock.lsm
vlock-1.3/vlock.pamd
vlock-1.3/vlock.spec
root@oriana /tmp$ make
make: *** No targets specified and no makefile found. Stop.
root@oriana /tmp$ cd vlock-1.3
root@oriana /tmp/vlock-1.3$ make
gcc -O2 -DUSE_PAM -c -o vlock.o vlock.c
gcc -O2 -DUSE_PAM -c -o signals.o signals.c
gcc -O2 -DUSE_PAM -c -o help.o help.c
gcc -O2 -DUSE_PAM -c -o terminal.o terminal.c
gcc -O2 -DUSE_PAM -c -o input.o input.c
input.c:63:31: security/pam_appl.h: No such file or directory
input.c:64:31: security/pam_misc.h: No such file or directory
input.c:66: variable `PAM_conversation' has initializer but incomplete type
input.c:67: `misc_conv' undeclared here (not in a function)
input.c:67: warning: excess elements in struct initializer
input.c:67: warning: (near initialization for `PAM_conversation')
input.c:69: warning: excess elements in struct initializer
input.c:69: warning: (near initialization for `PAM_conversation')
input.c: In function `correct_password':
input.c:90: `pam_handle_t' undeclared (first use in this function)
input.c:90: (Each undeclared identifier is reported only once
input.c:90: for each function it appears in.)
input.c:90: `pamh' undeclared (first use in this function)
input.c:102: `PAM_SUCCESS' undeclared (first use in this function)
input.c:104: `PAM_USER_PROMPT' undeclared (first use in this function)
input.c:117: `PAM_USER' undeclared (first use in this function)
/usr/include/bits/sigset.h: At top level:
input.c:66: storage size of `PAM_conversation' isn't known
make: *** [input.o] Error 1
root@oriana /tmp/vlock-1.3$ vi Makefile
root@oriana /tmp/vlock-1.3$ make
gcc -O2 -c -o input.o input.c
gcc vlock.o signals.o help.o terminal.o input.o -o vlock
input.o(.text+0x28): In function `correct_password':
: undefined reference to `crypt'
input.o(.text+0x7a): In function `correct_password':
: undefined reference to `crypt'
collect2: ld returned 1 exit status
make: *** [vlock] Error 1
root@oriana /tmp/vlock-1.3$
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.