It runs on a variety of POSIX-based platforms. Dropbear is open source software, distributed under a MIT-style license. Dropbear is particularly useful for "embedded"-type Linux (or other Unix) systems, such as wireless routers.

In this thread I post two essentials pet files.

1. dropbear launcher:

This is my dropbear GUI frontend "dropbear Launcher", includes Server and Client GUI.

I attach the clarf_dropbear-0.52-i386.pet package, I originally made this package for Puppy 214X. It was compiled as multi-binary (one binary and some symlinks) and I got a small package, after many tests...

For this package I used (of course with a pair of tricks I learned from ttuuxxx):

I have a quick question for you. Is the SSH client GUI just a front-end for the SSH command already present in Puppy (and nearly every other *nix), or does it include its own implementation? In other words, if we don't need a server, is downloading the GUI package enough?_________________Be brave that God may help thee, speak the truth even if it leads to death, and safeguard the helpless. - A knight's oath

I have a quick question for you. Is the SSH client GUI just a front-end for the SSH command already present in Puppy (and nearly every other *nix), or does it include its own implementation? In other words, if we don't need a server, is downloading the GUI package enough?

HI SirDuncan,

This is a front-end for dropbear Server/client, then it wrappers dropbear commands that are not compatible with SSH. Conclusion, GUI package is not enough you need additionally the dropbear package (that indeed is really small). But not additional library or dependencies are needed after dropbear package is installed.

Note: The GUI package "Dropbear Launcher" already includes the trayicon application and needed libraries that are used for Server GUI.

/usr/bin/ssh and /usr/bin/scp conflict with those on OpenSSH. Those in Dropbear are not compatible. There are some scripts that use ssh and maybe scp, so if Dropbear is installed, they will stop working.

OpenSSH is still going to be needed, so Dropbear cannot be considered as a replacement in Puppy, but as an alternative where a little matching server/client is needed.

However, the utilities will all have to have different names from those in OpenSSH so as not to conflict. Unlike Busybox, Dropbear cannot launch its applets by "dropbear ssh <options>", so that is out.

The only thing I can think of is that ssh and scp symlinks be placed somewhere not in the executable search path._________________http://bkhome.org/news/

You are right OpenSSH full replacement is not really intended... You can just drop those simlynks (ssh and scp ) or move them to other locations from dropbear package in favor of OpenSSH tools, and still have full client/server functionality (with a nice GUI) in a small package.

The only really necessary symlinks for Server/Client functionality are dbclient and dropbear files, to use my GUI frontend you need trayicon (and one library) to launch, stop and monitor Server Status.

I compiled the full multibinary set because OpenSSH tools were damaged for 214X and can`t be used anymore, but the OpenSSH libraries were keeped for compatibility/dependency reasons, dropbear in fact is a good replacement for 214X or inclusive other thin pups that dont want to use (or cannot use) ssh, ssh-agent or ssh-keygen tools. Barry you can accommodate this packages for Puppy needs..

Thinking loud, I believe that giving the right order to the PATH environment variable could solve those problems too. i.e, put /usr/bin/ before /usr/local/bin path then OpenSSH tools will be found and used first.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum