Faysal Banna | 2 Jun 2007 15:29
Picon

ssh tunnel proxy setup

Hi all..
am trying to incorporate a tunnel from over a slow setup ........

/-------------------------/                                                                                        
/-------------------------------/
|     host1                  |=========//Tunnel ssh 
//====================|           Host2                   |
|     squid parent       |                               
                                                        | squid 
http_port 3128     |
|     127.0.0.1:8080   
|                                                                                       
|           acl accept all        |
\-------------------------\                                                                                        
\-------------------------------\

Host1 configuration :
ssh -L 8080:127.0.0.1:3128 -C   -N -f  client <at> host2

The tunnel goes through the link and forwards port 8080 to 3128 from 
host1 to host2
main reason is that the actual link size is 2Mbit/s and i need to pass 
the data in compression to gain maximum http transparent proxied data 
transfer from Host2 to Host1.
It works fine as long as i don't have heavy load but when i connect 
Host1 to the local home network i start having some delay after a 
certain amount of time i believe when the clients establish sessions 
through squid which redirected to parents over the Tunnel session created .
i have separated the logs squid log shows normal connectivity but on the 
console after ssh established i got this message
(Continue reading)

Faysal Banna | 2 Jun 2007 23:09
Picon

Channel setup

Hi all
am setting up a Forward Tunnel from one machine to another machine
can anyone Guide me what this might be its degrading performance on a 
busy server load

channel 968: open failed: administratively prohibited: open failed
channel 969: open failed: administratively prohibited: open failed
channel 973: open failed: administratively prohibited: open failed
channel 975: open failed: administratively prohibited: open failed
channel 976: open failed: administratively prohibited: open failed
channel 977: open failed: administratively prohibited: open failed
channel 978: open failed: administratively prohibited: open failed
channel 980: open failed: administratively prohibited: open failed
channel 981: open failed: administratively prohibited: open failed
channel 982: open failed: administratively prohibited: open failed
channel 983: open failed: administratively prohibited: open failed
channel 984: open failed: administratively prohibited: open failed
channel 987: open failed: administratively prohibited: open failed
channel 988: open failed: administratively prohibited: open failed
channel 989: open failed: administratively prohibited: open failed
channel 990: open failed: administratively prohibited: open failed
channel 991: open failed: administratively prohibited: open failed
channel 997: open failed: administratively prohibited: open failed
channel 1001: open failed: administratively prohibited: open failed
channel 1002: open failed: administratively prohibited: open failed
channel 1003: open failed: administratively prohibited: open failed
channel 1004: open failed: administratively prohibited: open failed
channel 1006: open failed: administratively prohibited: open failed
channel 1007: open failed: administratively prohibited: open failed
channel 1009: open failed: administratively prohibited: open failed
(Continue reading)

Faysal Banna | 2 Jun 2007 23:21
Picon

Tunnel connection channel Setup with proxy server

Hi all..
am trying to incorporate a tunnel from over a slow setup ........

/-------------------------/                                                                                        
/-------------------------------/
|     host1                  |=========//Tunnel ssh 
//====================|           Host2                   |
|     squid parent       |                               
                                                       | squid http_port 
3128     |
|     127.0.0.1:8080   
|                                                                                       
|           acl accept all        |
\-------------------------\                                                                                        
\-------------------------------\

Host1 configuration :
ssh -L 8080:127.0.0.1:3128 -C   -N -f  client <at> host2

The tunnel goes through the link and forwards port 8080 to 3128 from 
host1 to host2
main reason is that the actual link size is 2Mbit/s and i need to pass 
the data in compression to gain maximum http transparent proxied data 
transfer from Host2 to Host1.
It works fine as long as i don't have heavy load but when i connect 
Host1 to the local home network i start having some delay after a 
certain amount of time i believe when the clients establish sessions 
through squid which redirected to parents over the Tunnel session created .
i have separated the logs squid log shows normal connectivity but on the 
console after ssh established i got this message
(Continue reading)

Darren Tucker | 4 Jun 2007 16:16
Picon
Picon

