Thursday, June 11, 2015

How to Determine if an HP-UX Account is Locked

/usr/lbin/getprpw -l <account>
/usr/lbin/modprpw -k <account>

You need to know if accounts are locked
System may be a "trusted" system which means that it has higher security
enabled.
On a non-trusted system the /etc/passwd file will contain the information:
man passwd:
-s name Display some password attributes associated with the
specified name. Superuser privilege and non-trusted
mode is required if the files repository is specified.
The format of the display will be:
name status mm/dd/yy min max warn


or, if password aging information is not present
(#### e.g. that info is held in tcb directories ###)
name status
where status means: PS =passworded; LK =locked; and NP=no password.
passwd -s -a:
PS =passworded; LK =locked; and NP=no password
on a trusted system the /tcb directory structure holds the lock info;
man getprpw:
lockout returns the reason for a lockout in a "bit" valued string, where 0 = condition not present, 1 is present.

The position, left to right represents:
Google Voice and Video Chat Installer for Google Hangouts  "The Installer encountered error 1625:  This installation is forbidden by system policy.  Contact your system administrator".

1 past password lifetime
2 past last login time (inactive account)
3 past absolute account lifetime
4 exceeded unsuccessful login attempts
5 password required and a null password
6 admin lock
7 password is a *
(If the user is NOT locked, all bits will be 0)

getprpw:
for USER in `awk -F: '{print $1}' /etc/passwd`
do
printf $USER
printf " "
/usr/lbin/getprpw -m lockout,alock $USER
done

Bryan Payne on Linkedin  https://www.linkedin.com/in/paynebryan


+Bryan Payne add me on Google Plus


SOLVED: Kickstart (system-config-kickstart) - Could not read video driver database

After I updated to Ubuntu 14.04 I tried to launch the Kickstart Configurator GUI and it wouldn't load.

Error Message: "Could not read video driver database"

# system-config-kickstart

(system-config-kickstart.py:18686): IBUS-WARNING **: The owner of /home/user/.config/ibus/bus is not root!
Traceback (most recent call last):
  File "/usr/share/system-config-kickstart/system-config-kickstart.py", line 92, in <module>
    kickstartGui.kickstartGui(file)
  File "/usr/share/system-config-kickstart/kickstartGui.py", line 131, in __init__
    self.X_class = xconfig.xconfig(xml, self.kickstartData)
  File "/usr/share/system-config-kickstart/xconfig.py", line 80, in __init__
    self.fill_driver_list()
  File "/usr/share/system-config-kickstart/xconfig.py", line 115, in fill_driver_list
    raise RuntimeError, (_("Could not read video driver database"))
RuntimeError: Could not read video driver database
# 

This resolved my issue:
# apt-get remove hwdata
# wget ftp://mirror.ovh.net/mirrors/ftp.debian.org/debian/pool/main/h/hwdata/hwdata_0.234-1_all.deb
# dpkg -i hwdata_0.267-1_all.deb
# apt-get install system-config-kickstart 
Hope this helps you.

Bryan Payne on Linkedin  https://www.linkedin.com/in/paynebryan

+Bryan Payne add me on Google Plus

Monday, April 20, 2015

MSL6000 Service password


The default service password is 5566.
Default Factory password is 56789.
If you have lost the level 1 or level 2 passwords the factory password can be used to reset them.

If the password is no longer set to the defaults... you can discover the current password by using the MSLUTIL.exe via a serial connection.  There is no need to know the serial settings as the utility will autodiscover them.  The current configuration does not have to be reset and the password will be displayed in plain text.  You will need the correct serial cable.

More information can be obtained here:
http://h200003.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=es&cc=es&taskId=115&prodSeriesId=254838&prodTypeId=12169&objectID=c00023637

Bryan Payne on Linkedin  https://www.linkedin.com/in/paynebryan

+Bryan Payne add me on Google Plus

Sunday, December 14, 2014

Monday, February 17, 2014

Office Communicator via Pidgin for Ubuntu 12.04 LTS

Installed Pidgin from repository on Ubuntu 12.04...

Added SIPE plugin from here:
https://launchpad.net/ubuntu/quantal/amd64/pidgin-sipe/1.11.2-1ubuntu1

Project screen shots are here:
http://sipe.sourceforge.net/screens/

I was running a live DVD so even though newer versions were available it complicated the dependencies and I was in a hurry... so I loaded this version.

Under Basic Tab:
Listed SIP account as the username.
Login:  Used my AD account and PW

Under Advanced I changed email address if different from login name to match my actual email address.


How to fix libnss3 error on Ubuntu 12.04

google-chrome-stable_current_amd64.deb















Answer was to satisfy the dependencies by running:

sudo apt-get update
sudo apt-get install libgconf2-4 libnss3-1d libxss1
 
then:
download chrome for linux from here:
https://www.google.com/chrome?brand=CHMO#eula

then:
sudo dpkg -i google-chrome-stable_current_amd64.deb

Friday, May 10, 2013

HP-UX: HOW TO BOOT FROM TAPE EFI ITANIUM

Keep in mind that some servers do not support booting from tape, or may require a firmware update to support booting from tape.

Exit from the boot menu to the EFI Shell

fs0:\> reconnect -r

Broadcom NetXtreme Gigabit Ethernet (BCM5704) is detected (PCI-X)
Broadcom NetXtreme Gigabit Ethernet (BCM5704) is detected (PCI-X)
HP 2Port 2Gb Fibre Channel Adapter (driver 1.42, firmware 3.03.150)
Broadcom NetXtreme Gigabit Ethernet (BCM5703) is detected (PCI-X)
HP 2Gb Fibre Channel Combo Adapter (driver 1.30, firmware 3.03.171)
Broadcom NetXtreme Gigabit Ethernet (BCM5703) is detected (PCI-X)
Scsi(Pun0,Lun0) HP      MSL6000 Series  0520 ( 20 MBytes/sec)
Scsi(Pun1,Lun0) HP      Ultrium 3-SCSI  G63W (320 MBytes/sec)
ReconnectController(0,0,0) : Status = Success

From this we gather that the Ultrium 3 Tape Drive is Pun1, Lun0.

At this point exit from the shell... returning you to the boot menu.  At this point enter the boot configuration menu and boot from a file if you want a one time boot and look for result of your reconnect -r output... in my case it was Pun1, Lun0.

Boot menu showed the device as follows:
Device Path Acpi(HWP0002,PNP0A03,700)/Pci(1|1)/Scsi(Pun1,Lun0)

Other helpful commands would be:
devtree, devices, map
Bryan Payne on Linkedin  https://www.linkedin.com/in/paynebryan

+Bryan Payne add me on Google Plus