Further, this behavior causes root-owned files and directories in a user's home directory, e.g.:
ubuntu@lp1556302:~$ ls -l /home/ubuntu/.vim*
ls: cannot access '/home/ubuntu/.vim*': No such file or directory
ubuntu@lp1556302:~$ sudo vim /tmp/test
ubuntu@lp1556302:~$ ls -l /home/ubuntu/.vim*
-rw------- 1 root root 700 May 14 16:31 /home/ubuntu/.viminfo
ubuntu@lp1556302:~$ ls -ld /home/ubuntu/.emacs*
ls: cannot access '/home/ubuntu/.emacs*': No such file or directory
ubuntu@lp1556302:~$ sudo emacs /tmp/test
ubuntu@lp1556302:~$ ls -ld /home/ubuntu/.emacs*
drwx------ 2 root root 4096 May 14 16:32 /home/ubuntu/.emacs.d
Further, this behavior causes root-owned files and directories in a user's home directory, e.g.:
ubuntu@lp1556302:~$ ls -l /home/ubuntu/.vim* ubuntu/ .vim*': No such file or directory .viminfo
ls: cannot access '/home/
ubuntu@lp1556302:~$ sudo vim /tmp/test
ubuntu@lp1556302:~$ ls -l /home/ubuntu/.vim*
-rw------- 1 root root 700 May 14 16:31 /home/ubuntu/
ubuntu@lp1556302:~$ ls -ld /home/ubuntu/ .emacs* ubuntu/ .emacs* ': No such file or directory .emacs* .emacs. d
ls: cannot access '/home/
ubuntu@lp1556302:~$ sudo emacs /tmp/test
ubuntu@lp1556302:~$ ls -ld /home/ubuntu/
drwx------ 2 root root 4096 May 14 16:32 /home/ubuntu/
bug 1828208
and so on. This problem is true for *any* program/application that creates any files in $HOME, and might be run under sudo.