Hi all, I tried the above test, and didn't get any password in the output:
1 -> (tramp-read-passwd #<process *tramp/sudo [email protected]*>) 1 <- tramp-read-passwd: !non-local\ exit! Is there a way to try to figure out where tramp is trying to read the password from? I think this may be an OSX-related issue--I'm running OSX, and heard from someone running aquamacs with the same issue. Thanks!! Rishab On Sun, Aug 28, 2016 at 6:21 AM, Michael Albinus <[email protected]> wrote: > "Guha, Rishab" <[email protected]> writes: > > > Hi, > > Hi Rishab, > > > Tramp has been hanging on 'Sending password' for me whenever I try to > > use it. This includes the simplest test case of C-x C-f > > /sudo::/etc/hosts. > > > > After some trial-and-error with my .emacs, it looks like the problem > > occurs if and only if ESS is active. Unfortunately, I haven't been > > able to figure out anything more than that. Debug log output from the > > simplest possible test case, with init.el looking like > > http://pastebin.com/WVq9TTdA, is here: http://pastebin.com/XJp7abc3 > > > > I haven't found any way of replicating this without activating ESS. > > Note that though the message log says that Tramp is sending a > > password, I was never prompted to enter a password--the minibuffer > > proceeded directly to 'Sending password' > > I couldn't reproduce it locally, even after installing ess 20160825.413 > from melpa. Looking at the traces, your password is sent indeed several > times: > > --8<---------------cut here---------------start------------->8--- > 11:30:06.340081 tramp-maybe-open-connection (6) # /bin/sh -i > 11:30:06.344354 tramp-wait-for-regexp (6) # > #$ > 11:30:06.370876 tramp-send-command (6) # exec env SHELL=/bin/sh sudo -u > root -s -H -p P""a""s""s""w""o""r""d"": > 11:30:06.389828 tramp-accept-process-output (10) # *tramp/sudo > [email protected]* run *tramp/sudo [email protected]* > Password: > 11:30:06.480065 tramp-accept-process-output (10) # *tramp/sudo > [email protected]* run *tramp/sudo [email protected]* > > Sorry, try again. > Password: > 11:30:07.481634 tramp-accept-process-output (10) # *tramp/sudo > [email protected]* run *tramp/sudo [email protected]* > > Sorry, try again. > Password: > 11:30:07.773566 tramp-file-name-handler (1) # Interrupt received in > operation (file-exists-p /sudo:[email protected]:/DESCRIPTION) > > Sorry, try again. > Password: > --8<---------------cut here---------------end--------------->8--- > > We must try to find out which password was sent silently. You might set > the following: > > (trace-function-background 'tramp-read-passwd) > > Then you will get a buffer *trace-output* with a content like this: > > --8<---------------cut here---------------start------------->8--- > 1 -> (tramp-read-passwd #<process *tramp/sudo [email protected]*>) > 1 <- tramp-read-passwd: "secret" > --8<---------------cut here---------------end--------------->8--- > > I've used the password "secret" in this case; you might see something > else. DON'T send the output somewhere, but maybe it helps you to see > where the password comes from. > > I've seen also some strange Tramp usage in the ess code, but this might > not be related. We'll investigate if needed. > > > Best, > > > > Rishab > > Best regards, Michael. > -- Rishab Guha Ph.D Student in Business Economics Harvard University
_______________________________________________ Tramp-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/tramp-devel
