Disabling password requirement in boot menu + rearranging boot menu



  • Hello! I had a couple of questions about tuning fog trunk to better suit my purposes. (I’m using 5958)

    Multicasting has been going very well, but I wanted to know if there was a way to disable the password requirement to multicast and quick image in fog trunk. I mostly use fog to multicast a bench of machines, or quick image single ones.

    How would I disable login requirement for the fog boot menu when imaging machines?

    Also - is there a way to change the order of entries on the fog boot menu? For example, I’d like Multicast to be the first option. then Quick Image, then whatever.

    Any insight would be appreciated. Thanks, guys!


  • Moderator

    @Junkhacker said:

    worth noting here is that if you create a “Mobile/Quick Image Access Only” type account you can use the pxe menu for what you want but the info will not work to log into the web interface. slightly more secure since that way you’re not sending out the admin username/password as plain text to every host that pxe boots.

    So using that method, they can create a new account with “Mobile/Quick image access only” and plug that user’s username and pass into the script below to make it more secure. Nice.


  • Developer

    worth noting here is that if you create a “Mobile/Quick Image Access Only” type account you can use the pxe menu for what you want but the info will not work to log into the web interface. slightly more secure since that way you’re not sending out the admin username/password as plain text to every host that pxe boots.


  • Moderator

    You could also add the following lines to the top

    set username fogusername
    set password fogpassword

    Giving the following:

    set username fog
    set password password
    params
    param mac0 ${net0/mac}
    param arch ${arch}
    param ${username}
    param ${password}
    param sessionJoin 1
    isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
    isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
    

  • Moderator

    @forte647 said:

    @forte647 said:

    Deleting those lines causes my Multicast Join entry to not work (like I can select it but it just knocks me back to the first menu). Is there a way to hard code the user and pass into the param of multijoin? If so, what would that look like? Like if I wanted to hardcode username “fog” and password “password”.

    Sorry for the double post, but I got ballsy and tried it myself and this worked for me. My multijoin params are:

    params
    param mac0 ${net0/mac}
    param arch ${arch}
    param username fog
    param password password
    param sessionJoin 1
    isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
    isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

    got rid of the first login line (I guess that’s the login prompt) and then changed the user/pass lines from ${username} to a username I wanted (default account fog) and its ${password} “password”.

    Changing the default entry also worked, although in my mind I really wanted to arranged differently, but that’s okay too.

    Thank you, guys. :)

    Now that is sweet, good job and great solution!



  • @forte647 said:

    Deleting those lines causes my Multicast Join entry to not work (like I can select it but it just knocks me back to the first menu). Is there a way to hard code the user and pass into the param of multijoin? If so, what would that look like? Like if I wanted to hardcode username “fog” and password “password”.

    Sorry for the double post, but I got ballsy and tried it myself and this worked for me. My multijoin params are:

    params
    param mac0 ${net0/mac}
    param arch ${arch}
    param username fog
    param password password
    param sessionJoin 1
    isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
    isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

    got rid of the first login line (I guess that’s the login prompt) and then changed the user/pass lines from ${username} to a username I wanted (default account fog) and its ${password} “password”.

    Changing the default entry also worked, although in my mind I really wanted to arranged differently, but that’s okay too.

    Thank you, guys. :)



  • Deleting those lines causes my Multicast Join entry to not work (like I can select it but it just knocks me back to the first menu). Is there a way to hard code the user and pass into the param of multijoin? If so, what would that look like? Like if I wanted to hardcode username “fog” and password “password”.


  • Moderator

    These answers are both correct, but there’s another way and that’s to use the FOG Menu Configuration in the Webgui to change the paramaters passed to boot.php

    Here is my fog.multijoin for instance

    params
    param mac0 ${net0/mac}
    param arch ${arch}
    param sessionJoin 1
    isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
    isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
    

    Notice three lines are remove, the login param, the user param and the password param. Although, for me personally, this does not work on newer revisions. Works on 6186 and before, not sure about anything after (in my testing it no longer worked and just brought you back to main menu saying invalid login)


  • Testers

    @forte647 You can change the default selection under FOG Configuration>iPXE Menu Customization You can check the box on Multi join for Default Item. As for logging in as @Wayne-Workman pointed out you would have to try that, but you could just create a user with a simple login, such as:
    Username: A
    Password: A
    This would make it simple to log in without any modification to the server.


  • Moderator

    Due to a bug, an older revision allowed blank passwords. Not sure if the Developers will make it a “feature”.

    r6207 allows for blanks - you’ll have to figure out which SVN revision that is. Here’s the bug thread on it: https://forums.fogproject.org/topic/6626/quick-image-accepts-blank-password-for-users-6207/3


Log in to reply
 

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.