Frederik Pot | 2 Feb 15:59 2007
Picon

simple connection

Hello,

I am Frederik Pot 30 years old and live in Holland.
I want to connect from a realbasic application (on windows) to my linux 
computer on port 22.
I set the firewall off and do a xhost + command on the linux machine.
Then i can connect by tcp on port 22 and see as return something like 
SSH-OPENSSH4.
So there is a sort of connection.........

Well for me it is difficult  to see what to do further......

Setting up a public key ...???

Can you give me some tips on how to communicate with this protocol..

Or is it too difficult  for a simple example ???

Thx for your time

Greetings ,

Frederik Pot

_________________________________________________________________
Windows Live Mail: Slim, Persoonlijk, Betrouwbaar en het blijft natuurlijk 
gratis! http://imagine-windowslive.com/mail/launch/default.aspx?Locale=nl-nl

der Mouse | 2 Feb 16:04 2007
Picon

Re: simple connection

> I want to connect from a realbasic application (on windows) to my
> linux computer on port 22.

> I set the firewall off and do a xhost + command on the linux machine.
> Then i can connect by tcp on port 22 and see as return something like
> SSH-OPENSSH4.
> So there is a sort of connection.........

Right...though "xhost +" has nothing whatever to do with this; X
permissions are completely independent of access to your ssh server.

> Well for me it is difficult  to see what to do further......

> Setting up a public key ...???

> Can you give me some tips on how to communicate with this protocol..

> Or is it too difficult  for a simple example ???

It's too complicated to describe briefly.  See RFCs 4250 through 4254;
they are the spec for the basic protocol.

It will be rather difficult to use ssh directly from BASIC.  Not
impossible, assuming your BASIC supports networking and operations on
binary data, but...well, put it this way: I wouldn't try unless someone
were paying me quite a lot - and that's speaking as someone who's
written an ssh client (not, of course, in BASIC).

Unless you have a good deal of cryptography support available built
into your BASIC system....
(Continue reading)

Frederik Pot | 2 Feb 16:21 2007
Picon

Re: simple connection


Thank you verry much for your reply !!
I really appreciate for answering the email !

Thx for your time...

Greetings ,

Frederik Pot

>From: der Mouse <mouse <at> Rodents.Montreal.QC.CA>
>Reply-To: ietf-ssh <at> NetBSD.org
>To: ietf-ssh <at> NetBSD.org
>CC: Frederik Pot <frederikpot <at> hotmail.com>
>Subject: Re: simple connection
>Date: Fri, 2 Feb 2007 10:04:28 -0500 (EST)
>
> > I want to connect from a realbasic application (on windows) to my
> > linux computer on port 22.
>
> > I set the firewall off and do a xhost + command on the linux machine.
> > Then i can connect by tcp on port 22 and see as return something like
> > SSH-OPENSSH4.
> > So there is a sort of connection.........
>
>Right...though "xhost +" has nothing whatever to do with this; X
>permissions are completely independent of access to your ssh server.
>
> > Well for me it is difficult  to see what to do further......
>
(Continue reading)

Jeffrey Hutzelman | 2 Feb 16:17 2007
Picon

Re: simple connection


On Friday, February 02, 2007 10:04:28 AM -0500 der Mouse 
<mouse <at> Rodents.Montreal.QC.CA> wrote:

> Unless you have a good deal of cryptography support available built
> into your BASIC system....

Heh.  Doing RSA or DH in BASIC would be an interesting challenge, to say 
the least.

der Mouse | 2 Feb 18:11 2007
Picon

Re: simple connection

>> Unless you have a good deal of cryptography support available built
>> into your BASIC system....
> Heh.  Doing RSA or DH in BASIC would be an interesting challenge, to
> say the least.

It wouldn't be difficult, just slow.  I've done IDEA in MUF (a language
rather like FORTH but with all the real elegance ripped out).  I've
also done floating-point in it - in a version which has no native
support for any arithmetic type except machine integers.