Re: [PATCH] Add support for ldns

Simon Vallet wrote:
> nobody on this one ?

Sorry for the delay.  I started looking at this and then got sidetracked 
(as usual).

> I really think autonomous signature validation capabilities are a useful
> feature in an ssh client. In a mobile scenario, simply trusting the next
> DNS hop seems only marginally better as having no signed records at all.
> 
> I'm willing to spend more time on this patch if necessary, so any
> feedback is welcome

I have no objection to this in principle.  LDNS seems to be under a 
3-clause BSD style license so there's no potential license hassles.

About the patch itself, I would probably wait until the required 
features make it into a released version of the software so there's more 
likelihood of the interface being stable.  I would also like someone 
more familiar with DNSSEC than me to sanity check it.

You added the additional functionality to one of the files that we try 
to keep in sync with its OpenBSD counterpart, so that's a potential 
maintenance hassle.  I think it would be better in its own file, which 
according to the existing convention would be bsd-getrrsetbyname.c.

Also, I'm not wild about the use of debug() calls in the compat library 
but I can see why you've used them.  We try to avoid them in code that 
replaces library functions so the code is usable in other things.

(Continue reading)

Pat Cornick | 1 Jun 2007 15:17
Picon
Favicon

Need to sftp with automatic login from 1 aix machine to another, the id on the target is a DCE(DFS) id


Hi,

I had a question and can not find out on the web where anyone might have
done this.  I am sftping
between one AIX machine and another using automatic login.  I have created
the id_rsa.pub on the
source server and added it to the /.ssh/authorized_keys file on the target
server.  The problem we
are having seems to be that because the target id is a DCE(DFS) id and it's
home directory is
/fs/home/bondbpex  instead of /home/bondbpex it can't find the
/.ssh/authorized_keys file.  The
permissions on the .ssh directory is 700 and the authorized_keys file is
600.  Is this possible to be able
to do this?  Thanks for any help you can give me.

/home/bondbrdg> sftp -v -v -v bondbpex <at> d03ftp101.boulder.ibm.com
Connecting to d03ftp101.boulder.ibm.com...
OpenSSH_4.3p2, OpenSSL 0.9.7l 28 Sep 2006
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Failed dlopen: /usr/krb5/lib/libkrb5.a(libkrb5.a.so): Could not
load module /usr/krb5/lib/libkrb5.a(libkrb5.a.so).
System error: No such file or directory

debug1: Error loading Kerberos, disabling Kerberos auth.
debug2: ssh_connect: needpriv 0
debug1: Connecting to d03ftp101.boulder.ibm.com [9.17.187.85] port 22.
debug1: Connection established.
debug3: Not a RSA1 key file /home/bondbrdg/.ssh/id_rsa.
(Continue reading)

Peter Stuge | 4 Jun 2007 21:18

Re: Need to sftp with automatic login from 1 aix machine to another, the id on the target is a DCE(DFS) id

On Fri, Jun 01, 2007 at 09:17:39AM -0400, Pat Cornick wrote:
> The problem we are having seems to be that because the target id is
> a DCE(DFS) id and it's home directory is /fs/home/bondbpex  instead
> of /home/bondbpex it can't find the /.ssh/authorized_keys file.

So put authorized_keys in the correct directory then.

> The permissions on the .ssh directory is 700 and the
> authorized_keys file is 600.

That's all good. Check that the owner is correct too.

> Is this possible to be able to do this?

Yes, it works.

> /home/bondbrdg> sftp -v -v -v bondbpex <at> d03ftp101.boulder.ibm.com

This shows no problem. We also need sshd -ddd output from d03ft101.

//Peter
Darren Tucker | 5 Jun 2007 00:11
Picon
Picon

Re: Need to sftp with automatic login from 1 aix machine to another, the id on the target is a DCE(DFS) id

