9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Iruata Souza <iru.muzgo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9port behind corporate firewall with no DNS or port access
Date: Sat, 25 Jul 2009 13:56:44 -0300	[thread overview]
Message-ID: <d1c554290907250956j2a63fd20k8a04de87ceaffe01@mail.gmail.com> (raw)
In-Reply-To: <20090725163952.GA25352@finiteless.net>

On Sat, Jul 25, 2009 at 1:39 PM, Salman Aljammaz<sio@finiteless.net> wrote:
> Uriel wrote:
>> If your work firewall proxies port 80, then things get trickier, you
>> could mount sources on the home inferno instance, and then export it
>> using mjl's httpd as a read-only http 'tree'.
>
> assuming you've got openssh, one trick i used to do back in school was
> run sshd on on port 443.
>
> you can then forward specific ports (-L) or even run socks (-D) on ssh.
>
> salman
>
>
>

on unix:
% cat .ssh/config
Host xxx
ProtocolKeepAlives 30
ProxyCommand /path/to/proxytunnel/proxytunnel -p proxyhost:proxyport
-P proxyuser:proxypass -d xxx.org

% ssh -D localproxyport
-Llocaladdress:localport:sources.cs.bell-labs.com:564 user@xxx.org


on Plan 9:
% srv -nq tcp!localaddress!localport sources /n/sources


and there you have it. only tested it for non-authenticated connections.

iru



      parent reply	other threads:[~2009-07-25 16:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25  4:06 Jason Catena
2009-07-25  4:35 ` andrey mirtchovski
2009-07-25  4:55   ` Jason Catena
2009-07-25 13:56     ` erik quanstrom
2009-07-25  8:12 ` Steve Simon
2009-07-25 12:43   ` Uriel
2009-07-25 16:39     ` Salman Aljammaz
2009-07-25 16:55       ` John Floren
2009-07-25 16:56       ` Iruata Souza [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d1c554290907250956j2a63fd20k8a04de87ceaffe01@mail.gmail.com \
    --to=iru.muzgo@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).