+ Post New Thread
Results 1 to 6 of 6
O/S Deployment Thread, Fog Custom PXE Menu Password in Technical; Hi everyone I've got a problem with Fog's PXE menu - I've added GParted to my boot menu but want ...
  1. #1
    pnlrogue1's Avatar
    Join Date
    Jul 2008
    Location
    Edinburgh, Scotland
    Posts
    72
    Thank Post
    37
    Thanked 5 Times in 3 Posts
    Rep Power
    13

    Question Fog Custom PXE Menu Password

    Hi everyone

    I've got a problem with Fog's PXE menu - I've added GParted to my boot menu but want to password protect it

    When editing the /tftpboot/pxelinux.cfg/default to add the GParted option, I thought about copying the password line from another menu item but noticed that they all have different password lines, in spite of using the same password (damned clever encryption...)

    Any ideas how I can do this?

    Thanks!

  2. #2

    Join Date
    Apr 2007
    Location
    Birmingham
    Posts
    145
    Thank Post
    6
    Thanked 45 Times in 39 Posts
    Rep Power
    23
    Admittedly I only used a cleartext password for a couple of my menu items, but this is from the syslinux menu.txt documentation and should help:

    Code:
    
    MENU PASSWD passwd
    
    	(Only valid after a LABEL statement.)
    
    	Sets a password on this menu entry.  "passwd" can be either a
    	cleartext password or a password encrypted with one of the
    	following algorithms:
    
    	MD5		(Signature: $1$)
    	SHA-1		(Signature: $4$)
    	SHA-2-256	(Signature: $5$)
    	SHA-2-512	(Signature: $6$)
    
    	Use the included Perl scripts "sha1pass" or "md5pass" to
    	encrypt passwords.  MD5 passwords are compatible with most
    	Unix password file utilities; SHA-1 passwords are probably
    	unique to Syslinux; SHA-2 passwords are compatible with very
    	recent Linux distributions.  Obviously, if you don't encrypt
    	your passwords they will not be very secure at all.
    
    	If you are using passwords, you want to make sure you also use
    	the settings "NOESCAPE 1", "PROMPT 0", and either set
    	"ALLOWOPTIONS 0" or use a master password (see below.)
    
    	If passwd is an empty string, this menu entry can only be
    	unlocked with the master password.

  3. #3
    pnlrogue1's Avatar
    Join Date
    Jul 2008
    Location
    Edinburgh, Scotland
    Posts
    72
    Thank Post
    37
    Thanked 5 Times in 3 Posts
    Rep Power
    13
    Hey Andy, thanks for the reply but I'm a bit confused:

    Code:
    If passwd is an empty string, this menu entry can only be
    unlocked with the master password.
    Does that mean that if I set a master password and then leave the other options blank, ALL menu options will use the same one? If so, that would be sweeeeeeeeeeeeeeeeeeeeeeeeeeet

    ---

    Code:
    Use the included Perl scripts "sha1pass" or "md5pass" to
    encrypt passwords.  MD5 passwords are compatible with most
    Unix password file utilities; SHA-1 passwords are probably
    unique to Syslinux; SHA-2 passwords are compatible with very
    recent Linux distributions.  Obviously, if you don't encrypt
    your passwords they will not be very secure at all.
    How do I use these? Sorry - bit of a Linux newbie

  4. #4
    pnlrogue1's Avatar
    Join Date
    Jul 2008
    Location
    Edinburgh, Scotland
    Posts
    72
    Thank Post
    37
    Thanked 5 Times in 3 Posts
    Rep Power
    13

    Bump and new request

    Hey guys

    Never got a working solution here but I was thinking that the ideal would be that I can set a 'master' password which unlocks all menu items (i.e. I set the password once and no matter what entry I click on (apart from Boot from Hard Disk), it asks for the same password so it doesn't have to be set on each item - is that possible?

    Thanks

  5. #5

    Join Date
    Oct 2009
    Location
    Brighton, UK
    Posts
    4
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Hi,

    I wanted to get the same results. Turns out the 'Master password' is like a master key, it'll open any label password.

    So to get the effect you're after all you need to do is under each label set a random password, then set the master password, don't worry about remembering the random password as the master password will get you in but keep the kids out!

    If you want an option accessible to the kids (boot from local hard drive) then just don't set a label password on it.

    Setting passwords doesn't affect FOG's ability to boot tasks set by the web interface.

    HTH,

    Seb

  6. #6
    ssx4life's Avatar
    Join Date
    Sep 2009
    Posts
    106
    Thank Post
    0
    Thanked 12 Times in 12 Posts
    Rep Power
    13
    if you need more help with setting passwords on the PXE boot menu let me know.



SHARE:
+ Post New Thread

Similar Threads

  1. [Fog] FOG not seeing network card when PXE on Aspire M3800
    By teky in forum O/S Deployment
    Replies: 3
    Last Post: 20th July 2010, 12:19 PM
  2. [Fog] PXE Boot Menu Password Causes Failure to connect to DB
    By mpmackenna in forum O/S Deployment
    Replies: 1
    Last Post: 14th January 2010, 02:12 AM
  3. [Fog] IRQ Error when loading PXE Linux in FOG
    By mpleonard in forum O/S Deployment
    Replies: 0
    Last Post: 24th November 2009, 02:43 PM
  4. [Fog] DHCP/PXE problem
    By danboid in forum O/S Deployment
    Replies: 3
    Last Post: 18th August 2009, 02:58 PM
  5. Custom Start menu problem
    By iSteve in forum Windows
    Replies: 2
    Last Post: 9th August 2007, 12:51 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •