Smilgs linux tools ASE scripts (installing bash, dropbear, mc, nano, opkg)

[Guest Smilgs]

Hello all.

During setting up a workable SSH connection to my Android (with all tools needed),

I created some scripts + resources using ASE (Android Scripting Engine) for installing:

• bash (.bashrc included with terminfo and path settings)
  (from http://forum.xda-developers.com/showpost.p...amp;postcount=4 )
  
• dropbear (generates dss and rsa keys, generates a random password in /data/local/dropbear/passwd
  (from http://android.modaco.com/content/htc-hero...om/294137/sshd/ )
  
• mc (unfortunately has weird exceptions)
  (from http://android.modaco.com/content/htc-hero...-coming-to-mcr/ )
  
• nano (changed to not wrap long lines and not add newlines to the end of files edited using a forwarder)
  (from http://android.modaco.com/content/software...or-for-android/ )
  
• opkg (this would be the preferred method to install mc - unfortunately does not work for me because of some MD5 issue)
  (from http://android.modaco.com/content/htc-hero...-coming-to-mcr/ )
  
  • Additional scripts:
    
  • start/stop dropbear
    
  • mount /system RW/RO
    

  !!! if you don't know what any of the above is, the scripts are most probably not for you)

  The scripts & installed tools should work from Hero and Desire - actually should work from other devices but I have only tested these two.

  Also I have tested only on Modaco ROMs, based on 2.1.

  All files are installed to /data, binaries / shell scripts to /data/xbin

  To run the scripts, you need to

  [*]extract http://girts.niedra.org/wordpress/wp-content/uploads/ase.zip into the root of /sdcard

  [*]install ASE from http://code.google.com/p/android-scripting/

  [*]launch ASE, chose the right script and click on it

  P.S.1. If installing nano and mc and plan to run from within sh (not bash), then run this prior:

export TERM=linux

export TERMINFO=/etc/terminfo

P.S.2. Also sharing the following cmd script that initiates port forwarding and launches putty SSH connection to Android (useful to connect using cable). Must edit the cmd to point to the actual location of putty, and adb.exe must be in PATH for it to work. I used the following putty connection: localhost. port 2222, auto-login-username=root, specified private key for authentication, and remote command "/data/xbin/bash --rcfile ~/.bashrc" (if you want to use bash instead of the default sh)

adb forward tcp:2222 tcp:2222

pthtoputty\putty.exe -load "android"

Edited July 4, 2010 by Smilgs