On Fri, May 1, 2009 at 2:54 AM, Fredrik Klasson <[email protected]> wrote:
> Hello,
> I'm not sure what I did wrong, but it seems this mail didn't make it to the
> mailing list when I sent it last time (can't see it in the archives at least).
> So I'm trying again (this time using gmail instead of my ISP's mail server).
> I'm sorry if the fwd'd mail ends up twice in your inboxes.
The mailing list rejects posts from unsubscribed addresses (it cuts
down a lot on spam) -- you probably have a bounce message somewhere,
if you look. (At least, I hope you do! If not then the mailing list
software is probably misconfigured somehow...)
> --------------- Vidarebefordrat brev ----------------
> Since I have the bad/obscure/fun habit of trying to avoid script-kiddies
> probing port 22, I tend to run in to the problems of applications assuming
> that ssh is always using the default port (22/tcp). So, instead of just
> complaining I thought I'd make life a little more fun, so I created this
> little patch against partial-all-0.0.6.
> This patch actually adds 2½ features:
> * ability to connect/attach via ssh on a non-standard port
> * ability to enable (actually request, please refer to ssh(1)) ssh
> compression.
> * (the ½ feature) A little extra debug output, debug features "/ssh[1-3]?/",
> which i.e. adds -v or -v up to -vvv for ssh.
Cool, thanks for sending this in!
> The compression is something I've noticed makes quite a difference when I'm
> using ssh via a wifi link, which tend to be like a modem - slow and
> unreliable. For fast links (e.g. LAN) it's according to ssh(1) probably slower
> (though, I haven't noticed any major degradation when using -C locally).
That's very very surprising. xpra does its own compression under the
hood, and it's enabled by default. Adding ssh compression on top of
that should have no effect whatsoever (except increasing CPU time a
bit). When you say you've noticed it makes a difference, do you mean
that it feels a bit faster, you guess, maybe, sure, definitely? Or is
it totally dramatic and each time you switch back and forth you notice
immediately? Do you have any measurements?
> The new format for attaching to ssh is:
> ssh:host[[:port]:display]
> compared to the old:
> ssh:host[:display]
1) Just for your information, you can save some typing in general, and
not just with xpra, by adding the port info to your ~/.ssh/config -- I
think the syntax is
Host my.host.com *.foo.edu
Port 3117
2) I think it'd be better to handle ssh compression/verbosity/port
number/whatever someone thinks of next through a single unified
mechanism, maybe
xpra attach --ssh="ssh -p 3117 -C" ssh:frodo.ucsd.edu
The hack with ssh3: etc. is clever but seriously non-obvious, and then
someone will want 'ssh3blowfish:' to specify the -c option, and...
yeah. Interested in writing up a patch to do things this way? (You can
see the handling of --remote-xpra for something analogous.)
> I'm pretty confident this patch won't break anything but only add the listed
> features. Though, I'm not sure I've used the --debug argument correctly, see
> the FIXME comment.
Yeah, you shouldn't be looking at the --debug argument directly, you
should just log a message with the proper subsystem identifier and
then let the logger figure out what to do with it. The usual way is to
stick two boilerplate lines at the top of the file:
from wimpiggy.log import Logger
log = Logger()
which is a helper that creates a logger for the subsystem named after
the current module (most files have this already), and then use it
like
log("hey! %s", message)
log.warn("oops")
etc.
> Btw, I'm probably going to start loving xpra just as I do screen :).
Glad to hear it!
> Though,
> I've had some issues with input not working with xterm (I only get mojibake
> from my keystrokes). But that's a different issue .:)
Yes, keyboard handling is the nastiest part of the current design...
it needs to be rewritten, but it's not clear how to get things Right
given the constraints of X. I'm still trying to figure out the best
approach. For now, basic US English stuff should mostly work, and if
you need other characters than you might try changing the keymap that
the xpra server uses (e.g. by running setxkbmap against your xpra
display).
-- Nathaniel
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
