Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    protect config.g with password.

    Scheduled Pinned Locked Moved
    Firmware wishlist
    4
    5
    225
    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.
    • FS-TOOLSundefined
      FS-TOOLS
      last edited by Phaedrux

      Hello,

      is it maybe possible to safe the config.g file with a keyword?

      Best regards

      Fabian

      Phaedruxundefined 1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator @FS-TOOLS
        last edited by

        @FS-TOOLS said in Save config.g with keyword.:

        with a keyword?

        Can you elaborate on what you mean by this?

        Z-Bot CoreXY Build | Thingiverse Profile

        FS-TOOLSundefined 1 Reply Last reply Reply Quote 0
        • FS-TOOLSundefined
          FS-TOOLS @Phaedrux
          last edited by FS-TOOLS

          @Phaedrux
          I mean, that only someone like an admin can change something in the system configurations

          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @FS-TOOLS
            last edited by

            @FS-TOOLS there's currently no password protection for the config etc

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            1 Reply Last reply Reply Quote 0
            • Phaedruxundefined Phaedrux moved this topic from Tuning and tweaking
            • oliofundefined
              oliof
              last edited by

              What you could try is to use SBC mode and set the immutable flag on config.g on the linux side. Then you would need to be superuser to unset the flag before changes to config.g would be saved. I would not recommend this though, because its hard to debug when things go awry.

              And even if config.g.would be locked down, users can change roughly every aspect of machine configuration dynamically via gcodes. So the next step would be to only allow "reasonable operator" and "admin" commands depending on who uses the machine -- and there is no facility for this. Its a can of worms.

              <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

              1 Reply Last reply Reply Quote 1
              • First post
                Last post
              Unless otherwise noted, all forum content is licensed under CC-BY-SA