Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Help in setting up password without Interaction. Post 8148 by rwb1959 on Saturday 6th of October 2001 04:11:05 PM
Old 10-06-2001
Ahhh... this clarifies your first posting
considerably Smilie

The short answer... I don't know if that can be
done but if it could, it would seem like a
security hole. Since the passwd program should not
accept input from anything other than an actual
"tty" attached to stdin. Having said that, a C
program run as root can pretty much do anything.
You may consider writing your own C program
to do it or look around (maybe as part of a
root kit or somthing but I woun't recommend
those Smilie ) for some code fragments.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Can i enter password with out user interaction

Can any body help me to write a scripting program for entering a password at run time with out user interaction. (1 Reply)
Discussion started by: kumar_d
1 Replies

2. UNIX for Dummies Questions & Answers

Setting password restrictions for all users

I would like to change the password requirements for all our AIX 5.2 logins but am having trouble finding a place where I can set the rules for everyone at the same time. I know I can go user by user in smit passwords but is there a way to create rules for everyone at the same time? Thanks,... (2 Replies)
Discussion started by: drathbone
2 Replies

3. UNIX for Advanced & Expert Users

setting password for user using useradd?

hi all i am writing a script to create user and group from the input given to script for eg. script needs to values 1. mode - 1 or 2 2. id - if mode is 1 then id should be 2 char like x1 / v1 / v2 if mode is 2 then id should be 1 char like x / v / e from these to values group is... (1 Reply)
Discussion started by: zedex
1 Replies

4. Solaris

Password Setting

Hi: Could I set the: - Login Time-out Interval - Password History Count - Lockout Duration - Lockout Threshold for user account in Sun Solaris 5.8. Thanks for your help (6 Replies)
Discussion started by: mlsun
6 Replies

5. UNIX for Advanced & Expert Users

setting password in ldap

Hi, I have installed open ldap according to the order from this video: YouTube - bowendenning's Channel sudo apt-get install slapd sudo apt-get install ldap-utils sudo apt-get install phpldapadmin The installaion was good. However it did NOT ask from me any password. After I enter to... (0 Replies)
Discussion started by: programAngel
0 Replies

6. AIX

Setting up Password Security in AIX 5.3

In AIX 5.3 tech level 11: I want to setup a default password policy to have at least one of each of the following: alpha character, numeric character, and "special" character ("!", "&", etc). The smitty Security and Users --> Passwords --> System Password Policy screen only offers "MIN... (2 Replies)
Discussion started by: kikwit_phil
2 Replies

7. Solaris

default password setting

Can anyone kindly explain to me the meaning of the default values of the code below please? Thank you very much #MINDIFF=3 #MINALPHA=2 #MINNONALPHA=1 #MINUPPER=0 #MINLOWER=0 #MAXREPEATS=0 #MINSPECIAL=0 #MINDIGIT=0 #WHITESPACE=YES (1 Reply)
Discussion started by: cjashu
1 Replies

8. SuSE

Setting password complexity

Hi, I am setting password complexity in SLES 11. I am able to do most of things pam-config -d --pwcheck pam-config -a --cracklib pam-config -a --cracklib-minlen=8 pam-config -a --cracklib-dcredit=-1 pam-config -a --cracklib-ocredit=-1 pam-config -a --pwhistory pam-config -a... (1 Reply)
Discussion started by: solaris_1977
1 Replies

9. Solaris

Problems setting password.

Hi All, I have a problem setting the password when I have to create a user and password as detailed below. username : gaacj01 password : oshopp01 username : gaacj02 password : oshopp02 username : gaacj03 password : oshopp03 username : gaacj04 password : oshopp04 username : gaacj05 ... (17 Replies)
Discussion started by: kittigolf
17 Replies

10. HP-UX

Password compliance setting

