Re: [mosh-devel] Mosh website giving 404 not found

Update: I moved hosting for mosh.org over to GitHub Pages to get the site back online. mosh.mit.edu is still giving a 404 for unclear reasons. :-/ Mosh folks: the "moshweb" repo is now an alias to the " mosh-project.github.io" repo, and pushing there will go live on the https://mosh.org website au

[mosh-devel] Mosh website giving 404 not found

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 'mosh_p

Re: [mosh-devel] Mosh and 2FA

; https://www.youtube.com/watch?v=D9RGX6QFm5E > Dave Täht CSO, LibreQos > > ___ > mosh-devel mailing list > mosh-devel@mit.edu > https://mailman.mit.edu/mailman/listinfo/mosh-devel > ___ mosh-devel mailing list mosh-devel@mit.edu https://mailman.mit.edu/mailman/listinfo/mosh-devel

Re: [mosh-devel] Mosh and 2FA

mosh leverages ssh to initiate the connection, which can be 2FA. However the advantage to mosh is its persistence, so adding 2FA to it periodically would make sense. On Mon, Feb 5, 2024 at 8:15 AM Rafael Ribeiro dos Santos wrote: > > Hello, > > My name is Rafael and I currently work for Universi

[mosh-devel] Mosh and 2FA

Hello, My name is Rafael and I currently work for University of Bergen in Norway, supporting users of our HPC systems. An user recently created a ticket asking to have Mosh available as his connection is not very reliable and I escalated to our internal team, which asked me if Mosh would work

[mosh-devel] mosh 1.4.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello Mosh users and developers, The Mosh team is pleased to announce the long-awaited 1.4.0 release. This is our first release in five years and marks ten years since Mosh 1.0. The source code is at: https://mosh.org/mosh-1.4.0.tar.gz (SHA-256: 87

Re: [mosh-devel] Mosh 1.4.0 is available on GitHub

On Fri, Oct 28 2022, "Wolfgang E. Sanyer" wrote: > My opinion (fwiw): i agree with Alex that the tag shouldn't be unpushed. > Last time this happened caused some headaches for me personally so maybe > I'm biased 😅 Downstream speaking : I would strongly suggest that you don't overwrite published t

Re: [mosh-devel] Mosh 1.4.0 is available on GitHub

) In the past the release announcement email named/credited the >>>> > "primary >>>> > developer and release manager" -- what do you want it to say this time? >>>> > (I.e who should be credited and in what order?) >>>> >>>&

Re: [mosh-devel] Mosh 1.4.0 is available on GitHub

cgull, Anders, Alex, and I all contributed >>> over 100 lines of diff to Mosh since the last release. It’s an arbitrary >>> cutoff, but it seems as good as any to me. I think cgull should probably >>> go first on the list, since they were making active contributions until >>> 2021. >>> >>> As for release manager, I think that’s Alex. He was definitely the >>> forcing function here. :) >>> >> ___ > mosh-devel mailing list > mosh-devel@mit.edu > https://mailman.mit.edu/mailman/listinfo/mosh-devel > ___ mosh-devel mailing list mosh-devel@mit.edu https://mailman.mit.edu/mailman/listinfo/mosh-devel

Re: [mosh-devel] Mosh 1.4.0 is available on GitHub

I don't think we should un-push the tag. I also don't think it's worth 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

Re: [mosh-devel] Mosh 1.4.0 is available on GitHub

Hmm, what's the best way to push the signed tag? In the past we've done an "a" for last-minute release issues, so we could rev to mosh-1.4.0a... On Thu, Oct 27, 2022 at 7:47 PM Alex Chernyakhovsky wrote: > I don't think we should un-push the tag. I also don't think it's worth > rev'ing the versi

Re: [mosh-devel] Mosh 1.4.0 is available on GitHub

Thanks Ben. I didn't realize we had pushed an unsigned tag already. I guess... my tentative thought would be let's un-push the "mosh-1.4.0" tag since I'd rather maintain past practice and have that be a signed tag anyway. Unless you think this will cause lots of problems (but I don't think it will)

Re: [mosh-devel] Mosh 1.4.0 is available on GitHub

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 for it. I completely forgot about the changelog. Yes, we should update that. What do you think – should we

Re: [mosh-devel] Mosh 1.4.0 is available on GitHub

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

Re: [mosh-devel] mosh bug without UTF-8

