ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Allowing Root Password Login via SSH to Dragonfly BSD

    IT Discussion
    unix bsd ssh dragonfly bsd
    5
    22
    3.4k
    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.
    • scottalanmillerS
      scottalanmiller @black3dynamite
      last edited by

      @black3dynamite said in Allowing Root Password Login via SSH to Dragonfly BSD:

      @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

      That's one of the nice things about the BSD ecosystem, people fork it way less often.

      Speaking BSD ecosystem, how is the development of BSD hypervisor, bhyve?

      It's going, but I'm not following it closely. It's not very interesting at this point.

      1 Reply Last reply Reply Quote 0
      • thwrT
        thwr @scottalanmiller
        last edited by

        @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

        By default, Dragonfly disables both root and password-based logins from SSH. This can be a big pain if you are just using the system casually or temporarily. To fix this you need to first edit the configuration file for SSHD:

        vi /etc/ssh/sshd_config

        Then to allow root to log in via SSH make PermitRootLogin be "yes":

        PermitRootLogin yes

        And to allow root or any user to use passwords for SSH login change PasswordAuthentication to "yes".

        PasswordAuthentication yes

        You'll need to restart SSHD for this to take effect:

        /etc/rc.d/sshd restart

        A whole bunch of Linux distros do the same. You should choose a more general name for the thread - like "Allowing root password login via SSH".

        Anyway, it's generally a better idea to use key based logins.

        scottalanmillerS 1 Reply Last reply Reply Quote 0
        • scottalanmillerS
          scottalanmiller @thwr
          last edited by

          @thwr said in Allowing Root Password Login via SSH to Dragonfly BSD:

          @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

          By default, Dragonfly disables both root and password-based logins from SSH. This can be a big pain if you are just using the system casually or temporarily. To fix this you need to first edit the configuration file for SSHD:

          vi /etc/ssh/sshd_config

          Then to allow root to log in via SSH make PermitRootLogin be "yes":

          PermitRootLogin yes

          And to allow root or any user to use passwords for SSH login change PasswordAuthentication to "yes".

          PasswordAuthentication yes

          You'll need to restart SSHD for this to take effect:

          /etc/rc.d/sshd restart

          A whole bunch of Linux distros do the same. You should choose a more general name for the thread - like "Allowing root password login via SSH".

          Anyway, it's generally a better idea to use key based logins.

          This is the only OS I know that does this by default. People looking for Dragonfly issues will run into it.

          black3dynamiteB 1 Reply Last reply Reply Quote 0
          • black3dynamiteB
            black3dynamite @scottalanmiller
            last edited by

            @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

            @thwr said in Allowing Root Password Login via SSH to Dragonfly BSD:

            @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

            By default, Dragonfly disables both root and password-based logins from SSH. This can be a big pain if you are just using the system casually or temporarily. To fix this you need to first edit the configuration file for SSHD:

            vi /etc/ssh/sshd_config

            Then to allow root to log in via SSH make PermitRootLogin be "yes":

            PermitRootLogin yes

            And to allow root or any user to use passwords for SSH login change PasswordAuthentication to "yes".

            PasswordAuthentication yes

            You'll need to restart SSHD for this to take effect:

            /etc/rc.d/sshd restart

            A whole bunch of Linux distros do the same. You should choose a more general name for the thread - like "Allowing root password login via SSH".

            Anyway, it's generally a better idea to use key based logins.

            This is the only OS I know that does this by default. People looking for Dragonfly issues will run into it.

            Debian disallows root login not sure about passwords.

            scottalanmillerS thwrT 2 Replies Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller @black3dynamite
              last edited by

              @black3dynamite said in Allowing Root Password Login via SSH to Dragonfly BSD:

              @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

              @thwr said in Allowing Root Password Login via SSH to Dragonfly BSD:

              @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

              By default, Dragonfly disables both root and password-based logins from SSH. This can be a big pain if you are just using the system casually or temporarily. To fix this you need to first edit the configuration file for SSHD:

              vi /etc/ssh/sshd_config

              Then to allow root to log in via SSH make PermitRootLogin be "yes":

              PermitRootLogin yes

              And to allow root or any user to use passwords for SSH login change PasswordAuthentication to "yes".

              PasswordAuthentication yes

              You'll need to restart SSHD for this to take effect:

              /etc/rc.d/sshd restart

              A whole bunch of Linux distros do the same. You should choose a more general name for the thread - like "Allowing root password login via SSH".

              Anyway, it's generally a better idea to use key based logins.

              This is the only OS I know that does this by default. People looking for Dragonfly issues will run into it.

              Debian disallows root login not sure about passwords.

              Totally different as it...

              • Allows passwords
              • Creates the user
              • Sets the user to be sudo

              All of that is not used in Dragonfly.

              1 Reply Last reply Reply Quote 0
              • thwrT
                thwr @black3dynamite
                last edited by

                @black3dynamite said in Allowing Root Password Login via SSH to Dragonfly BSD:

                @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

                @thwr said in Allowing Root Password Login via SSH to Dragonfly BSD:

                @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

                By default, Dragonfly disables both root and password-based logins from SSH. This can be a big pain if you are just using the system casually or temporarily. To fix this you need to first edit the configuration file for SSHD:

                vi /etc/ssh/sshd_config

                Then to allow root to log in via SSH make PermitRootLogin be "yes":

                PermitRootLogin yes

                And to allow root or any user to use passwords for SSH login change PasswordAuthentication to "yes".

                PasswordAuthentication yes

                You'll need to restart SSHD for this to take effect:

                /etc/rc.d/sshd restart

                A whole bunch of Linux distros do the same. You should choose a more general name for the thread - like "Allowing root password login via SSH".

                Anyway, it's generally a better idea to use key based logins.

                This is the only OS I know that does this by default. People looking for Dragonfly issues will run into it.

                Debian disallows root login not sure about passwords.

                At least Ubuntu is

                PermitRootLogin without-password

                by default

                scottalanmillerS 1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller @thwr
                  last edited by

                  @thwr said in Allowing Root Password Login via SSH to Dragonfly BSD:

                  @black3dynamite said in Allowing Root Password Login via SSH to Dragonfly BSD:

                  @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

                  @thwr said in Allowing Root Password Login via SSH to Dragonfly BSD:

                  @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

                  By default, Dragonfly disables both root and password-based logins from SSH. This can be a big pain if you are just using the system casually or temporarily. To fix this you need to first edit the configuration file for SSHD:

                  vi /etc/ssh/sshd_config

                  Then to allow root to log in via SSH make PermitRootLogin be "yes":

                  PermitRootLogin yes

                  And to allow root or any user to use passwords for SSH login change PasswordAuthentication to "yes".

                  PasswordAuthentication yes

                  You'll need to restart SSHD for this to take effect:

                  /etc/rc.d/sshd restart

                  A whole bunch of Linux distros do the same. You should choose a more general name for the thread - like "Allowing root password login via SSH".

                  Anyway, it's generally a better idea to use key based logins.

                  This is the only OS I know that does this by default. People looking for Dragonfly issues will run into it.

                  Debian disallows root login not sure about passwords.

                  At least Ubuntu is

                  PermitRootLogin without-password

                  by default

                  Right, they allow a lot. 🙂

                  1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller
                    last edited by

                    Dragonfly is tough by default because unless you use something like Salt, you can't connect to it to get keys to it in the first place. You can curl keys to it, of course. But you need totally different processes than you would typically use with any other OS to get it set up.

                    black3dynamiteB 1 Reply Last reply Reply Quote 0
                    • black3dynamiteB
                      black3dynamite @scottalanmiller
                      last edited by

                      @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

                      Dragonfly is tough by default because unless you use something like Salt, you can't connect to it to get keys to it in the first place. You can curl keys to it, of course. But you need totally different processes than you would typically use with any other OS to get it set up.

                      That means it's not even Ansible friendly. Pretty much agent-based tools like Puppet, Salt, etc... is the way to go.

                      scottalanmillerS 1 Reply Last reply Reply Quote 0
                      • scottalanmillerS
                        scottalanmiller @black3dynamite
                        last edited by

                        @black3dynamite said in Allowing Root Password Login via SSH to Dragonfly BSD:

                        @scottalanmiller said in Allowing Root Password Login via SSH to Dragonfly BSD:

                        Dragonfly is tough by default because unless you use something like Salt, you can't connect to it to get keys to it in the first place. You can curl keys to it, of course. But you need totally different processes than you would typically use with any other OS to get it set up.

                        That means it's not even Ansible friendly. Pretty much agent-based tools like Puppet, Salt, etc... is the way to go.

                        Yup, unless you have some way to push the Ansible key ahead of time, like in a curl. So back to the beginning there 🙂

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 2 / 2
                        • First post
                          Last post