• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Disabling password requirement in boot menu + rearranging boot menu

Scheduled Pinned Locked Moved
FOG Problems
5
10
4.5k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F
    forte647
    last edited by forte647 Feb 11, 2016, 1:26 PM Feb 11, 2016, 7:02 PM

    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!

    I 1 Reply Last reply Feb 11, 2016, 7:41 PM Reply Quote 0
    • W
      Wayne Workman
      last edited by Feb 11, 2016, 7:16 PM

      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

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      1 Reply Last reply Reply Quote 0
      • I
        ITSolutions Testers @forte647
        last edited by Feb 11, 2016, 7:41 PM

        @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.

        1 Reply Last reply Reply Quote 1
        • Q
          Quazz Moderator
          last edited by Feb 12, 2016, 9:14 AM

          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)

          1 Reply Last reply Reply Quote 1
          • F
            forte647
            last edited by Feb 12, 2016, 3:59 PM

            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”.

            F 1 Reply Last reply Feb 12, 2016, 4:08 PM Reply Quote 0
            • F
              forte647 @forte647
              last edited by Feb 12, 2016, 4:08 PM

              @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. 🙂

              W 1 Reply Last reply Feb 12, 2016, 4:11 PM Reply Quote 2
              • W
                Wayne Workman @forte647
                last edited by Feb 12, 2016, 4:11 PM

                @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!

                Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                Daily Clean Installation Results:
                https://fogtesting.fogproject.us/
                FOG Reporting:
                https://fog-external-reporting-results.fogproject.us/

                1 Reply Last reply Reply Quote 1
                • Q
                  Quazz Moderator
                  last edited by Quazz Feb 12, 2016, 10:21 AM Feb 12, 2016, 4:20 PM

                  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
                  
                  1 Reply Last reply Reply Quote 2
                  • J
                    Junkhacker Developer
                    last edited by Feb 12, 2016, 6:51 PM

                    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.

                    signature:
                    Junkhacker
                    We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                    W 1 Reply Last reply Feb 12, 2016, 7:13 PM Reply Quote 1
                    • W
                      Wayne Workman @Junkhacker
                      last edited by Feb 12, 2016, 7:13 PM

                      @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.

                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                      Daily Clean Installation Results:
                      https://fogtesting.fogproject.us/
                      FOG Reporting:
                      https://fog-external-reporting-results.fogproject.us/

                      1 Reply Last reply Reply Quote 0
                      • 1 / 1
                      1 / 1
                      • First post
                        7/10
                        Last post

                      168

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project