Pat Cornick wrote:
> Hi,
> 
> I had a question and can not find out on the web where anyone might have
> done this.  I am sftping
> between one AIX machine and another using automatic login.  I have created
> the id_rsa.pub on the
> source server and added it to the /.ssh/authorized_keys file on the target
> server.  The problem we
> are having seems to be that because the target id is a DCE(DFS) id and it's
> home directory is
> /fs/home/bondbpex  instead of /home/bondbpex it can't find the
> /.ssh/authorized_keys file.

As long as getpwnam() and friends return the correct home dir that 
should work.

> The
> permissions on the .ssh directory is 700 and the authorized_keys file is
> 600.  Is this possible to be able
> to do this?  Thanks for any help you can give me.

Is the home directory not mounted until the user presents a kerberos 
ticket or a password that can get one?  If so then sshd isn't going to 
be able to read the authorized_keys file in the user's home dir.

What you can do is set AuthorizedKeysFile in sshd_config to point to a 
local filesystem (eg /etc/ssh/keys or something) but that's a 
system-wide parameter so it will affect all users.  It would not be hard 
to make the Match keyword in recent versions support AuthorizedKeysFile 
(Continue reading)

Pat Cornick | 6 Jun 2007 15:25
Picon
Favicon

Re: Need to sftp with automatic login from 1 aix machine to another, the id on the target is a DCE(DFS) id

Hi Darren,

Thanks for your help on this.  We will be changing the id to a local AIX id
to get this to work.
Take care.

Regards,
Pat

                                                                           
             Darren Tucker                                                 
             <dtucker <at> zip.com.                                             
             au>                                                        To 
                                       Pat Cornick/Endicott/IBM <at> IBMUS      
             06/04/2007 06:11                                           cc 
             PM                        openssh-unix-dev <at> mindrot.org        
                                                                   Subject 
                                       Re: Need to sftp with automatic     
                                       login from 1 aix machine to         
                                       another, the id on the target is a  
                                       DCE(DFS) id                         

Pat Cornick wrote:
> Hi,
>
> I had a question and can not find out on the web where anyone might have
> done this.  I am sftping
> between one AIX machine and another using automatic login.  I have
created
> the id_rsa.pub on the
(Continue reading)

Peter Stuge | 7 Jun 2007 18:44

Re: sftp-server with defaultroot

On Mon, May 21, 2007 at 07:36:17PM +0200, Marten Lehmann wrote:
> Why doesn't the openssh sftp-server include this? Are there plans
> to do it? Are there certain reasons not to include?

This functionality needs to be in the shell, since the user's shell
is always used by sshd to execute whatever program is requested.
(Interactive, single command or subsystem.)

See e.g. rssh

//Peter
Damien Miller | 11 Jun 2007 06:43
Favicon

Recent MAC improvements

Hi,

There has been some recent work to improve the speed of the Message
Authentication Codes (MACs) that are used in OpenSSH.

The first improvement is a change from Markus Friedl to reuse the MAC
context, rather than reinitialising it for every packet. This saves two
calls to the underlying hash function (e.g. SHA1) for each packet. My
tests found that this yielded at 12-16% speedup for bulk transfers to
localhost using HMAC-MD5 and arcfour256. HMAC-SHA1 should see an even
bigger improvement, because SHA1 is a more expensive hash function.

The second improvement is Peter Valchev's addition of a new MAC: Ted
Krovetz' UMAC-64[1]. This MAC uses a very different approach than the
HMACs that OpenSSH currently supports, and it comes with a nice security
proof that guarantees its resistance so long as its underlying block
cipher (AES) remains cryptologically intact. Testing (bulk transfers to
localhost using arcfour256) found UMAC-64 to perform 20% better than
HMAC-MD5, and 28% faster than HMAC-SHA1. This new MAC may be selected
by specifying "MACs=umac-64 <at> openssh.com" in a server or client config.

These changes need testing on as many platforms as possible. In particular
we are interested in the following corner cases:

- Old OpenSSL version (0.9.5ish)
- Testing between big and little endian machines (i386 vs. sparc for example)
- Testing between previous OpenSSH versions and -current
- Testing on strict alignment architectures like Alpha and Itanium

Please report your findings to the mailing list.
(Continue reading)


Gmane