I need to set password compliance for some servers in my company. However, the requirements are that we need to set different password policies for 3 different user groups within the company. These are : System Users: i.e root, etc Batch/Application Users: oracle, bscs, etc Standard User:... (0 Replies)
Discussion started by: anaigini45
0 Replies
vga_init(3)							Svgalib User Manual						       vga_init(3)

NAME
vga_init - initialize svgalib library SYNOPSIS
#include <vga.h> int vga_init(void); DESCRIPTION
It detects the chipset and gives up supervisor rights. This is the recommended first line of any program that uses svgalib. vga_setchipset(3) can be called before it to avoid detection. Svgalib catches a bunch of signals that usually kill your program to restore textmode. If you catch signal's before calling vga_init() svgalib will restore textmode and prepare for shutdown and then call your handler routine. If you don't want this, catch the signal after calling vga_init and do not daisychain to svgalib's original handler. WARNING! svgalib needs two signals for it's own purposes (that is managing console switches). To avoid problems it uses the otherwise unused signals SIGUSR1 and SIGUSR2. However, this means that you cannot use them in your program by any means. They are setup by vga_init() as everything else is. Since version 1.2.11 vga_init() includes code to hunt for a free virtual console on its own in case you are not starting the program from one (but instead over a network or modem login, from within 'screen' or an 'xterm'). Provided there is a free console, this succeeds if you are root or if the svgalib calling user own the current console. This is to avoid people not using the console being able to fiddle with it. On graceful exit the program returns to the console from which it was started. Otherwise it remains in text mode at the VC which svgalib allocated to allow you to see any error messages. In any case, any I/O the svgalib makes in text mode (after calling vga_init) will also take place at this new console. Alas, some games misuse their suid root priviledge and run as full root process. svgalib cannot detect this and allows Joe Blow User to open a new VC on the console. If this annoys you ROOT_VC_SHORTCUT in Makefile.cfg allows you to disable allocating a new VC for root (except when he owns the current console) when compiling svgalib. This is the default (disabling the allocation for root). vga_init() returns a non-zero value in case of errors. As of this writing it will return -1 if it is unable to allocate a graphical con- sole. Otherwise, 0 is returned. BUGS
Svgalib versions prior to 1.2.11 had a security hole where it would be possible to regain root priviledges even after a vga_init() call. This is not necessarily a problem, but if your program is vulnerable to buffer overflows and other attacks, an attacker may exploit this. However, prior to your call, your program will need to run setuid root, so you should be very careful. The ioperm library by Olaf Titz will allow svgalib programs to run not setuid root. However, it gives all programs unlimited access to the hardware. Again, a malicious person can exploit this (albeit a bit more difficult) too. Thus, in general, make your svgalib programs as secure as any setuid root program. Some programs may (accidently) rely on the old behaviour (which was probably due to the author not knowing about saved uids (which might actually even not have existed in Linux at that time)). A line: security compat in the configuration file /etc/vga/libvga.conf will reinstate the old behaviour whereas security revoke-all-privs enables the (currently default) action. SEE ALSO
svgalib(7), vga_setmode(3), mouse_init(3), vga_claimvideomemory(3), vga_ext_set(3), vga_fillblt(3), vga_getcurrentchipset(3), vga_getde- faultmode(3), vga_getgraphmem(3), vga_runinbackground(3), vga_runinbackground_version(3), vga_safety_fork(3), vga_setchipset(3), vga_setchipsetandfeatures(3), vgagl(7), libvga.config(5), AUTHOR
This manual page was edited by Michael Weller <eowmob@exp-math.uni-essen.de>. The exact source of the referenced function as well as of the original documentation is unknown. It is very likely that both are at least to some extent are due to Harm Hanemaayer <H.Hanemaayer@inter.nl.net>. Occasionally this might be wrong. I hereby asked to be excused by the original author and will happily accept any additions or corrections to this first version of the svgalib manual. Svgalib (>;= 1.2.11) 27 July 1997 vga_init(3)
All times are GMT -4. The time now is 07:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy