Setting restrictions on minimum characters for root password

Hi,
I didn't think this could be that hard. I changed /etc/default/passwd and PASSLENGTH=8. I assumed this would mean if I reset the password of root I would need to specify a minimum of 8 characters. This is not the case. I was able to set the root password to lk.
Can somebody tell me how I do this?
Thanks

I believe that the restrictions are only for non-root accounts.
Darren

Similar Messages

Shaman doesn't ask for root password. But gets root privileges!!

As the title says:
Shaman is launched as a reguler user, never asks for root password, but still i able to install and uninstall packages.
Either something in my system is seriously fucked, or there is a major securiy problem with shaman.
Running openbox, installed shaman while running gnome, if that has anythiung to say. Sudo is not installed.
Output from running shaman in terminal:
[gert@flyktig ~]$ shaman
This process is currently running setuid or setgid.
GTK+ does not allow this therefore Qt cannot use the GTK+ integration.
Try launching your app using 'gksudo', 'kdesudo' or a similar tool.
See http://www.gtk.org/setuid.html for more information.
Translations are enabled.
Loading translations from "/usr/share/shaman/translations/"
Parsing "core"
Parser exited
Parsing "extra"
Parser exited
Parsing "community"
Parser exited
Parser exited
Log File should be: ""
"core" ---> "http://mirror.archlinux.no/core/os/i686"
"extra" ---> "http://mirror.archlinux.no/extra/os/i686"
"community" ---> "http://mirror.archlinux.no/community/os/i686"
Root privileges retired.
"/home/gert/.config/shaman/shaman.conf"
>>
>> Shaman 1.0.9
>> Compiled against Qt 4.4.1
>> Running with Qt 4.4.3
>>
>> Our website is @ http://shaman.iskrembilen.com/ , join in!!
>> You can also find a bugtracker in the website, please use it.
>>
>> Have you found a bug? Help us solving it faster! Please read
>> http://shaman.iskrembilen.com/trac/wiki/Debugging_Shaman
>> and please follow these steps to report bugs effectively!
>>
>> Starting Up Shaman...
User agent is: "shaman/1.0.9 (Linux i686) libalpm/3.1.1"
Shaman registered on the System Bus as ":1.51"
Service org.archlinux.shaman successfully exported on the System Bus.
--> UNSETENV HTTP_PROXY
--> UNSETENV FTP_PROXY
Populating Repo column
Log file is: /var/log/pacman.log
refinePkgView
The left TextBox is over, let's do the ComboBox
Show all packages
Remove Package
"Uninstall package: alunn"
"alunn"
"community"
Process Queue
Queue Dialog started
Queue signals connected
Starting Package Removal
Root Privileges granted.
Uid is: 1000
Received Event Callback
Alpm Thread Waiting.
Entering Queue Lock
Releasing Queue Lock
Alpm Thread awake.
Received Event Callback
Alpm Thread Waiting.
Entering Queue Lock
Releasing Queue Lock
Alpm Thread awake.
Received Event Callback
Alpm Thread Waiting.
Entering Queue Lock
No scriptlet for package alunn
Releasing Queue Lock
Alpm Thread awake.
Received Event Callback
Alpm Thread Waiting.
Entering Queue Lock
No scriptlet for package alunn
Releasing Queue Lock
Alpm Thread awake.
/sbin/ldconfig: Can't create temporary cache file /etc/ld.so.cache~: Ikke tilgang
Root privileges retired.
Transaction Completed Successfully
refinePkgView
refinePkgView
The left TextBox is over, let's do the ComboBox
Show all packages
[gert@flyktig ~]$

The point of this thread was that you don't need to enter the root password at all. Not the first time, not ever.
As far as I understand, it is supposed to work like this: When you first use shaman too install anything, it asks for the root password You can tick a "Do not ask me again"-box, so you don't have to enter the password again. If you tick the box and enter the password, shaman add the lines
[auth]
askforpwd=false
to the users shaman.conf-file (~./config/shaman/shaman.conf) The next time shaman is run, it checks the config file, and if the askforpwd value is set to false, it grants itself root privileges (with some nifty setuuid root-thingy, I imagine) This is not the problem - this is the feature.
The bug is this:
the fact that any user can add the lines
[auth]
askforpwd=false
to his own shaman.conf file, without ever entering the root password in shaman. The next time shaman is run, it checks the config file, and if the askforpwd value is set to false, it grants itself root privileges - even though the user has never entered the root password.
This works for any unprivileged user on the system.
If that is indeed a feature intended by any sane person, then I'm Mother Mary. And that can't be, seeing as I don't have breasts.

How can i see hidden characters for email passwords?

how can I see hidden characters for email passwords?

You can't. Under what circumstances are you hoping to see the characters? When you type them in? You do see each character as you type it in for a fraction of a second. But you can't see the whole thing.

After jumpstart host doesn't prompt for root password

Hiya gang,
I am migrating my jumpstart functionality to a new server and while it would appear that 100% of things are identical on both (as far as my /jumpstart tree is concerned), when I jumpstart a host (V240, in this case, but I've seen it on a SunBlade 150 too) everything appears to go well, but after the host reboots at the very end and I attempt to log in on console as root I am not even prompted for a password.
I've booted to single user over the net and on the disk that was just jumpstarted I see what would appear to be a normal Solaris system. There are no indications that I can find of why it wouldn't prompt for password at all, and I'm not well enough versed with the way the login functionality works to know why this is.
My new jumpstart server is running Solaris 10 (08/07), and I'm trying to jump a host with the same version. The very same jumpstart using my old jumpstart server works just fine.
Thanks in advance,
pb

Darren,
Thanks for your reply. It got me in the right frame of mind for troubleshooting :)
I set up pam debugging for pam_ldap and got the following messages in /var/adm/messages:
Aug 29 10:13:46 testfoo login: [ID 293258 auth.warning] libsldap: Status: 2 Mesg: Unable to load configuration '/var/ldap/ldap_client_file' ('').
Aug 29 10:13:46 testfoo login: [ID 562097 auth.alert] open_module: Owner of the module /usr/lib/security/pam_mkhomedir.so is not root
Aug 29 10:13:46 testfoo login: [ID 487707 auth.error] load_modules: can not open module /usr/lib/security/pam_mkhomedir.so
Aug 29 10:13:46 testfoo svc.startd[7]: [ID 694882 daemon.notice] instance svc:/system/console-login:default exited with status 1
Aug 29 10:56:51 testfoo su[3209]: [ID 105162 auth.alert] open_pam_conf: Owner of /etc/pam.conf is not root
Aug 29 10:57:49 testfoo login[1225]: [ID 105162 auth.alert] open_pam_conf: Owner of /etc/pam.conf is not root
...so, I checked them out and /etc/pam.conf and /usr/lib/security/pam_mkhomedir.so are both owned nobody:nobody, which smelled like an NFS issue since both of those files are copied over to the hosts as part of a JASS_FILES variable, but during the finish script execution (they're copied by install-templates.fin). So, I did some digging there and found another Sun forum thread that had info on it:
http://forums.sun.com/thread.jspa?forumID=841&threadID=5100999
...so I made the requisite change to /etc/default/nfs (setting the max version to 3) and the next jumpstart I tested worked perfectly, password prompt and all. All files that were previously owned nobody:nobody had the correct ownership this time around.
Crazy!
Thanks again Darren for your input!

Snow Leopard Finder always prompting for root password

I've just 'upgraded' to Snow Leopard from Tiger on my Macbook Pro, only because increasing numbers of applications wouldn't install on Tiger. Snow Leopard is significantly slower than Tiger (2 gig plainly isn't enough for SL) and it's knackered a few of my installed applications, but that's not the main irritation. Now, when I carry out any move or delete operations in the Applications folder in Finder, I'm repeatedly prompted for the root password, even though I'm logged in as the root user. As it's quite a long password, for security reasons, this is a real PITA. Under Tiger, I was never so prompted. Can anyone suggest why Leopard's producing this prompt, and what can be done about it? Other than de-install SL and re-install Tiger, that is...
Fred

William Boyd, Jr. wrote:
Is running as "root" your normal mode of operation? If so, why? For several reasons that's recommended.
Fred Riley wrote:
Ok, I suppose I should be a bit more accurate. I login as user 'fredriley' which is a user with superuser rights. I don't login as 'root' because that's pretty bad practice in the Unix world (and rightly so), so my original message was inaccurate.
I'm guessing that's a mistype and should say "For several reasons that's not recommended" since in OS X root is disabled by default. What you were really getting a prompt for is the admin password. But you know that.
Now, though, I find some apps that would work under Tiger not working under SL, and I see no real functionality gain from 10.4 to 10.6. Ho hum.
Only because the application versions you have were written for an OS that was superseded almost four years ago. The current versions of those apps are likely better than ever.
As for "no functionality gain" ...look harder. For me, Tiger was a good solid OS with a few annoyances, Leopard was even more solid with the refinement and removal of most of the Tiger annoyances, and Snow Leopard is a further optimization.
Some people complain about new versions of various apps and OSs only getting loaded down with feature bloat. Well, with OS X you also get a lot of refinement and optimization. If a new version appears to have "no functionality gain," would that not imply that most of the work went into substance (performance, efficiency, workflow) rather than style (feature bloat and eye candy)? Just trying to help you keep an open mind. Personally, I would not want to go back to Tiger because I would miss the subtle but positive adjustments that were made since then. Tiger would just annoy me now.

How to restrict number of characters for an input field

Hi All,
I have an input field.
The max number of characters for this input field is 10.
when a user enter more then 10 characters. it should prompt for an error or the input field should not allow to accpet the 11 character.
how we do this in VC.
need your helpful answers
Rgds
Srinivas

Hi Srinu
You could achieve this by configuring error messages under the formula:-
Select the control properties and in the Input field at the Display tab write the formula
"IF((@<LEN(text)>10),'appropriate message','Records available')"
Note :- there is a LEN(text) under text functions in formula tab.
Regards
Navneet
Message was edited by:
Navneet Giria

How can I set my iphone to prompt for a password when viewing a selected email account?

I can see a lot of people complaining about adhoc password entry when using email but nothing where people actually want to be prompted for a password. If I have multiple email accounts and a phone where others can pick up and enter the top level security 4 digit number, I would like one of the email accounts to be slightly more secure than the others, hence need it to prompt for a password. Does anybody have any ideas how I can do this?

Sorry, there is no way to do this in the current iOS. Suggest such to Apple here:
http://www.apple.com/feedback/iphone.html

What are the ASC11 and hexadecimal characters for wireless passwords?

I am trying to set up my wireless airport and have no clue what these characters are. I use a cable modem and a router for my current setup but now have an Extreme and Express to go wireless. I remember seeing a diagram for setting up a home network but can't locate it now that I need it.
Thanks in advance for any help.

Are the characters numbers? Letters? OR????
Are they to be entered in a certain order or font???

Just purchased a second hand iPad 3 in Bangkok which requires set up, but asks me for iCloud password from previous owner which I cannot obtain. Does anyone know how to activate

Cannot activate iPad 3 I recently purchased second
hand. I need to have previous owners iCloud details, which I cannot get. Does anyone know if iPad can be activated?

If you are trying to activate an iPad or iPhone and it is asking for a previous owners Apple ID and password, you have encountered the Activation Lock. This is a security feature that prevents thieves from setting up and using a stolen or lost iPad or iPhone. You have no alternative. You must contact the previous owner to get permission to use the device. If you cannot contact the previous owner return the device to where you bought it and get a refund. You will never be able to activate the device and no one can help you do it.

Yaourt suddenly asking for root password, pacman-color [NEVERMIND]

So just a few days ago I started getting the following whenever I try to install something from yaourt:
==> Continue building boxee-source ? [Y/n]
==> --------------------------------------
==>
==> Building and installing package
==> Install or build missing dependencies for boxee-source:
Password: <just to see what's up I type the wrong password...>
su: incorrect password
Password:
bash: pacman-color: command not found
Any ideas why yaourt is invoking su and trying to invoke pacman-color? I can't install anything from aur using yaourt anymore, it always ends up failing:
Password:
bash: pacman-color: command not found
==> WARNING: Your packages are saved in /tmp/yaourt-tmp-mgalgs/
==> WARNING: Following packages have not been installed:
db4.5
==> WARNING: Dependencies have been installed before the failure
==> Restart building python24 ? [y/N]
==> ---------------------------------
==>
==> WARNING: Following packages have not been installed:
python24
==> WARNING: Dependencies have been installed before the failure
==> Restart building boxee-source ? [y/N]
==> -------------------------------------
==>
==> WARNING: Following packages have not been installed:
boxee-source
(I'm showing boxee-source here, but the same thing happens with any aur package...)
thanks!
Last edited by mitch_feaster (2011-03-22 15:39:32)

Ouch, guess I'll just run along then... I don't remember enabling testing but I'll have to double-check.
su is being invoked before pacman, which is why I've done nothing more with it than try (unsuccessfully) to install it with yaourt... But I'll just be getting off y'all's front lawn now...

Allowed Characters for Password

I'm using ACEGI and it works well. However, if you enter certain 'bad' characters for your password, it will set the password no problem, but you can never authenticate against it. So if your password is test(oo), that will work. But test!oo! will fail at login time. I'm trying to figure out which characters are acceptable and which are not. I don't see that there's any industry standard and everyone seeme to have their own allowed character set. Does anyone know if the good vs. bad characters for ACEGI? Or can anyone recommend a character set that's universal?

Also, I've been searching Google for the last hour looking for a good way to use regex to figure out if the input has characters that aren't allowed but all i can find is pattern matching, replacing, exact matching, etc. Why are there no examples that simply check all characters in a string to see if any of the characters exist in another string. Seems simple enough to me. I just want to make a string of all the bad chars and then test the input to make sure they aren't in there. I must be missing something.

Maximum Number of Characters for Password??

Hello, and thank you for reading my post. I recently modified my Apple ID Password to a very strong password containing 32 characters. When I try to log into this discussions group with that particular Apple ID, I can't because the website won't accept the password? Wouldn't all of Apple's sites accept the same password?
Is there a maximum number of characters for a password in this discussion group?
Thanks

What makes you believe that 32 characters is remotely necessary? As Ralph indicates, a shorter password is equally secure, in realistic terms. Keep in mind that even if some hacker set up a script to repeatedly try random passwords on your account, they're never going to get in because there are limits on the number of times one can enter an incorrect password before being blocked on any decent system. You can have a much shorter password, and as long as a human can't guess it from what is publicly known about you, it's secure.

Root Password Problem

Hi ,
I am new to solaris . I installed the solaris 10 (beta 7) on P-111 machine. I start installation with Intractive installation but after 1 cd complition , OS reboots but no GUI. I tried 2-3 times.
After that i choose the option Jump start and installation completes. During the installation root password was not asked.
After installation ,when i login it just ask user not for password.
I can login in CDE session but not able in Java Desktop Environment.
Now I want to add user with the help of "Solaris management console" utility. But it ask for Root password.
Now please guide me how i can choose the Root password and how i can login in the Java desktop environment.
Regards
Gorayen

You can set your password with the passwd command

[Solved] Reset root password

Hi folx
I need to reset the root password. I tried going into GRUB and appending the relevant line with:
(1.) single
(2.) 1
(3.) single init=/bin/bash
Result:
(1.) asked for root password during boot
(2.) asked for root password during boot
(3.) didn't get that far as it went into kernel panic
I downloaded Ubuntu 8.10 desktop to use as a live CD, but that didn't work as the CD just dumped me into an initramfs session.
How am I supposed to reset my root password?
Thank you, wickyd.
Last edited by wickyd (2009-03-19 07:38:14)

this has all been discussed before - ad nauseatum
1) boot up with _any_ live cd
2) mount your root filesystem as - say - /mnt/fs
3) vi /mnt/fs/etc/passwd
change the first line to:
root::0:0:root:/root:/bin/bash
4) unmount /mnt/fs and reboot
5) you can now log in as 'root' with no passwd
6) pwconv && passwd (now set new password)
<edit>
With all due respect - chroot is _not_ the way to go.
In order to actually _set_ a new password, you have to run the same kind of
authorization as in your present system - it may be different for different distros.
</edit>
Last edited by perbh (2009-03-18 16:49:01)

"Always Open In..." View Options for Root Level of a Disk Image File

I ran into a problem/bug tonight that I can't find listed anywhere and was wondering if anyone else has encountered it. I am using Snow Leopard (now 10.6.1), upgraded from the last revision of Leopard.
I create DVD-R sized disk images with Disk Utility (using "Mac OS Extended" only w/o Journaling) for saving downloaded files. Because of the number of files on this disk, I create single-letter folders (for alphabetical filing) and set up these disk images to "Always Open In List View". For the individual folders, I can set these to "Always Open In List View" without a problem. However, for the "root level" of these disk images, I can only access "Always Open In Icon View" no matter which view option is selected.
For previously created disk images that were already set to "Always Open In List View", these show the previously set "List View" at the disk image "root level" as expected. But if I uncheck the box, it immediately goes to "Always Open In Icon View". And like before, no matter which view option is selected, I can never get back to "Always Open In List View". Note also that I can set this option as expected for "root levels" of real disks - this only seems to be a problem with the disk image files.
I had no problems at all with this under Tiger or Leopard. I've only run into this now under Snow Leopard. The upgrade tonight to 10.6.1 hasn't seem to affect this problem.
So should I be doing something differently now to get this option to reappear, a possible conflict with something on my computer or is this a bug with Snow Leopard? Can anyone else duplicate this issue?

Additional info, in case anyone is running into this issue...
If I do the following with the "root level" of the disk image, I can set the "Always Open in List View" option.
1. Open the "root level" view of the disk image - for me, it always opens in icon view. Then, select "Show View Options" from the View menu.
2. Check the "Always Open in Icon View" box. While leaving this dialog open, select "as List" from the View menu.
3. Uncheck the "Always Open in Icon View" box. It will instantly turn into "Always Open In List View". Recheck this box immediately, then close dialog. This will make the setting stick.
I've been able to repeat this situation several times. I might be wrong, but it sure acts like a small bug to me. Hope this helps anyone else who might have encountered this issue.

Setting restrictions on minimum characters for root password

Similar Messages

Maybe you are looking for