.:: Bots United ::.

.:: Bots United ::. (http://forums.bots-united.com/index.php)
-   The Agora (http://forums.bots-united.com/forumdisplay.php?f=38)
-   -   Bots United start a Sourceforge project? (http://forums.bots-united.com/showthread.php?t=1181)

Pierre-Marie Baty 28-03-2004 19:39

Re: Bots United start a Sourceforge project?
 
I agree with botmeister. Since not everybody in the Council seem to have the same preference, someone opens a poll in the moderators forum, so that we can decide quickly.

Nova 29-03-2004 12:32

Re: Bots United start a Sourceforge project?
 
Another option:

Sourceforge system is opensource. Why dont we just run our ownm project management system ?

Nova

Nova 30-03-2004 19:33

Re: Bots United start a Sourceforge project?
 
Quote:

Originally Posted by Nova
Another option:

Sourceforge system is opensource. Why dont we just run our ownm project management system ?

Nova

oh, and btw. i got our own CVS server running coz i use it for my own work.

Onno Kreuzinger 30-03-2004 20:07

Re: Bots United start a Sourceforge project?
 
so its up and running allready ?
cool 8)

should we use ssh fowarding (perhaps with key authentication) instad of opening the port in the firewall ?

Nova 30-03-2004 20:28

Re: Bots United start a Sourceforge project?
 
Quote:

Originally Posted by memed
so its up and running allready ?
cool 8)

should we use ssh fowarding (perhaps with key authentication) instad of opening the port in the firewall ?

your the security expert not me :) if you want ok ...

Terran 30-03-2004 21:37

Re: Bots United start a Sourceforge project?
 
You can use CVS directly with SSH, there is no need for portforwarding.
For Linux you set an environment variable which replaces the default rsh command with the ssh command.
For Windows this depends on the client...

Onno Kreuzinger 30-03-2004 22:39

Re: Bots United start a Sourceforge project?
 
i know, but that includes a valid shell login, i thought of ssh2 key with strict permissions to only foward a certain port :-)

cheers memed
----
there are paranoid admins and stupid admins *g*

Terran 31-03-2004 11:57

Re: Bots United start a Sourceforge project?
 
You can't do that without logging in to the host. I'll try to explain:

The ssh protocol is an end-to-end protocol, only the connections between two authenticated and authorized hosts are encrypted. You can use ssh tunnels between those two hosts once you're in. These tunnels encrypt the traffic between those hosts bot not the traffic outside of these connections!

And (at least with OpenSSH) you can't restrict which ports are allowed to be forwarded - you only can turn it on or off.

What you could do would be to use stunnel instead of ssh. (www.stunnel.org)
Use it to encrypt the pserver protocoll and block the direct access to the pserver port using iptables. The drawback of this is that the developers need iptables at their machines too - but that's not a big problem ;).

Onno Kreuzinger 31-03-2004 12:24

Re: Bots United start a Sourceforge project?
 
*g* nice that you want to explain, but i think i know what i'm talking about ;)

Quote:

Originally Posted by Terran
You can't do that without logging in to the host. I'll try to explain:
The ssh protocol is an end-to-end protocol, only the connections between two authenticated and authorized hosts are encrypted. You can use ssh tunnels between those two hosts once you're in. These tunnels encrypt the traffic between those hosts bot not the traffic outside of these connections!

And (at least with OpenSSH) you can't restrict which ports are allowed to be forwarded - you only can turn it on or off.

What you could do would be to use stunnel instead of ssh. (www.stunnel.org)
Use it to encrypt the pserver protocoll and block the direct access to the pserver port using iptables. The drawback of this is that the developers need iptables at their machines too - but that's not a big problem ;).

a ssh login which does arbitraty application (terminal) forwarding needs to be able to log in, whilst a portforwarding only account can't login. the difference is that with the normal ssh login account you can log into the server an get a shell, while the portfw only login can not log in and request a terminal.

sounds not very different but in terms of security it's a key point. the portfw only user can not try local root exploits (e.g. do_brk ..) since he can not spawn a shell at all.

stunnel is not as secure as ssh unless a real PKI is used, allthough it's probably the easier one to setup and security is very good allready.

cheers memed

from man sshd:
[qoute]
AUTHORIZED_KEYS FILE FORMAT
$HOME/.ssh/authorized_keys is the default file that lists the public keys
that are permitted for RSA authentication in protocol version 1 and for
public key authentication (PubkeyAuthentication) in protocol version 2.
AuthorizedKeysFile may be used to specify an alternative file.
...
...
...
no-pty Prevents tty allocation (a request to allocate a pty will fail).

permitopen="host:port"
Limit local ``ssh -L'' port forwarding such that it may only con-
nect to the specified host and port. IPv6 addresses can be spec-
ified with an alternative syntax: host/port. Multiple permitopen
options may be applied separated by commas. No pattern matching
is performed on the specified hostnames, they must be literal
domains or addresses.

[/quote]

Terran 31-03-2004 13:13

Re: Bots United start a Sourceforge project?
 
GREAT DANGER: not having a pty doesn't prevent users from executing programs !!!

Test for yourself:
ssh -v user@host /bin/bash

But I've at least missed the permitopen="host:port" option, never noticed that before 9_9. But for a person with some skills this is no real limitation, he/she would simple install/use another forwarder...


All times are GMT +2. The time now is 04:28.

Powered by vBulletin® Version 3.8.2
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.