all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "João Távora" <joaotavora@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>,
	Michael Albinus <michael.albinus@gmx.de>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: sudo:: method in tramp possible security issue
Date: Tue, 20 Nov 2018 18:12:05 -0500	[thread overview]
Message-ID: <jwvh8gbwdnx.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CALDnm51khRvTJ6CKW-TO7c2No6Sc92oAbOExEh6zj1p0fkbifw@mail.gmail.com> ("João Távora"'s message of "Tue, 20 Nov 2018 22:27:01 +0000")

> In other words, what bothers me the most about the sudo:: method is
> the persistent sudo session that makes me vulnerable to attackers, and
> to my elisp developing mistakes.  This is why I think a warning makes
> sense, or some visual way to identify this vulnerable state.

I guess it all depends on the sudo setup:

Can you run a shell via sudo?  On those machines where I can do that,
I typically do "sudo zsh" and then live happily in my root shell.
But even you don't, after you've used sudo, there's a time window
during which sudo won't ask for your password and during which an
attacker could run "sudo sh" via start-process, regardless of Tramp.

If you can't run a shell via sudo, then Tramp's sudo method won't work
anyway.


        Stefan



  reply	other threads:[~2018-11-20 23:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALDnm52oYOV_kPWZH62ub8seM4uug-GH68ywgXGJfDAbG7_4Xg@mail.gmail.com>
     [not found] ` <87ftvwdcdw.fsf@gmx.de>
     [not found]   ` <CALDnm51fhzD48-40-t04KU9S19Lz8_sf8Y=pKZbnSHR+tbCgTQ@mail.gmail.com>
     [not found]     ` <87bm6kdb68.fsf@gmx.de>
     [not found]       ` <CALDnm53tX4vFz4CH=P27_dUt=9dXWMrE7xdTz3iZuqybsndygg@mail.gmail.com>
     [not found]         ` <jwvmuq4zqsz.fsf-monnier+emacs@gnu.org>
     [not found]           ` <CALDnm52moQthtMvSEw2ELWjZg3yJ8jypG=TBLgSsdr6R8ru0Aw@mail.gmail.com>
     [not found]             ` <87bm6kyxc3.fsf@gmx.de>
     [not found]               ` <CALDnm5211UDT_pW-HzgnRb5dQtnCZSgN+GRGHYM1hPVAjBWavA@mail.gmail.com>
     [not found]                 ` <87k1l83yd3.fsf@gmx.de>
     [not found]                   ` <CALDnm52KU0wNd3Sd-7m78JrPcLsiNuZ8hQxcTs3PgDNG7+0a0g@mail.gmail.com>
     [not found]                     ` <87o9ajvost.fsf@gmx.de>
2018-11-20 14:13                       ` sudo:: method in tramp possible security issue João Távora
2018-11-20 21:14                         ` Paul Eggert
2018-11-20 21:18                           ` Stefan Monnier
2018-11-20 21:25                             ` Paul Eggert
2018-11-20 21:44                               ` Stefan Monnier
2018-11-20 22:06                               ` Michael Albinus
2018-11-20 22:27                                 ` João Távora
2018-11-20 23:12                                   ` Stefan Monnier [this message]
2018-11-21  7:41                                   ` Michael Albinus
2018-11-21 12:26                                     ` Michael Albinus
2018-11-21 12:44                                     ` Filipp Gunbin
2018-11-21 12:51                                       ` Michael Albinus
2018-11-21 14:44                                     ` John Shahid
2018-11-21 14:52                                       ` Michael Albinus
2018-11-21 14:55                                         ` John Shahid
2018-11-21 15:07                                           ` Michael Albinus
2018-11-20 22:16                           ` Michael Albinus
2018-11-20 22:30                         ` Michael Albinus
2018-11-20 22:54                           ` João Távora
2018-11-21  7:49                             ` Michael Albinus
     [not found]           ` <87ftvwyxh7.fsf@gmx.de>
2018-12-16 15:24             ` Tramp sudoedit method (was: sudo:: method in tramp possible security issue) Michael Albinus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvh8gbwdnx.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=michael.albinus@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.