Honestly, if I had to do ssh in BASIC, I'd probably build an
interpreter (or perhaps compiler to pcode and then a pcode engine) for
a language better suited to the task and then write the code in that.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse <at> rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

Peter Gutmann | 3 Feb 09:07 2007
Picon
Picon
Picon

Re: simple connection

der Mouse <mouse <at> Rodents.Montreal.QC.CA> writes:
>It will be rather difficult to use ssh directly from BASIC.  Not
>impossible, assuming your BASIC supports networking and operations on
>binary data, but...well, put it this way: I wouldn't try unless someone
>were paying me quite a lot - and that's speaking as someone who's
>written an ssh client (not, of course, in BASIC).

There are a few SSH libs available as Windows DLLs which should be callable
from, well VB anyway, I assume RealBasic is the same.  A google search
for something like "windows dll ssh" should find something.

Peter (author of one of said DLLs :-).

Ben Harris | 17 Feb 22:42 2007
Picon

draft-bjh21-ssh-transport-extension-00

I've just uploaded an internet-draft that would allocate an SSH message 
number to be used for named message types, where the names work like all 
the other names in SSH.  This should make it easier to extend the SSH 
transport layer in ways that need new message types, as it appears might 
be necessary to produce a race-free version of zlib <at> openssh.com.  Named 
packet types aren't right for everything, of course, but they seem 
sensible for packets that are only likely to be sent a few times per 
connection.

What do people think of this idea?

<http://www.ietf.org/internet-drafts/draft-bjh21-ssh-transport-extension-00.txt>

--

-- 
Ben Harris

Jeffrey Hutzelman | 18 Feb 03:00 2007
Picon

Re: draft-bjh21-ssh-transport-extension-00


On Saturday, February 17, 2007 09:42:54 PM +0000 Ben Harris 
<bjh21 <at> bjh21.me.uk> wrote:

> I've just uploaded an internet-draft that would allocate an SSH message
> number to be used for named message types, where the names work like all
> the other names in SSH.  This should make it easier to extend the SSH
> transport layer in ways that need new message types, as it appears might
> be necessary to produce a race-free version of zlib <at> openssh.com.  Named
> packet types aren't right for everything, of course, but they seem
> sensible for packets that are only likely to be sent a few times per
> connection.
>
> What do people think of this idea?
>
> <http://www.ietf.org/internet-drafts/draft-bjh21-ssh-transport-extension-
> 00.txt>

Sounds like a good idea.  I can't find evidence of any reason to restrict 
allocation of transport-level message numbers other than the extreme 
scarcity of the namespace, so opening it up in the way you describe seems 
reasonable.

I think it is probably worth noting that anyone defining a standards-track 
extension requiring a new transport-level message would now have a choice 
as to whether to allocate a new message type number or used a named type. 
This decision would presumably be made on the basis of whether there are 
performance implications which make it a good idea to consume a number.

I think the advice you give in the security considrations section is 
(Continue reading)

der Mouse | 19 Feb 09:30 2007
Picon

Re: draft-bjh21-ssh-transport-extension-00

> [...] a race-free version of zlib <at> openssh.com.

Speaking of which, can anyone point me to docs on the various
 <at> openssh.com names?  Besides zlib <at> openssh.com as a compression method,
I've seen keepalive <at> openssh.com channel requests, and have so far been
unable to find authoritative documentation on either.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse <at> rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

der Mouse | 19 Feb 10:30 2007
Picon

Re: draft-bjh21-ssh-transport-extension-00

> I've just uploaded an internet-draft that would allocate an SSH
> message number to be used for named message types, where the names
> work like all the other names in SSH.

Named *transport-layer* message types, it seems to me.  Or am I
misreading?

> What do people think of this idea?

"Good."  I don't have any immediate use for it (the one new packet type
I'm using more appropriately falls into the "local extension" range
192-255, since it never appears on the wire), but I agree that it's a
very good thing to have.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse <at> rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B


Gmane