plications! Never for a remote connection... > > Cannot be SUCH hard, or? > > P.S. And no, ssh or telnet or rlogin or rsh never ever had a problem with > this configuration, not on one system based on IRIX, HP-UX, True64, SunOS, > Solaris, AIX or Linux from most different vendors.

[mosh-devel] mosh bug without UTF-8

Hello, together Is the any chance, that you will fix this bug with the error message "mosh-client needs a UTF-8 native locale to run."? All Unix like systems I know and use since over 30 years are always set to POSIX / C! And all of them simply do not work with mosh, which is a massive shame. m

[mosh-devel] Mosh keeps disconnecting in my MBP 2019

To whom it may concern: Hi, I'm a heavy user of mosh + iTerm2 + tmux in my working environment. The combination worked great in the past, however a month ago I got a new laptop (MacBookPro 2019, installed macOS Big Sur 11.4) from my company and the pre-installed mosh (version 1.3.2) on this lap

Re: [mosh-devel] Mosh `make check` failure

This is the same as https://github.com/mobile-shell/mosh/issues/935: If you’re using a Perl version before 5.14, you need the Socket::GetAddrInfo module. Anders ___ mosh-devel mailing list mosh-devel@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh

[mosh-devel] Mosh `make check` failure

Hello, I just built mosh 1.3.2. When I ran make check it failed and said to send a bug report to this email address. I’ve attached test-suite.log. Here’s some version information that might be relevant: $ uname -a Linux finagle.wot.eecs.northwestern.edu 2.6.32-754.28.1.el6.x86_64 #1 SMP Fri Jan 3

Re: [mosh-devel] Mosh supported on Redhat?

Great, thanks! On Fri, Mar 27, 2020 at 11:33 AM Alex Chernyakhovsky wrote: > *Message sent from a system outside of UConn.* > > > Hi Joseph, > > The packages for mosh on RedHat are included in EPEL: > https://fedoraproject.org/wiki/EPEL, available for RHEL/CentOS 6, 7, > and 8. > > Sincerely, >

Re: [mosh-devel] Mosh supported on Redhat?

nn.edu > University of Connecticut, > Mechanical Engineering M.S., 2020 > > ___ > mosh-devel mailing list > mosh-devel@mit.edu > http://mailman.mit.edu/mailman/listinfo/mosh-devel ___ mosh-devel ma

[mosh-devel] Mosh supported on Redhat?

Hello, I am need to work remotely on a Redhat Linux machine and I am looking for a more robust method than ssh to connect remotely. I could not find an installation on your website that supports Red Hat Linux. Is this not yet supported? Thanks! -- Best Regards, *Joseph N. Squeo* joseph.sq...@

[mosh-devel] Mosh over mqtt

Hello I have a quick question. How hard would it be to implement mosh when data is transmitted with only mqtt messages? Tomas Mažvila ___ mosh-devel mailing list mosh-devel@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh-devel

Re: [mosh-devel] mosh continuous fuzzing improvement suggestion

nuous fuzzing for projects like systemd, radare, apache. >>> >>> You can read about systemd-fuzzit case study here >>> <https://fuzzit.dev/2019/06/20/continuous-fuzzing-systemd-case-study/> where >>> they use our platform in addition to OSS-fuzz. >>> >>> Also, will be happy to discuss fuzzing in general and share ideas. >>> >>> Looking forward to hearing from you, >>> >>> Yevgeny Pats, >>> Founder & CEO, Fuzzit >>> >> ___ > mosh-devel mailing list > mosh-devel@mit.edu > http://mailman.mit.edu/mailman/listinfo/mosh-devel > ___ mosh-devel mailing list mosh-devel@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh-devel

Re: [mosh-devel] mosh continuous fuzzing improvement suggestion

Hi Keith, Thanks for the detailed response. Just to make sure I understood correctly, there are two main steps for continuous fuzzing integration for Mosh: 1) Writing the appropriate libFuzzer targets. 2) Integrating with Continuous Fuzzing platform that will fuzz those targets in parallel to th

Re: [mosh-devel] mosh continuous fuzzing improvement suggestion

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; see

Re: [mosh-devel] Mosh-based infrastructure for remote management of remote devices

