Hi Seth,
Thanks for your kind words! I think we have sort of crossed paths
before (I think you know my high-school friend Meryl, and didn't you
write that DeCSS haiku?).
Right now most people probably just use mosh together with screen or
tmux, which works fine. We put the mosh-server PIDs in
Hello all,
Just pushed some changes to Mosh to address two persistent sources of
frustration.
(1) The Mosh authors have waived the GPL-iTunes incompatibility. Mosh
is now portable to iOS without a conflict with the iTunes Usage Rules.
(Not that we _have_ a port yet...)
(2) Mosh now uses the AES
it for branding and around the text describing mosh?
Dean
On 8/13/2012 12:23 AM, Keith Winstein wrote:
Howdy,
I'm the author of Mosh.
mosh.png___
mosh-devel mailing list
mosh-devel@mit.edu
http://mailman.mit.edu/mailman/listinfo/mosh-devel
Hello Michael,
Thanks for the suggestion. I think, honestly, this is not going to
happen any time soon (at least not with us writing the code).
Best regards,
Keith
On Tue, Sep 4, 2012 at 8:11 AM, Michael Albinus michael.albi...@gmx.de wrote:
Hi,
some of you might know, that Emacs is able to
Hi Ed,
You can force mosh to start up outside a UTF-8 charset by editing the
is_utf8_locale() function (in src/util/locale_utils.cc) to always
return true. (Patch attached.)
As you can appreciate, it's a lot easier to maintain a terminal
emulator for _one_ charset than to try to make it agile
on x86, amd64, or another architecture?
-Keith
On Sun, 30 Dec 2012, Axel Beckert wrote:
Hi Keith,
On Sun, Dec 30, 2012 at 12:31:46PM -0500, Keith Winstein wrote:
Thanks for the detailed report. Last reply means that the _server_
is not getting (or at least not acknowledging) packets from
On Mon, 31 Dec 2012, Axel Beckert wrote:
Hi,
On Mon, Dec 31, 2012 at 01:36:56AM -0500, Keith Winstein wrote:
On Mon, Dec 31, 2012 at 12:47 AM, Axel Beckert a...@deuxchevaux.org wrote:
It looks like the data sent from the client is not (correctly)
received on the server side.
Do you think
wanted to let you know we figured this one out.
Thanks again for the report.
Cheers,
Keith
On Mon, Dec 31, 2012 at 11:50 AM, Keith Winstein kei...@mit.edu wrote:
On Mon, 31 Dec 2012, Axel Beckert wrote:
Hi,
On Mon, Dec 31, 2012 at 01:36:56AM -0500, Keith Winstein wrote:
On Mon, Dec 31, 2012
Thanks guys, looks great and thank you for carefully reproducing the
results. I do agree that probably you might need a longer trace to map
the tails of the delay distribution more precisely, although would be
helpful to see the histogram to know what's goin gon.
We'll be happy to link to you
-- Forwarded message --
From: Paul Schreiber paulschrei...@gmail.com
Date: Sat, Mar 30, 2013 at 11:51 PM
Subject: Re: [mosh-devel] mosh 1.2.4 on mac quits with error message
To: Keith Winstein kei...@mit.edu
Hi Keith —
first, an aside. I was unable to configure 1.2.4 from
On Tue, Apr 16, 2013 at 7:44 AM, Jérémie Courrèges-Anglas
j...@wxcvbn.org wrote:
... but please pull from git://git.wxcvbn.org/mosh.git - branch
openbsd-build-fixes - as I don't have a github account.
Merged and pushed to master. Thank you!
-Keith
I just want to clarify: nobody has objected. We used to link with
skalibs on Debian (and included a convenience copy for
MacPorts/Homebrew and other platforms where skalibs aren't packaged),
but ran into trouble when we added our binary hardening flags.
The current status quo (with pselect()) is
Hi Timo,
Sounds reasonable.
-Keith
On Sat, May 11, 2013 at 7:46 AM, Timo J. Rinne t...@iki.fi wrote:
Hi
After more or less carefully going through the code, I've changed my
mind. I think most elegant and straightforward way to implement agent
forwarding is to implement a generic out of
Hi Seth et al.,
I had a chance to test this out. Yes, you can set the ACK_INTERVAL as
high as you want -- it just means Mosh will take longer to recover if
the client's IP address changes out from under it and nothing is being
typed.
Here is a patch that will get you very low bandwidth use, at
d...@opencsw.org
Date: Mon, Jun 17, 2013 at 3:28 PM
Subject: Re: [mosh-users] Mosh package for Solaris
To: Keith Winstein kei...@mit.edu
Hi Keith,
Am 18.04.2013 um 14:28 schrieb Dagobert Michelsen d...@opencsw.org:
Am 12.04.2013 um 14:40 schrieb Dagobert Michelsen:
Am 11.04.2013 um 22:54
Hello Weiwu,
The mosh wrapper script does use ssh, but only to remotely execute a
mosh-server on the server (running as the user) and collect the
session key it prints out.
Others have replaced SSH with HTTPS (the user authenticates with a
password or X.509 certificates and then gets the secret
Hello Bonz,
Unfortunately we don't support these cases where a server's IP address may
need to change during a connection, at least not yet.
Of course you can give mosh an IP address to connect to (instead of a
domain name) and it will connect to whatever you ask, but it can't handle
the
Hello Lawrence,
Unfortunately not. (See previous reply.) But you can follow this issue at
https://github.com/keithw/mosh/issues/210
The main blocker for this is that we need an asynchronous DNS resolver in
mosh-client to be able to discover if the server's IP has changed in the
middle of the
Hello Edward,
I'm not quite sure I follow. Do you want an arbitrary tunnel of a
byte-stream, or do you just want to be able to get a persistent, roamable
shell login to a machine that's behind a firewall?
Mosh doesn't support arbitrary tunnels (yet!), but if you just need a shell
login from a
be
appreciated.
Ed
On Sat, Aug 10, 2013 at 7:58 PM, Keith Winstein kei...@mit.edu wrote:
Hello Edward,
I'm not quite sure I follow. Do you want an arbitrary tunnel of a
byte-stream, or do you just want to be able to get a persistent, roamable
shell login to a machine that's behind a firewall?
Mosh
Hello Hannes,
There's no fundamental reason that Mosh couldn't support an
application-specific local echo model. Look
in src/frontend/terminaloverlay.cc (
https://github.com/keithw/mosh/blob/master/src/frontend/terminaloverlay.cc)
for the current code.
You *might* be better off just writing your
before you mosh (e.g. LC_TIME= mosh servername).
(2) Build the client's locale on the server.
-Keith
On Tue, Dec 10, 2013 at 2:23 PM, Goffredo Baroncelli kreij...@inwind.itwrote:
Hi Keith,
On 2013-12-10 20:11, Keith Winstein wrote:
Goffredo,
Unfortunately this is a general problem
Thanks, Tim. Our tentative thoughts on this are to create slosh as a
separate program that will fork a lightweight Linux container (with
unshare()) in a new network namespace with a TUN device, and gracefully
proxy all the network connections initiated from within the container to
the server,
, Dec 30, 2013 at 8:36 PM, Jim Cheetham jim.cheet...@otago.ac.nz
wrote:
(sorry about the quoting, webmail isn't quite so flexible as my normal MTA)
--
*From:* winst...@gmail.com [winst...@gmail.com] on behalf of Keith
Winstein [kei...@mit.edu]
*Sent:* Friday, 27
On Wed, Jan 1, 2014 at 11:06 PM, Jim Cheetham jim.cheet...@otago.ac.nz wrote:
Currently I'm on at 13:20 WST (Perth, Australia) on Thursday 9 Jan. I don't
know your timezone, but that'll be between 9pm and midnight on *Wednesday*
for the US
Thanks for reporting this. Do you know what the correct Cygwin link should
be?
Thank you,
Keith
On Thu, Feb 27, 2014 at 11:57 AM, P. Blissenbach pu...@web.de wrote:
Hi,
I am new to this list, and only popping in to tell that the cygwin part on
the website
http://mosh.mit.edu/#getting
has
Hello Jonathan,
Happy to hear Mosh is helpful! Re: an API, you might take a look at
how the mosh-client program is implemented
(https://github.com/keithw/mosh/blob/master/src/frontend/mosh-client.cc).
It instantiates an STMClient object, calls the init() method, and then
the main() method, which
Hello Max,
The s is there already -- perhaps it is just getting wrapped to the next
line based on your browser width?
Best regards,
Keith
On Tue, Nov 25, 2014 at 2:17 AM, Max.Goncharov g...@gmax.at wrote:
Hi
during the install instructions for Ubuntu the “s” missing in
sudo apt-get
Hello Alex,
I think it's unlikely that the SSP implementation will be directly
helpful to another project, but it may be worth a look.
https://github.com/keithw/mosh/tree/master/src/network
https://mosh.mit.edu/mosh-paper-draft.pdf (has more information than
the published version)
delays
and slow visual feedback. Hard to correctly position cursor.
-- Robert
On 1657-0700 Tue 21 Apr, Keith Winstein wrote in part:
Can you give a try to the lowbandwidth branch with the
--predict=experimental command-line option? You might find that
to be more to your liking.
We
Good question!
We have a (small) crypto-focused test suite that gets run from make check
and as part of building the Debian/Ubuntu packages (and possibly
Fedora/EPEL?), but it doesn't test protocol interoperability among versions
of mosh that were compiled differently.
It would be great to do a
Hello Hayden and Simon,
Happy to help if we can. There may be others on the list who are more
familiar with some of these kinds of concerns than me -- hope they
will weigh in. Why don't you let us bat around the response for a bit
before we commit to it. My instincts are that if you really want
Thanks, Romain. I think at this rate, let's just revisit this once 1.2.5 is
released, uploaded to the main archive, and hits testing.
Cheers,
Keith
On Sat, Jun 27, 2015 at 5:26 AM, Romain Francoise rfranco...@debian.org
wrote:
Hi Keith,
On Fri, Jun 26, 2015 at 11:17:27PM -0400, Keith
Hello Mosh users and developers,
On the heels of the successful 1.2.5 release, just an FYI that the
Mosh repo has moved to: https://github.com/mobile-shell/mosh
This has allowed us to turn on Travis CI for continuous
integration/testing (without giving Travis full access to my GitHub
account).
FYI: Mosh 1.2.5 was just accepted into jessie-backports.
On Sun, Aug 9, 2015 at 11:15 AM, Keith Winstein kei...@mit.edu wrote:
Hello Jonathan,
I believe it's already been uploaded to the NEW queue for
jessie-backports and will be there once it gets reviewed.
Best regards,
Keith
On Sun
without PTY. (Keith Winstein)
* network.cc: Properly close old fd on Socket assignment
operator. (Thanks to Igor Bukanov)
* mosh-server: Allow startup with zero-window-size PTY.
(Igor Bukanov)
* AddrInfo: Fix error message generation when node == NULL
Thanks for the report. Point taken. We'll take a pull request!
Best,
Keith
On Sep 5, 2015 12:20 PM, "Andrew C Aitchison"
wrote:
>
> Thanks for continuing work on mosh;
> I particularly appreciate the XTerm mouse mode.
>
> I can't see the point in making a release for
Hello Kris,
Could you point me to the instructions you're following?
The typical use of Mosh just involves typing "mosh " on the
client, or typing the name of server into the Mosh Chrome app. It doesn't
involve running anything on the server (other than installing mosh in the
first place).
For
Short answer is, yes, source code is basically the definitive reference
(and mosh-paper.pdf / mosh-paper-draft.pdf). The state-synchronized objects
that define the Mosh protocol are in
https://github.com/mobile-shell/mosh/tree/master/src/statesync
Best regards,
Keith
On Mon, Jan 4, 2016 at 2:08
Hello Dinesh,
The mosh paper used the term-save and term-replay utilities (
https://github.com/keithw/stm-data). These can record and replay the
timestamps of user keyboard input and an application response.
You might also enjoy reading some of the other student reproductions of the
mosh
Thanks for the report! Is this a regression -- did 1.2.5 or 1.2.4 work
out-of-the-box on OpenBSD?
Thanks
Keith
On May 31, 2016 3:45 AM, "Peter Jeremy" <pe...@rulingia.com> wrote:
> Hi Keith,
>
> On 2016-May-30 00:33:27 -0700, Keith Winstein <kei...@mit.edu>
rg
> Subject: Fw: Re: [mosh-devel] Mosh 1.2.6 release candidate available for
> testing]
> User-Agent: Mutt/1.6.1 (2016-04-27)
>
> Sorry, I should have copied you on the attached.
>
> --
> Peter Jeremy
>
> Date: Tue, 31 May 2016 20:45:02 +1000
> From: Peter Jeremy <
Thanks, Carlos, it will be very interesting to read through the code. I'm
trying to make sure I understand the licensing implications of what you're
planning to release on the App Store. Could you please describe:
(a) Which parts of the overall Blink application are you planning to
release as
ain function. You can see that in the code for Blink in
> Sessions/Session.m and Sessions/MoshSession.m. And then MoshSession for
> example calls SSHSession, etc... So yes, I tried to replicate the basis of
> a pipes and process system so that connecting other tools would be easy too
> (and
Kaseorg, Keith
Winstein)
* Workaround a glibc-2.22 issue causing segfaults on
Debian Sid. (John Hood with help from many others)
* Prefer c++ to g++, for systems like FreeBSD where
g++ is not usable. (John Hood
Thanks for this -- the website is maintained at
https://github.com/mobile-shell/moshweb . If you can submit a pull
request on GitHub that adds OpenIndiana, I expect we can take it. It
could go right next to OpenCSW.
Cheers,
Keith
On Tue, Aug 16, 2016 at 2:54 AM, Predrag Zečević - Unix Systems
Hello Jonathon,
I investigated and it's probably my fault -- I'm compiling and statically
linking on an Ubuntu system that expects it
in /usr/lib/x86_64-linux-gnu/utempter/utempter, and athena.dialup has it
in /usr/lib/utempter/utempter.
Could you please install libutempter-dev on the dialups?
> Hi Keith,
>
> libutempter-dev is now installed on test.dialup.mit.edu. It should hit
> the production dialups over the course of next week, but doing your
> build on test.dialup.mit.edu should be fine. thanks for the help.
>
> Jonathon
>
>
>
> Keith
Hello Mosh developers,
Historically, mosh-devel has been our public contact address (and gets a
lot of spam), while mosh-users has been restricted to "members-only"
posting.
A lot of people want to be on mosh-devel but don't like spam, so I just
changed mosh-devel to "Hold" non-member posts for
is for you to just submit a PR
with a proposed snapcraft.yaml (and changes to .travis.yml if appropriate)
and we can all try it out.
Cheers,
Keith
On Fri, Jan 13, 2017 at 7:56 AM, Leo Arias <y...@elopio.net> wrote:
> On Thu, Jan 12, 2017 at 11:59:53PM -0800, Keith Winstein wrote:
&g
Hello Leo,
Thanks for getting in touch, and thanks for your kind words about mosh!
Right now we have a Debian package, which we maintain in our own source
tree, and which we upload to Debian every time there's a new release. That
flows into Ubuntu as part of the normal release schedule. For
shell/mosh/issues. The developers can
also be found on IRC at .
The full change log for this release:
===
* New features:
* Change website URLs from http://mosh.mit.edu to https://mosh.org.
(Keith Winstein)
* Add --no-ssh-pty option for Dropbear compatibility and other issues.
* Switch t
Hood)
* Work around JuiceSSH rendering bug. (John Hood)
* Do not move cursor for SCROLL UP and SCROLL DOWN--
fixes an issue with tmux 2.4. (John Hood)
===
Best regards on behalf of the Mosh team,
Keith Winstein
-BEGIN PGP SIGNATURE-
iQIcBAEBCAAGBQJZc8lFAAoJECC3KDr
s, we are subscribed to the mosh-devel
> channel and happy with answering questions related to our implementation.
> Btw, we have UserVoice integrated into our apps so we see most of the
> requests right there.
>
> On 7 August 2017 at 7:48:41 PM, Keith Winstein (kei...@cs.stanford.edu)
&g
org so
> end users have more options to pick up from.
>
> On 4 May 2017 at 4:46:24 PM, Keith Winstein (kei...@cs.stanford.edu)
> wrote:
>
> Hello Roman,
>
> Okay, but if we can't see your code, we don't have a good way to start to
> know if your implementation is "
Thanks, Jeremie! Do these tests work with 1.3.0? (And if so, are you able
to bisect this for us?)
Cheers,
Keith
On Fri, May 26, 2017 at 4:55 PM, Jeremie Courreges-Anglas
wrote:
>
> On OpenBSD-current (amd64), make check reports two failures. Log files
> attached.
>
>
>
> --
>
Thanks for letting us know!
(1) Could you please describe the process you used to develop a clean-room
implementation of the Mosh protocol? Did you write up a protocol
specification based on the Mosh source code, and then have somebody else
implement the spec? If so, would you be willing to share
gt; On 2 May 2017 at 6:40:20 AM, Keith Winstein (kei...@cs.stanford.edu)
> wrote:
>
> Thanks for letting us know!
>
> (1) Could you please describe the process you used to develop a clean-room
> implementation of the Mosh protocol? Did you write up a protocol
> specificatio
Hello Daniel,
The issue is basically the same since the original pull request in 2013 --
whatever change we make to the Mosh protocol to support ssh-agent
forwarding is one we have to live with forever, and the limitations of the
Mosh protocol make us not want to commit ourselves to these
Hello,
It is our understanding that we have complied with the requirements
(including notification) for Mosh to have an ECCN of 5D002.
Sincerely,
Keith Winstein
On Tue, Sep 12, 2017 at 3:25 PM, Kumar, Ashish /CS <ashish.ku...@em-msph.com
> wrote:
> Hi Keith,
>
>
>
>
>
Hello Dan,
For idea #1, please check out the MOSH_SERVER_NETWORK_TMOUT
and MOSH_SERVER_SIGNAL_TMOUT environment variables. These are documented in
the mosh-server(1) man page. The feature was released in Mosh 1.2.6 (August
2016) so your mosh-server needs to be at least that new.
For idea #2, we
On Thu, Nov 9, 2017 at 6:43 AM, Daniel Roethlisberger wrote:
> Specifically, I am not interested in manually approving agent
> requests. The ratio of hassle to mitigated risk is unreasonable
> in my opinion. It addresses a narrow category of attacks while
> not helping against
, the
underlying mechanism, or the best way to make this smooth for Mosh users.
Thanks all,
the Guardian Agent developers (Dima Kogan, Henri Stern, David Mazieres,
Keith Winstein)
___
mosh-devel mailing list
mosh-devel@mit.edu
http://mailman.mit.edu/mailman
>> on the client side, just like it does for the mouse reporting mode. I would
>> add a resource-values member to Terminal::DrawState for the xterm settings,
>> and then watch for changes in Display::new_frame() sending the correct
>> sequence to the user's terminal there. I'm
Hi Erik,
I'm a little confused why you want this in general, and it may relate to a
design weakness in Mosh, which is that it basically assumes that the client
terminal acts like an xterm. By default, an xterm sends Ctrl-H (0x08) when
the user types "Ctrl-Backspace" (and VTE seems to also follow
, but maybe something like a MAC
> address for example?
>
> Thanks,
> Tom
>
> On 27 June 2018 at 04:50, Keith Winstein wrote:
> > Hi Thomas,
> >
> > Glad you could provoke a very interesting discussion! But I'm still
> confused
> > -- how is "stick
Hi Thomas,
Glad you could provoke a very interesting discussion! But I'm still
confused -- how is "sticky IP-based routing" going to work after the client
roams to a new IP address (or to a new UDP source port)? When your system
seems an incoming UDP datagram from a previously unseen source
uld be great to get Mosh working as well.
>
> So just another friendly reminder - I'm having to tell people to
> compile Mosh themselves to get true colour support.
>
> On 8 July 2018 at 11:56, Keith Winstein wrote:
> > Hi Thomas,
> >
> > Hmm, let me try to see if I can
I don't think Jim's message was quite a response to my earlier one -- if
you do use a proxy/NAT as I described, you do not need to use a bastion
host and you don't need the proxy to be aware of the internals of the SSP
protocol, or worry about keys, or decrypt anything. It can be pretty
oblivious
>
> The only thing I don't understand is why the outgoing UDP datagram has
> to rewrite the container's source IP. Isn't the original MOSH CONNECT
> IP:port the canonical reference?
>
> On 1 July 2018 at 12:54, Keith Winstein wrote:
> > How about a semi-smart (but mos
oposed registrations for mosh.cn, mosh.com.cn,
mosh.net.cn, or mosh.org.cn.
We have no affiliation or connection with Kaikun Ltd.
Sincerely,
Keith Winstein
Mosh project
From: "Charles Liu<char...@chinaregistry.cn>" <
> servi...@chinaregistry-jb.org.cn>
> To: <mosh-dev
Hello -- thanks for your kind words! It is probably possible to adapt
mosh-server to do what you propose here (basically allowing the server to
roam instead of the client), but we have not done this or shipped it. I
think most people probably do just use an auto-roaming VPN (e.g. OpenVPN or
Hello -- I think the main issue here is that you are using ISO 2022 shift
sequences to switch to the "alternate character set" to draw those lines on
the screen. Mosh follows the practice of some (but not most) UTF-8 (ISO
10646) ANSI terminal emulators in refusing to interpret the "locking
shifts"
Hello Adrian,
Mosh's use of utempter is pretty orthodox -- we call utempter_add_record()
and utempter_remove_record() in mosh-server.cc and that's about it. You can
see all the calls here:
https://github.com/mobile-shell/mosh/blob/master/src/frontend/mosh-server.cc
You might try writing a very
Hello Yevgeny,
Thanks for getting in touch. We were included in the oss-fuzz repository,
but I'm not sure anybody ever actually did the work of integrating Mosh or
fuzzing it. (People have separately fuzzed the terminal emulator and found
some overcautious assertions that we ended up removing;
>
>AsyncSSH (maintained by Ron Frederick)
>libassh (maintained by Alexandre Becoulet)
>Mobile SSH (aka Mosh via mosh.org and )
> (original paper authors
>Keith Winstein ,
>Hari Balakrishnan )
>PuTTY (main
Thanks! Would you mind sending us a pull request to the moshweb repo?
Best regards,
Keith
On Wed, Apr 7, 2021 at 1:27 PM Mark Urban wrote:
> Hi,
>
> Just wanted to suggest that you should consider updating the "Getting
> Mosh" section of your web site. Termux is no longer being updated on the
Hello,
Thanks for your email. As I wrote when you came on the IRC channel, we
don't think this behavior is a bug. The reason Mosh requires a UTF-8 native
locale has to do with terminal emulation. ANSI-style terminals operate on
an underlying state machine (https://vt100.net/emu/dec_ansi_parser).
Hi -- I am the original creator of Mosh and use it every day. I don't think
the project is defunct -- we are very proud of our essentially perfect
decade-long track record on security and feel like that record gets longer
every day as hundreds of thousands of people, or maybe millions, continue
to
netsarang.com
>
>
> *FACEBOOK: *http://facebook.com/netsarang
> <https://tracking.cirrusinsight.com/25b7bb93-8a74-4813-a129-bd31a9e05784/facebook-com-netsarang>
> | *TWITTER**: *http://twitter.com/netsarang
> <https://tracking.cirrusinsight.com/25b7bb93-8a74-4813-a129-bd3
Hello,
Thank you for your inquiry. Mosh is free software, licensed under the GNU
GPL. The requirements would be similar to those of Linux, Git, GCC, Emacs,
OpenJDK, Blender, GIMP, VLC, Wordpress, etc. You are welcome to
redistribute Mosh under the terms of the license -- you may want to consult
for how you'd all like to get this done. (And if you want
me involved for an occasional call, let me know.) Welcome again!
Sincerely,
Keith
> El jue, 27 ene 2022 a la(s) 03:09, Keith Winstein (kei...@mit.edu)
> escribió:
>
>> Hello Wolfgang,
>>
>> Welcome, and thanks f
Hello Wolfgang,
Welcome, and thanks for writing! We're happy to have you involved. Let me
loop in Alex (our RPM package maintainer) who is willing to help get this
off the ground, as well as Quentin Smith (one of the Mosh authors) and Ben
Barenblat, who are also interested in helping make this
Mosh." It is a registered trademark referring to our software.
Please let us know when this is done.
-Keith
On Wed, Aug 30, 2017 at 6:12 PM Roman Kudiyarov wrote:
> Hi Keith,
>
>
>
> On 9 August 2017 at 11:51:44 AM, Keith Winstein (kei...@cs.stanford.edu)
> wrote:
>
Great, and thank you -- this is awesome!
(1) Should we update the ChangeLog file for the source release? It looks
like you (and achin?) already wrote text for it.
(2) Should I make the final 1.4.0 debian/changelog entry (probably
including the same bullet points as we'll put into ChangeLog) or do
ast-minute friction here.
-Keith
On Thu, Oct 27, 2022 at 7:14 PM Benjamin Barenblat
wrote:
> On Wednesday, October 26, 2022, at 8:33 PM -0700, Keith Winstein wrote:
> > (1) Should we update the ChangeLog file for the source release? It looks
> > like you (and achin?) already wrote text
rth
> rev'ing the version over the changelog? But I'd definitely rev the version
> if we think we need to include it.
>
> Sincerely,
> -Alex
>
> On Thu, Oct 27, 2022, 10:42 PM Keith Winstein
> wrote:
>
>> Thanks Ben. I didn't realize we had pushed an unsigned tag alr
the remote command fails, pause briefly (John Hood)
Bug fixes:
- -ignore unknown renditions (Keith Winstein)
- -Overlays were getting set to the wrong colors (John Hood)
- -Fix issue with incorrect true-color background erase colors (John Hood)
- -Use HAVE_UTEMPTER instead
Thanks for the report -- I think there's just an issue today with our web
host at MIT. I've sent email.
Sincerely,
Keith
On Wed, Apr 17, 2024 at 9:58 AM Andrew C Aitchison
wrote:
>
> I see that the domain mosh.org is no longer in "the DNS"
> (although whois still works).
>
> I would be sorry
s://mosh.org website automatically.
On Wed, Apr 17, 2024 at 10:20 AM Keith Winstein
wrote:
> Hi folks,
>
> Overnight, the mosh_project locker seems to have lost its associations on
> scripts.mit.edu. We're getting "404 Not Found" from http://mosh.mit.edu
> is (and http:/
The site is back online. Thank you for the report!
On Wed, Apr 17, 2024 at 10:22 AM Keith Winstein wrote:
> Thanks for the report -- I think there's just an issue today with our web
> host at MIT. I've sent email.
>
> Sincerely,
> Keith
>
> On Wed, Apr 17, 2024 at 9:58
Hi folks,
Overnight, the mosh_project locker seems to have lost its associations on
scripts.mit.edu. We're getting "404 Not Found" from http://mosh.mit.edu is
(and http://mosh.org, which is served through Cloudflare), and
https://pony.scripts.mit.edu:444/index?locker=mosh_project says "The
92 matches
Mail list logo