World: r3wp

Kaj, can you see, if it's a SSL implementation or just SSH? Or is 
SSL there by automatic, when making SSH implementations?

There is hardly any talk of SSL, but of the separate authentication 
methods that it comprises. Indeed, SSH implies what is called SSL, 
so it's in there in some form

Thanks!

It could be completely entangled with the SSH protocol, but since 
they also do SFTP, one can hope it is somewhat abstracted internally

SFTP is basically nothing more than a set of specific commands sent 
over SSH.

That alone won't require much abstraction, I fear.

Ah, right, so it could still be entangled. I was thinking of FTPS

AFAIK, SSL and SSH are different communication protocols that rely 
on common hashing and encryption algorithms on the low-level layer.

Yes, it doesn't seem to be called SSL within SSH, but there is talk 
of TLS

Didn't PuTTY also do telnet/ssl?

Hmm, seems it doesn't.

Well, then there's probably hardly anything SSL/TLS-specific in there, 
except for some common crypto primitives as Doc mentioned.

There is a "telnet.c" in the PuTTY sources.

I have just bricked my Sheevaplug by doing a simple "apt-get upgrade"...:-(

No way to get access to it anymore even using the USB direct connection.

So I need to find a suitable ARM emulator now to be able to finish 
the ARM port...

No warranty?

Seem to be several howtos on how to unbrick a sheevaplug

Warranty: I don't think that warranties apply on "bricked" hardware, 
anyway, I never rely on warranties.

I will see if I can setup QEMU to emulate an ARM and install a suitable 
Linux image over it.

Can not be reflashed ?

http://myubuntublog.wordpress.com/tag/sheevaplug/

Yes it can, but the procedure is long and complicated. It also requires 
a USB stick that will be recognized by the sheeva.

I can't get the QEMU network emulation to work at all...

Just spent my whole day trying to make QEMU work fully, I'm giving 
up that option for now. I will try tomorrow to get my sheeva back 
to life.

Never trust update systems

I've been working on a GoboLinux upgrade for the past days after 
nuking my installation, and there are all sorts of problems

Got networking partially working with QEMU, let's see if it's enough 
to setup the tools I need.

Kaj: you got a message here: https://gist.github.com/1326101

Got my QEMU/ARM Debian instance working properly now. I am using 
WinSCP to automatically transfer the compiled binary files between 
the host and guest OS.

green lights for Red !!

I am trying more Red examples from Kaj's bindings.  Some working 
well.... but GTK failing on libgio-2.0-0.dll   Other DLLs that were 
needed for WinXP seemed to be in the mysql distribution ... except 
this one.     Little hits on reliable downloads of pre-built DLL. 
  Anybody used it in WinXP?

I've uploaded a zipped copy of mine: http://sidl.fr/tmp/libgio-2.0-0.zip

merci

But, I have tested it on Seven only...

Soon on XP

Cascading DLL problems ... libglib*....  Can you provide the full 
DLL list that works with GTK?

Let me find that...

Here's the direct download link for the GTK runtime I'm using: http://freefr.dl.sourceforge.net/project/gtk-win/GTK%2B Runtime Environment/GTK%2B 2.22/gtk2-runtime-2.22.0-2010-10-21-ash.exe

Mike, I got the DLL versions for Windows from the official Windows 
download from the GTK site

Although it may just have been followed up by a newer version

I have 2.22.1-20101227 here

Nope, still the same bundle on the site

There are individual packages for the new 2.24, though, which replaces 
2.16 as the stable Windows version

Thanks there is no guarantee that I am doing it right but I am anxious 
to get it working. Thanks for the help guys.

Nice. All examples now  working now except GTK-widgets

With empirical debugging, this line passes the compile but make sthe 
execution fail  "fixed button [50 25  "Print"  :get-lines lines] 
gtk-tight"

Yes ... lots of those in the example ... it is the last one ... commented 
out and the executable does not fail.

How does it fail?

GTK-widgets.exe has encountered a problem and needs to close.  We 
are sorry for the inconvenience.