evard Ornano > > 93200 Saint-Denis > > Tél : +33 1 83 65 40 49 (poste direct) > > Tél : +33 1 83 65 40 40 (standard) > > Portable : +33 6 75 68 32 35 > > Site internet : www.bruitparif.fr > > > ___ > mosh-devel mailing list > mosh-devel@mit.edu > http://mailman.mit.edu/mailman/listinfo/mosh-devel > ___ mosh-devel mailing list mosh-devel@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh-devel

[mosh-devel] Mosh-based infrastructure for remote management of remote devices

Hi to all Discovered mosh today (better now than never...) and very impressed ! Sure I will love it, as I'm sure also that internet would have been better if built over UDP than TCP ;-) I have a question for you... I deploy many devices (raspberry pi family) that are connected to the internet

Re: [mosh-devel] Mosh on Kuberbnetes

ditional "bastion host" in > the middle, use mosh to connect to that, and from there make inbound ssh > connections to your service hosts (because you can get away with ssh on an > internal "reliable" network, and because you're using TCP for this, you can > go through a load balancer if required). > > > > -jim > > > > -- > > Jim Cheetham, Information Security, University of Otago, Dunedin, N.Z. > > ✉ jim.cheet...@otago.ac.nz☏ +64 3 470 4670☏ m +64 21 279 4670 > > ⚷ OpenPGP: B50F BE3B D49B 3A8A 9CC3 8966 9374 82CD C982 0605 > > ___ > mosh-devel mailing list > mosh-devel@mit.edu > http://mailman.mit.edu/mailman/listinfo/mosh-devel > ___ mosh-devel mailing list mosh-devel@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh-devel

Re: [mosh-devel] Mosh on Kuberbnetes

> >> records > >> >> >> the SSH user still has to have VerifyHostKeyDNS enabled, which as > I > >> >> >> understand most people don't. And then on top of that my DNS > >> >> >> provider > >> >> >> (DNSSimple) automatically rotate the keys

Re: [mosh-devel] Mosh on Kuberbnetes

Thanks Jim, That really clears things up for me. So but you're saying that Keith's idea of having the outgoing datagram's source IP remapped is not possible? I totally agree about the traditional approach of the "bastion host", it's basically like having SSH act as the "load balancer" - as I'll

Re: [mosh-devel] Mosh on Kuberbnetes

Excerpts from Thomas Buckley-Houston's message of July 13, 2018 3:58 pm: > So > because UDP is a connectionless protocol, every datagram has to > contain the source IP in order for the receiver to send responses? Every packet does have the source IP address in it, but not because it's a UDP packe

Re: [mosh-devel] Mosh on Kuberbnetes

> >> the DNSSEC records. Is it all worth it do you think? >> >> >> >> >> >> On 24 June 2018 at 13:36, Anders Kaseorg wrote: >> >> >> > You may have a misunderstanding about how a Mosh

Re: [mosh-devel] Mosh on Kuberbnetes

>> > processes > >> >> > exchange UDP packets encrypted with the shared key; communication > is > >> >> > successful if the packets can be decrypted. > >> >> > > >> >> >

Re: [mosh-devel] Mosh on Kuberbnetes

sh-server is >> >> > launched >> >> > on a new port for each Mosh session (it is not a daemon like sshd). >> >> > >> >> > The easiest way to put Mosh servers behind a load balancer is with >> >> > round-robin DNS where a single hostna

Re: [mosh-devel] Mosh on Kuberbnetes

the SSH connection and > >> > the > >> > UDP packets, because that’s needed for MIT’s athena.dialup.mit.edu > pool. > >> > > >> > If that’s not an option and you really need all connections to go > >> > through > >> > a sing

Re: [mosh-devel] Mosh on Kuberbnetes

u pool. >> > >> > If that’s not an option and you really need all connections to go >> > through >> > a single load balancer address, you could try wrapping mosh-server in a >> > script that passes different disjoint port ranges (-p) on different >>

Re: [mosh-devel] Mosh on Kuberbnetes

the corresponding backends from > > the load balancer. > > > > Unrelatedly, brow.sh doesn’t resolve with DNSSEC-enabled resolvers like > > 1.1.1.1 or 8.8.8.8, seemingly due to some problem with the DS records set > > with the registrar: https://dnssec-debugger.verisign

Re: [mosh-devel] Mosh on Kuberbnetes

On Mon, Jun 25, 2018 at 06:10:58PM +0800, Thomas Buckley-Houston wrote: > Thanks so much for the clarification. > > > UDP is connectionless > > That's the key here. So I have no choice but to use sticky IP-based > routing. Round-robin DNS isn't an option I don't think, because I hope > one day to

Re: [mosh-devel] Mosh on Kuberbnetes

Thanks so much for the clarification. > UDP is connectionless That's the key here. So I have no choice but to use sticky IP-based routing. Round-robin DNS isn't an option I don't think, because I hope one day to be able to scale to thousands of servers. And thanks so much for the heads up about

Re: [mosh-devel] Mosh on Kuberbnetes

You may have a misunderstanding about how a Mosh session is set up. The mosh script launches a mosh-server on the remote system via SSH; mosh-server picks a port number and a random encryption key, and writes them to stdout, where they go back over SSH to the mosh script; then the mosh script

[mosh-devel] Mosh on Kuberbnetes

Hello Mosh Developers, This is my first post to the list. Thanks for the introduction Keith. I'm the author of Texttop (soon to be re-released as Browsh): https://github.com/tombh/texttop It is a fully-modern text-based browser. You can actually SSH into a demo: `ssh brow.sh` (no auth needed). T

Re: [mosh-devel] mosh CN domain and keyword

Hello, Thank you for reaching out to us. Mosh is an open-source software project. We have the domain name "mosh.org", and our website is hosted at https://mosh.org. We have a pending trademark registration for "Mosh" in the United States. We were not aware of these proposed registrations for mosh

Re: [mosh-devel] [mosh-users] How to properly kill old mosh-server connections

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 c

[mosh-devel] mosh 1.3.2 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Mosh users and developers, mosh 1.3.2 has been released. This is primarily a maintenance release. (We skipped version 1.3.1 because of a glitch in Debian packaging. The previous release was mosh 1.3.0.) The source code is at: https://mosh.org

Re: [mosh-devel] [mosh-users] Mosh 1.3.1 release candidate 2 available for testing

ite summary for mosh 1.3.1-rc2 > > # TOTAL: 29 > # PASS: 27 > # SKIP: 0 > # XFAIL: 2 > # FAIL: 0 > # XPASS: 0 > # ERROR: 0 > ==== > > > > > ___

Re: [mosh-devel] [mosh-users] Mosh 1.3.1 release candidate 2 available for testing

john hood writes: > On 5/28/17 11:15 AM, Jeremie Courreges-Anglas wrote: >> ack, let me know if you need more data. >> > Nicholas Marriott and I seem to have found a solution involving small > changes to both tmux and mosh's tests. I'm waiting for his changes to > appear in OpenBSD CVS and/or on

Re: [mosh-devel] [mosh-users] Mosh 1.3.1 release candidate 2 available for testing

On 5/28/17 11:15 AM, Jeremie Courreges-Anglas wrote: > ack, let me know if you need more data. > Nicholas Marriott and I seem to have found a solution involving small changes to both tmux and mosh's tests. I'm waiting for his changes to appear in OpenBSD CVS and/or on GitHub for final verification

Re: [mosh-devel] [mosh-users] Mosh 1.3.1 release candidate 2 available for testing

On 5/26/17 9:37 PM, John Hood wrote: > On 05/26/2017 21:21, Jeremie Courreges-Anglas wrote: >> Keith Winstein writes: >> >>> Thanks, Jeremie! Do these tests work with 1.3.0? (And if so, are you able >>> to bisect this for us?) >> Summary: >> emulation-80th-column.test result: ERROR instead of FAIL

Re: [mosh-devel] [mosh-users] Mosh 1.3.1 release candidate 2 available for testing

Hi, I did not look precisely at problems reported by make check with mosh-1.3.1-rc2 on OpenBSD-current; but here are the logs for ten make check runs: http://autogeree.net/~jca/tmp/mosh-1.3.1-rc2-OpenBSD-make-check.tgz grep ERROR: shows that emulation-80th-column exists with either FAIL or ER

Re: [mosh-devel] [mosh-users] Mosh 1.3.1 release candidate 2 available for testing

On 05/26/2017 21:21, Jeremie Courreges-Anglas wrote: > Keith Winstein writes: > >> Thanks, Jeremie! Do these tests work with 1.3.0? (And if so, are you able >> to bisect this for us?) > Summary: > emulation-80th-column.test result: ERROR instead of FAIL > emulation-scroll.test result: did not exis

Re: [mosh-devel] [mosh-users] Mosh 1.3.1 release candidate 2 available for testing

Keith Winstein writes: > Thanks, Jeremie! Do these tests work with 1.3.0? (And if so, are you able > to bisect this for us?) Summary: emulation-80th-column.test result: ERROR instead of FAIL emulation-scroll.test result: did not exist in 1.3.0 So nothing to bisect, as far as I can see. Log fil

Re: [mosh-devel] [mosh-users] Mosh 1.3.1 release candidate 2 available for testing

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. > > > > -- > jca | PGP : 0x152

Re: [mosh-devel] Mosh 1.3.1 release candidate 2 available for testing

On OpenBSD-current (amd64), make check reports two failures. Log files attached. mosh-make-check.log Description: Binary data test-suite.log Description: Binary data -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE signature.asc Description: PGP signature __

Re: [mosh-devel] [mosh-users] Mosh 1.3.1 release candidate 2 available for testing

-mosh-users Passes smoke test in Mosh for Chrome, although my build system isn't running any tests. On Sun, May 21, 2017 at 8:23 PM john hood wrote: > Hi all, > > I'm pleased to announce a release candidate for Mosh 1.3.1. This is a minor, > bug-fix release, addressing platform/portability is

[mosh-devel] Mosh 1.3.1 release candidate 2 available for testing

Hi all, I'm pleased to announce a release candidate for Mosh 1.3.1. This is a minor, bug-fix release, addressing platform/portability issues and a couple of terminal emulation issues. Most users will not need to upgrade to this release, but if you use the JuiceSSH Android client or tmux 2.4 o

[mosh-devel] mosh 1.3.0 released (corrected announcement)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Mosh users and developers, mosh 1.3.0 has been released. (This is a corrected release announcement that fixes a typo in the previous email.) The source code is at: https://mosh.org/mosh-1.3.0.tar.gz (SHA-256: 320e12f461e55d71566597976bd9440ba

[mosh-devel] mosh 1.3.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Mosh users and developers, mosh 1.3.0 has been released. The source code is at: https://mosh.org/mosh-1.3.0.tar.gz (SHA-256: 320e12f461e55d71566597976bd9440ba6c5265fa68fbf614c6f1c8401f93376) John Hood was the primary developer and release co

Re: [mosh-devel] Mosh 1.3.0 release candidate 2 available for testing

On 03/21/2017 06:07, Jeremie Courreges-Anglas wrote: > John Hood writes: > >> Thanks for the fix. I ended up fixing some problems with our test cases >> so that they run properly on OpenBSD 6.0+, and your change checks out >> OK. It's all at . >>

Re: [mosh-devel] Mosh 1.3.0 release candidate 2 available for testing

Jeremie Courreges-Anglas writes: > John Hood writes: > >> Thanks for the fix. I ended up fixing some problems with our test cases >> so that they run properly on OpenBSD 6.0+, and your change checks out >> OK. It's all at . >> Keith, Jeremie, woul

Re: [mosh-devel] Mosh 1.3.0 release candidate 2 available for testing

John Hood writes: > Thanks for the fix. I ended up fixing some problems with our test cases > so that they run properly on OpenBSD 6.0+, and your change checks out > OK. It's all at . > Keith, Jeremie, would you mind looking at that? With the pull

Re: [mosh-devel] Mosh 1.3.0 release candidate 2 available for testing

__ mosh-devel mailing list mosh-devel@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh-devel ___ mosh-devel mailing list mosh-devel@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh-devel

Re: [mosh-devel] Mosh 1.3.0 release candidate 2 available for testing

john hood writes: > Hi all, > > I'm pleased to announce a release candidate for Mosh 1.3.0. We have > brought you mostly bugfixes and release engineering improvements-- the > version number jump is because we have switched to semantic versioning > (). The changes mostly addr

Re: [mosh-devel] mosh and utmp on athena.dialup.mit.edu

Just to close the loop, the utempter-dev package is now on the production dialups too. Jonathon Jonathon Weiss wrote: > 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 o

Re: [mosh-devel] mosh and utmp on athena.dialup.mit.edu

AFS has sysname fallback built in these days. It looks like in the mosh_project locker both 16.04 and 14.04 are falling back to amd64_ubuntu1004 (which is a link to amd64_deb60). If you create a new amd64_ubuntu1604, you could build for it seperately, while letting the dialups (14.04) continue t

Re: [mosh-devel] mosh and utmp on athena.dialup.mit.edu

Hello Lizhou, Sigh, these should probably not be the same sysname, but I guess that ship has probably sailed. I reverted to a statically-linked binary, but still compiled on Athena. utempter seems to be still working on athena.dialup. -Keith On Fri, Feb 24, 2017 at 2:23 PM, Lizhou Sha wrote: >

Re: [mosh-devel] mosh and utmp on athena.dialup.mit.edu

Hi Keith, I'm observing a regression for my self-deployed Ubuntu 16.04 dialup with regards to libprotobuf linkage: $ mosh --ssh="ssh -K" --server="athrun mosh_project mosh-server" sha.mit.edu -- byobu a -d /afs/sipb.mit.edu/project/mosh/arch/amd64_deb60/bin/mosh-server.real: error while loading s

Re: [mosh-devel] mosh and utmp on athena.dialup.mit.edu

Hello Jonathon, I deployed a new build of mosh-server for amd64 architectures (compiled on test.dialup) in the mosh_project locker. It seems to be updating utmp now. Please let me know if you see any trouble. -Keith On Fri, Feb 24, 2017 at 1:17 PM, Jonathon Weiss wrote: > Hi Keith, > > libutem

Re: [mosh-devel] mosh and utmp on athena.dialup.mit.edu

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 Winstein wrote: > Hello Jonathon, > > I investigate

Re: [mosh-devel] mosh and utmp on athena.dialup.mit.edu

iss > MIT/IS&T/Infrastructure Design & Engineering > Cloud Platforms (Server Operations) > ___ > mosh-devel mailing list > mosh-devel@mit.edu > http://mailman.mit.edu/mailman/listinfo/mosh-devel > ___ mosh-devel mailing list mosh-devel@mit.edu http://mailman.mit.edu/mailman/listinfo/mosh-devel

Re: [mosh-devel] mosh and utmp on athena.dialup.mit.edu

On 23 February, 2017 - Jonathon Weiss wrote: > > Hello all, > > Following up on a zephyr conversation I had with Keith and others > about a week ago, I was wondering why mosh logins don't appear in the > output of "who" or "w" on the athena.dialup.mit.edu servers. We got > as far as confirming

[mosh-devel] mosh and utmp on athena.dialup.mit.edu

Hello all, Following up on a zephyr conversation I had with Keith and others about a week ago, I was wondering why mosh logins don't appear in the output of "who" or "w" on the athena.dialup.mit.edu servers. We got as far as confirming that utempter was setgid utmp: -rwxr-sr-x 1 root utmp 10104

Re: [mosh-devel] Mosh 1.3.0 release candidate 2 available for testing

Hi, I have compiled and tested (and am using) 1.3.0-rc2 (a092b0f) on multiple current OpenBSD 6.0 boxes connected via satellite and terrestrial links. There appear to be no regressions from 1.2.6 (68f91a0). /Dan ___ mosh-devel mailing list mosh-devel@mit

Re: [mosh-devel] Mosh 1.3.0 release candidate 2 available for testing

On 01/06/2017 00:36, john hood wrote: > Areas we'd like to see testing ('make distcheck', mostly) in before we > do a final release: > > * Fedora > * RHEL 5 and 6 > * the OS X binary .pkg, especially on older OS X versions > * OS X compiling from source > * OpenBSD > * FreeBSD > * NetBSD > * ARMv

Re: [mosh-devel] [mosh-users] Mosh 1.3.0 release candidate 2 available for testing

I have successfully done a smoke test of 1.3.0 RC2 in Mosh for Chrome. No issues building or running. On Fri, Jan 6, 2017 at 1:59 AM Richard Woodbury wrote: > -mosh-users@ > > I've slated time to do a bunch of Mosh for Chrome work on the week of Jan > 16, so I'll give it a go at that time. > > >

Re: [mosh-devel] Mosh 1.3.0 release candidate 2 available for testing

Hi, On Fri, Jan 06, 2017 at 12:36:52AM -0500, john hood wrote: > I'm pleased to announce a release candidate for Mosh 1.3.0. If you want to have Mosh 1.3.0 in the next Debian Stable release (expected in Summer this year), Mosh 1.3.0 needs to be uploaded to Debian Unstable latest on 24th of Januar

Re: [mosh-devel] [mosh-users] Mosh 1.3.0 release candidate 2 available for testing

-mosh-users@ I've slated time to do a bunch of Mosh for Chrome work on the week of Jan 16, so I'll give it a go at that time. On Fri, Jan 6, 2017 at 12:39 AM john hood wrote: > Hi all, > > I'm pleased to announce a release candidate for Mosh 1.3.0. We have > brought you mostly bugfixes and rel

[mosh-devel] Mosh 1.3.0 release candidate 2 available for testing

Hi all, I'm pleased to announce a release candidate for Mosh 1.3.0. We have brought you mostly bugfixes and release engineering improvements-- the version number jump is because we have switched to semantic versioning (). The changes mostly address regressions in the previous

Re: [mosh-devel] Mosh OS X package build on Travis

On 11/2/16 8:43 PM, Jim Cheetham wrote: > Quoting john hood (2016-11-02 18:45:17) >> This isn't going to happen instantly. One approach to the trust issue >> here might be to just cop out-- stop doing OS X package builds and tell >> people to build their own, until we get this stuff into better sh

Re: [mosh-devel] Mosh OS X package build on Travis

Quoting john hood (2016-11-02 18:45:17) > This isn't going to happen instantly. One approach to the trust issue > here might be to just cop out-- stop doing OS X package builds and tell > people to build their own, until we get this stuff into better shape. That probably doesn't really help - jus

Re: [mosh-devel] Mosh OS X package build on Travis

Hi there. Pardon the de-lurk, but I have a few thoughts on the topic that might help. I use mosh on os x and linux. I also happen to use homebrew. As you've already pointed out, a proper package manager makes a lot of this much easier. There are a couple ways to get closer to this on a mac. Firs

Re: [mosh-devel] Mosh OS X package build on Travis

On 10/31/16 10:46 AM, john hood wrote: > On 10/31/16 12:41 AM, Jim Cheetham wrote: >> Quoting john hood (2016-10-31 17:12:06) >>> Alas, we will not get any kind of repeatable builds out of this, Travis >>> constantly updates their build images and we update to current Homebrew >>> for dependencies

Re: [mosh-devel] Mosh OS X package build on Travis

On 10/31/16 6:18 AM, John Hawkinson wrote: > I think we should not lose sight of the fact that mosh is > security-sensitive software in a category unlike many other > software packages, and thus it is worth some inconvenience to > the maintainers that you might not accept in a less sensitive > tool

Re: [mosh-devel] Mosh OS X package build on Travis

On 10/31/16 12:41 AM, Jim Cheetham wrote: > Quoting john hood (2016-10-31 17:12:06) >> Alas, we will not get any kind of repeatable builds out of this, Travis >> constantly updates their build images and we update to current Homebrew >> for dependencies on every build. > > That's the worst bit. Us

Re: [mosh-devel] Mosh OS X package build on Travis

I think we should not lose sight of the fact that mosh is security-sensitive software in a category unlike many other software packages, and thus it is worth some inconvenience to the maintainers that you might not accept in a less sensitive tool. Another question: would we rather we be compromise

Re: [mosh-devel] Mosh OS X package build on Travis

Quoting john hood (2016-10-31 17:12:06) > Alas, we will not get any kind of repeatable builds out of this, Travis > constantly updates their build images and we update to current Homebrew > for dependencies on every build. That's the worst bit. Using external services that are *unlikely* to attack

[mosh-devel] Mosh OS X package build on Travis

I've been working on making Travis do the OS X package build for us. (Previously, some poor Mosh developer had to do it manually and upload it to the Mosh website.) The thing I have it doing now is building the package when a tag is pushed, and uploading it to a GitHub release on cgull/mosh. The

[mosh-devel] mosh-devel anti-spam changes (moderating posts from non-members)

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 m

Re: [mosh-devel] Mosh regression between 10.x and 11-stable

On 8/13/16 4:30 AM, Peter Jeremy wrote: > Hi John, > > Sorry, I got side-tracked. > > On 2016-Aug-12 16:37:15 -0400, John Hood wrote: >> >Could I ask you to look at this a little further? On the one hand, it >> >sure looks like a Mosh issue, and tcdrain() solves it-- but on the other >> >hand,

[mosh-devel] mosh 1.2.6 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Mosh users and developers, mosh 1.2.6 has been released. The source code is at: https://mosh.org/mosh-1.2.6.tar.gz (SHA-256: 7e82b7fbfcc698c70f5843bb960dadb8e7bd7ac1d4d2151c9d979372ea850e85) John Hood was the release coordinator and deserves a

Re: [mosh-devel] Mosh regression between 10.x and 11-stable

That's interesting (not in a good way). Next thing to try: mosh --server='/usr/local/bin/mosh-server 2>/dev/null' peter@VPS (with an unmodified mosh-server) Mosh prints the 'MOSH CONNECT ...' message on stdout, then forks. The parent exits immediately, and the child prints verbose and copyrigh

Re: [mosh-devel] Mosh regression between 10.x and 11-stable

On 2016-Aug-11 10:06:35 -0700, Ngie Cooper wrote: > >> On Aug 11, 2016, at 09:30, John Hood wrote: >> >> I still can't reproduce this on 3 different 11.0-BETA4 servers and a >> variety of clients and networks. Can you try and identify a more >> portable repro or at least figure out why it fails

Re: [mosh-devel] Mosh regression between 10.x and 11-stable

On 2016-Aug-11 12:30:23 -0400, John Hood wrote: >I still can't reproduce this on 3 different 11.0-BETA4 servers and a >variety of clients and networks. Can you try and identify a more >portable repro or at least figure out why it fails on your system? > >Please try applying this patch, too. It's

Re: [mosh-devel] Mosh regression between 10.x and 11-stable

> On Aug 11, 2016, at 09:30, John Hood wrote: > > I still can't reproduce this on 3 different 11.0-BETA4 servers and a > variety of clients and networks. Can you try and identify a more > portable repro or at least figure out why it fails on your system? > > Please try applying this patch, too

Re: [mosh-devel] Mosh regression between 10.x and 11-stable

I still can't reproduce this on 3 different 11.0-BETA4 servers and a variety of clients and networks. Can you try and identify a more portable repro or at least figure out why it fails on your system? Please try applying this patch, too. It's a shot in the dark, though. regards, --jh >From

Re: [mosh-devel] Mosh regression between 10.x and 11-stable

On 2016-Aug-10 14:32:15 -0400, john hood wrote: >On 8/10/16 4:18 AM, Peter Jeremy wrote: >> I recently updated one of my VPS hosts from 10.3-RELEASE-p5 to 11.0-BETA4 >> r303811 and mosh to that host from my Linux laptop stopped working. All >> I get on the laptop is: >> $ mosh remotehost >> Conne

Re: [mosh-devel] Mosh regression between 10.x and 11-stable

On 8/10/16 4:18 AM, Peter Jeremy wrote: > I recently updated one of my VPS hosts from 10.3-RELEASE-p5 to 11.0-BETA4 > r303811 and mosh to that host from my Linux laptop stopped working. All > I get on the laptop is: > $ mosh remotehost > Connection to remotehost closed. > /usr/bin/mosh: Did not fi

Re: [mosh-devel] Mosh regression between 10.x and 11-stable

On 8/10/16 4:18 AM, Peter Jeremy wrote: > I recently updated one of my VPS hosts from 10.3-RELEASE-p5 to 11.0-BETA4 > r303811 and mosh to that host from my Linux laptop stopped working. All > I get on the laptop is: > $ mosh remotehost > Connection to remotehost closed. > /usr/bin/mosh: Did not fi

[mosh-devel] mosh-devel?欧洲《议会杂志》：欧盟应对中共强摘器官采取行动！From 方阡華

你知道什麼是發生在我們的國家NgSBv3JpI6CcnHqhXefjBg==?我們給了z8MRp/ke7yBc/B7YwenmiA==實話你vePRz9+NK3t/VkR3Q1IZ4Q== http://coduyen.info/BHV/mb1.pdf http://zhanxiang.svm.club/getdocs.aspx?id=thetruth 閱讀HcU1cf+XgMUnTfVXpiIkJQ==全文87ZCH5LRB5KqE4R94jNlug==： 谢谢 ! Virus-free. www.avast.com _

Re: [mosh-devel] Mosh 1.2.5-2 silently dying on ubuntu 16.04

Hi, I'm baffled. It seems to work now. I compiled from git and installed it into /usr/local/bin/mosh , which seems to work: patrik@hirvinen:~/mosh⟫ /usr/local/bin/mosh-server new -v MOSH CONNECT 60003 RobGIv+BFf58Q79o6/Fs3w mosh-server (mosh 1.2.5.95rc1) [build mosh-1.2.5.95rc1-4-gece4280]

  1   2   3   >