|
From: <tho...@ph...> - 2003-09-23 15:13:18
|
Hi,
we are not allowed to have outbound traffic save using our proxies. Sourceforge indicates other
ports (e.g. 80) are supported, and it's easy to set that in ssh, but I have no idea how to tell ssh to
use our proxy (btw I use openssh, I'll have a closer look if time allows it).
If that remains difficult I will use my home account.
Ciao,
Thomas
Dr. Thomas Portele Tho...@ph...
Philips Research Laboratories Man-Machine Interfaces
Weisshausstrasse 2 52066 Aachen, Germany
Phone: +49 241 6003-712 Fax.: +49 241 6003-518
To: mul...@li...
cc: Stefan Merten <me...@df...>
(bcc: Thomas Portele/ACN/RESEARCH/PHILIPS)
Subject: Re: [MP-d] Re: Parallel branches for existing derivations
Stefan Merten <me...@df...>
Classification:
Sent by:
mul...@li...
.net
09/23/2003 10:54 AM
Please respond to multiplatform-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hi Thomas!
1 hours ago thomas portele wrote:
> it seems I am having problems with our firewall.
:-(
I have a firewall / address translation configuration at home which
works without any problems. However, this firewall does not prevent
outbound connections.
> I.e. ssh to sourceforge does not work.
This is a prerequisite for playing an active role as far as I can see
:-( .
> One possibility is using another port (e.g. 80) but I have not yet figured out how
> to tell ssh to use our HTTP proxy for the connection.
So it seems the access to the outbound port is blocked. That's bad.
Why does someone want to block outbound traffic for port 22? Anyway.
A useful general tip with all these problems is the `-v' flag of
`ssh'.
Another useful information is which version of `ssh' you are using. To
my knowledge there are three main streams out there: `ssh1' and `ssh2'
by SSH Corp. and `ssh' by OpenSSH which combines version 1 and version
2 functionality. Just a few days ago I checked the current state of
affairs and learned that OpenSSH is the best choice because it is most
interoperable and has a number of options.
In OpenSSH there are some options for ports:
-p port
Port to connect to on the remote host. This can be specified on
a per-host basis in the configuration file.
-P Use a non-privileged port for outgoing connections. This can be
used if your firewall does not permit connections from privileged
ports. Note that this option turns off RhostsAuthentication and
RhostsRSAAuthentication for older servers.
May be `-P' might help you. After all using privileged ports I could
imagine to be a reason for blocking.
Hope this helps
Stefan
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQCVAgUBP3AKVgnTZgC3zSk5AQHYjAP+O/bn/WKdYH49+i/nJQ2Z+XHABF5J9j5g
rz6syQVtKPFTqjWnTrg6S2LS+c1FJ2AweRZnghkDF1nkT9mNY/zuTt5PT+KVn8ts
nZuWYTj2bwkWzjkJRuJRgcyBPsluRT9Ow/+Pg3vq5RXJNEy7yqwZMFsMyB330Sc3
EwVY/Jp6NCY=
=MLt6
-----END PGP SIGNATURE-----
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
multiplatform-devel mailing list
mul...@li...
https://lists.sourceforge.net/lists/listinfo/multiplatform-devel
|