<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Oops, I'm forgetting two rather important things, sorry.</p>
<p>* The --local flag is only in mosh master, not yet in any release
(though 1.2.6 is coming soon). Available on GitHub near you. If
you don't want to mess with source you can run mosh-client and
mosh-server manually as documented on
<a class="moz-txt-link-rfc2396E" href="https://mosh.mit.edu/"><https://mosh.mit.edu/></a>.<br>
</p>
<p>* mosh-server itself disables coredumps to protect its
cryptographic secrets. Disabling that requires editing source and
rebuilding mosh-server.</p>
<p>regards,</p>
<p> --jh<br>
</p>
<div class="moz-cite-prefix">On 06/07/2016 20:21, Deven Lahoti
wrote:<br>
</div>
<blockquote
cite="mid:CANGLR7tO0DFNErQDY9sgDNjhtPAt6+aFXRVXhoTXe5ynTgB7bg@mail.gmail.com"
type="cite">
<div dir="ltr">mosh --local just gives "unknown option", and I
can't figure out how to enable coredumps for mosh-server -
coredumps work for everything else, so I'm not sure why they're
disabled here.<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Jun 7, 2016 at 9:39 AM, John
Hood <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:cgull@glup.org" target="_blank">cgull@glup.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto">
<div>Try running </div>
<div><br>
</div>
<div>strace -ffo trace mosh --local 127.0.0.1</div>
<div><br>
</div>
<div>on that server after enabling coredumps. That's not
exactly the same as normal execution, since it doesn't
use ssh, but it's useful for issues like this one.</div>
<div><br>
</div>
<div>regards,</div>
<div><br>
</div>
<div> --jh</div>
<div>
<div class="h5">
<div><br>
On Jun 7, 2016, at 12:56 AM, Deven Lahoti <<a
moz-do-not-send="true"
href="mailto:deywos@mit.edu" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:deywos@mit.edu">deywos@mit.edu</a></a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<p dir="ltr">Neither strace nor gdb will give me a
backtrace, since they both lose track of it when
it forks, but the failure happens after forking.
For some reason, systemd says that coredumps are
disabled for the process, so I can't get one of
those either. </p>
<div class="gmail_quote">On Jun 7, 2016 00:31,
"Alex Chernyakhovsky" <<a
moz-do-not-send="true"
href="mailto:achernya@mit.edu" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:achernya@mit.edu">achernya@mit.edu</a></a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">Unfortunately, that's
not much to go on. Could you grab the core
file<br>
and get a backtrace? I'm assuming some syscall
(probably malloc?)<br>
failed.<br>
<br>
Sincerely,<br>
-Alex<br>
<br>
On Tue, Jun 7, 2016 at 12:18 AM, Deven Lahoti
<<a moz-do-not-send="true"
href="mailto:deywos@mit.edu" target="_blank">deywos@mit.edu</a>>
wrote:<br>
> I don't think that's the problem, since
it's now giving me:<br>
> mosh-server[21489]: segfault at 0 ip
(null) sp 00007fffffffcbd8<br>
> error 14 in
mosh-server[555555554000+60000]<br>
><br>
> On Mon, Jun 6, 2016 at 11:42 PM, Alex
Chernyakhovsky <<a moz-do-not-send="true"
href="mailto:achernya@mit.edu"
target="_blank">achernya@mit.edu</a>><br>
> wrote:<br>
>><br>
>> I think the offending line is<br>
>><br>
>> Jun 06 22:32:19 <hostname>
kernel: PAX: From 18.X.X.X: execution<br>
>> attempt in: (null), 00000000-00000000
00000000<br>
>> Jun 06 22:32:19 <hostname>
kernel: PAX: terminating task:<br>
>>
/usr/bin/mosh-server(mosh-server):12505,
uid/euid: XXXX/XXXX, PC:<br>
>> (nil), SP: 000003844385a508<br>
>><br>
>> mosh-server needs to fork and exec to
start subprocesses, and your<br>
>> kernel/configuration doesn't consider
mosh-server to be in the<br>
>> whitelist.<br>
>><br>
>> Sincerely,<br>
>> -Alex<br>
>><br>
>><br>
>> On Mon, Jun 6, 2016 at 11:30 PM,
Deven Lahoti <<a moz-do-not-send="true"
href="mailto:deywos@mit.edu" target="_blank">deywos@mit.edu</a>>
wrote:<br>
>> > Hi, when trying to connect to my
machine running Gentoo Hardened on<br>
>> > kernel<br>
>> > 4.4.8, mosh-server fails to
start. Here are the logs (modified to remove<br>
>> > personal info) [<a
moz-do-not-send="true"
href="http://web.mit.edu/deywos/www/mosh.log"
rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="http://web.mit.edu/deywos/www/mosh.log">http://web.mit.edu/deywos/www/mosh.log</a></a>].
I'm not really<br>
>> > sure<br>
>> > what the problem is, and I don't
know much about how mosh works, so I<br>
>> > was<br>
>> > hoping someone here could help
me out.<br>
>> ><br>
>> > Thanks,<br>
>> > Deven<br>
>> ><br>
>> >
_______________________________________________<br>
>> > mosh-users mailing list<br>
>> > <a moz-do-not-send="true"
href="mailto:mosh-users@mit.edu"
target="_blank">mosh-users@mit.edu</a><br>
>> > <a moz-do-not-send="true"
href="http://mailman.mit.edu/mailman/listinfo/mosh-users"
rel="noreferrer" target="_blank">http://mailman.mit.edu/mailman/listinfo/mosh-users</a><br>
>> ><br>
><br>
><br>
</blockquote>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>mosh-users mailing list</span><br>
<span><a moz-do-not-send="true"
href="mailto:mosh-users@mit.edu"
target="_blank">mosh-users@mit.edu</a></span><br>
<span><a moz-do-not-send="true"
href="http://mailman.mit.edu/mailman/listinfo/mosh-users"
target="_blank">http://mailman.mit.edu/mailman/listinfo/mosh-users</a></span><br>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>