This is a reminder to user sudoedit. Especially useful for Vim and Neovim users who have a rich and personal configuration.

sudoedit /etc/fstab

is also an option. sudoedit is a short form for sudo -e. It uses the default editor set int EDITOR or VISUAL variable. The difference to sudo vim FILE or sudo nano FILE is, that sudoedit FILE will use the editor configuration from the current user instead from the root. For me this makes a huge difference, because my plugins and settings for Neovim are not used when doing sudo vim.

Man page: https://linux.die.net/man/8/sudoedit

-e’ The -e (edit) option indicates that, instead of running a command, the user wishes to edit one or more files. In lieu of a command, the string “sudoedit” is used when consulting the security policy. If the user is authorized by the policy, the following steps are taken:

  1. Temporary copies are made of the files to be edited with the owner set to the invoking user.

  2. The editor specified by the policy is run to edit the temporary files. The sudoers policy uses the SUDO_EDITOR, VISUAL and EDITOR environment variables (in that order). If none of SUDO_EDITOR, VISUAL or EDITOR are set, the first program listed in the editor sudoers(5) option is used.

  3. If they have been modified, the temporary files are copied back to their original location and the temporary versions are removed.

If the specified file does not exist, it will be created. Note that unlike most commands run by sudo, the editor is run with the invoking user’s environment unmodified. If, for some reason, sudo is unable to update a file with its edited version, the user will receive a warning and the edited copy will remain in a temporary file.

  • Name@programming.dev
    2·
    5 days ago

    Meanwhile, a reverse vim enjoyer like myself, using micro to edit any file running as my user. If it requires root to write, it will simply elevate the permissions for that operation when I press Ctrl+S, asking for password if needed.

    Same idea with VSCodium, but via GUI polkit prompt.

    Life is good when you don’t hjkl _

  • notabot@lemm.ee
    18·
    7 days ago

    Be cautious of doing this with security sensitive files. When it copies the file and gives you ownership, any sensitive data in it is exposed to any process running as your user id, and and temporary fil£s the editor creates may also contain the sensitive content and be owned by you.

    • thingsiplay@beehaw.orgOP
      3·
      7 days ago

      Good point. I was always wondering how secure this is, as it works with copies of the files in my environment. Because I’m in my personal environment, doing sudoedit /etc/fstab does not let me edit other files from root while in that file. That means if any of the plugins from Vim tries to, they can’t edit arbitrary files, right? (If you don’t trust the plugin, then don’t use, but that’s another topic.) Little side note, just learned that sudoedit ~/.bashrc does not allow me to edit files in my home too.

      • notabot@lemm.ee
        3·
        7 days ago

        Vim is running as you, rather than root, so you wont be able to edit other files as root, and any rogue plugins wont be able to either, which is good.

        Sudoedit has various guards around what it’ll let you edit, in particular, you can’t edit a file in a directory you already have write permission on as doing so allows the user to bypass restrictions in the sudoers setup (there’s more detail in their issue tracker. If the directory is already writable though, you don’t need sudoedit anyway.

    • thingsiplay@beehaw.orgOP
      2·
      7 days ago

      Yes. And this has huge implications, as as root user in Vim you can load and edit other files. While sudoedit is limited to your personal environment, as while the editing process no root privileges are in use. (I think…)

  • Yingwu@lemmy.dbzer0.comEnglish
    21·
    7 days ago

    I had a problem where even if I tried to set the default editor to vim, it’d still not use my lazyvim setup and I never figured out how to fix it.

    • thingsiplay@beehaw.orgOP
      2·
      7 days ago

      I use LazyVim too BTW. You mean it would not use in sudo environment or in your current environment?

      • Yingwu@lemmy.dbzer0.comEnglish
        1·
        7 days ago

        It worked fine in my current environment, but not with sudoedit no. Can’t remember exactly why, might look at it again. It worked for you just by setting the default editor variable?

        • thingsiplay@beehaw.orgOP
          1·
          7 days ago

          I didn’t do anything special to make that work. The variable export EDITOR='nvim' is set in my “.bash_profile” file in “Home” directly. The point of sudoedit is to use your personal environment, so it should pick it up. If there is any configuration needed to make this work, then I"m not aware of it.

        • mbirth
          2·
          7 days ago

          It’s probably loading the home environment of root similar to sudo -H vim … instead of just elevating privileges but keeping your home environment.