10-22-2006, 07:27 PM | #76 |
Connoisseur
Posts: 50
Karma: 861
Join Date: Aug 2006
Device: Zaurus C1000/iLiad/SE K750i
|
Yes. I don't think, that system will waste 4KB, but to check first is a good way for copying key. But the best - to check existance authorized_key, if it exsits, to check that it doesn't contain id_rsa.pub etc. But it was quick way
|
10-22-2006, 09:14 PM | #77 | |
Banned
Posts: 1,300
Karma: 1479
Join Date: Jul 2006
Location: Peoples Republic of Washington
Device: Reader / iPhone / Librie / Kindle
|
Quote:
Did you know scp isn't working? dropbear needs an scp handler to actually do inbound scp... |
|
10-23-2006, 08:14 AM | #78 | |
Guru
Posts: 607
Karma: 2157
Join Date: Oct 2005
Device: NCR3125, Nokia 770,...
|
Quote:
|
|
10-24-2006, 02:05 PM | #79 |
Member
Posts: 18
Karma: 10
Join Date: Jun 2006
|
It sounds like the 2.7.1 patch disables the exploit for the network key. Can anyone confirm this?
|
10-25-2006, 03:49 AM | #80 | ||
Uebermensch
Posts: 2,583
Karma: 1094606
Join Date: Jul 2003
Location: Italy
Device: Kindle
|
Quote:
Quote:
|
||
11-01-2006, 08:49 AM | #81 |
Enthusiast
Posts: 28
Karma: 73
Join Date: Jul 2006
|
Here's another set of scripts that can make your life easier. This also works as a first time setup (2.7 only).
Note: This is using the startup.sh hook from I survived 2.7.1 and the dropbear.tar from earlier in this thread. (1) Attach your iLiad to your PC. Put the content of the dropbear.tar into the root directory, "F:\" or whatever it is on your PC. (2) Create a file named "startup.sh" and put it there, too. Content: Code:
#!/bin/sh # ATTN: Changing this script can brick your iLiad cp /mnt/free/daemon.sh /tmp/daemon.sh chmod 755 /tmp/daemon.sh /tmp/daemon.sh & Code:
#!/bin/sh
if [ ! -d /home/root/.ssh ];then
mkdir /home/root/.ssh
fi
if [ ! -f /home/root/.ssh/authorized_keys ];then
cp /mnt/free/id_rsa.pub /home/root/.ssh/authorized_keys
fi
if [ ! -x /tmp/dropbear ];then
cp /mnt/free/dropbear /tmp
chmod 755 /tmp/dropbear
fi
if [ ! -x /tmp/dropbearkey ];then
cp /mnt/free/dropbearkey /tmp
chmod 755 /tmp/dropbearkey
fi
if [ ! -f /mnt/free/dropbear_dss_host_key ];then
/tmp/dropbearkey -t dss -f /mnt/free/dropbear_dss_host_key
fi
if [ ! -e /mnt/free/dropbear_rsa_host_key ];then
/tmp/dropbearkey -t rsa -f /mnt/free/dropbear_rsa_host_key
fi
touch /mnt/free/newspapers/del_to_start_network.txt
while [ 1 ]
do
sleep 30
if [ ! -e /mnt/free/newspapers/del_to_start_network.txt ];then
touch /mnt/free/newspapers/del_to_start_network.txt
/usr/bin/wired.sh start dhcp
sleep 5
/usr/bin/killall dropbear
/tmp/dropbear -d /mnt/free/dropbear_dss_host_key -r /mnt/free/dropbear_rsa_host_key
fi
done
(5) Disconnect your iLiad from your PC and connect it to your LAN instead. (6) Now on the iLiad; start creating a new connection profile. Choose a WEP protected wireless connection. Name and SID don't matter. When you are asked for the WEP key enter this: Code:
`/bin/sh /mnt/free/startup.sh` (8) While the iLiad is still "Searching", abort the creation of the connection profile. Don't save it, you won't need it anymore. (9) Press the "NEWS" button. There should be a new file called "del_to_start_network.txt". Delete it. After 1 to 30 seconds, the network should become active. 5 seconds later the ssh daemon is started. (10) Use ssh to connect your iLiad. (11) Create a new file "/etc/rc5.d/S99zWHATEVER" (where WHATEVER is whatever you want) and make it executable ("chmod 755 /etc/rc5.d/S99zWHATEVER"). Put in the content from I survived 2.7.1. Content: Code:
#!/bin/sh # ATTN: Changing this script can brick your iLiad if test -f /mnt/card/startup.sh then /bin/sh /mnt/card/startup.sh fi if test -f /mnt/free/startup.sh then /bin/sh /mnt/free/startup.sh fi (13) Execute step 9 and 10 again and notice that every time you delete that file, the wired network becomes active and the ssh daemon is started for you. This should also survive the update to 2.7.1, and may survive 2.7.x, but it's unlikely it'll survive 2.8. Last edited by Henry Loenwind; 11-05-2006 at 09:30 AM. Reason: I had messed up step 11 |
11-01-2006, 11:02 AM | #82 |
Banned
Posts: 1,300
Karma: 1479
Join Date: Jul 2006
Location: Peoples Republic of Washington
Device: Reader / iPhone / Librie / Kindle
|
@Henry Loenwind
An elegant piece or work and excellent documentation. Well done! That said, everyone needs to keep in mind that if you crash your iLiad's boot sequence (er_registery accident, or whatever) this boot up won't work as you won't be able to remove the lock file. But for everyday access to launch dropbear and let you in, an elegant solution. Remember, let's be safe out there. |
11-01-2006, 11:29 AM | #83 | |
Enthusiast
Posts: 28
Karma: 73
Join Date: Jul 2006
|
Quote:
--- Also, someone asked how to install ipdf? Code:
cp /mnt/free/ipdf /usr/bin/ mv /usr/bin/xpdf /usr/bin/xpdf.original ln -s /usr/bin/ipdf /usr/bin/xpdf Problems with step 11? Create the file on your PC, put it onto the iLiad together with the other scriptfile, the type in the following on the iLiad's command line: Code:
cp /mnt/free/S99zWHATEVER /etc/rc5.d/ chmod 755 /etc/rc5.d/S99zWHATEVER |
|
11-05-2006, 03:19 AM | #84 | |
Banned
Posts: 1,300
Karma: 1479
Join Date: Jul 2006
Location: Peoples Republic of Washington
Device: Reader / iPhone / Librie / Kindle
|
Quote:
Code:
#!/bin/sh if test -f /mnt/free/startup.sh then /bin/sh /mnt/free/startup.sh & fi if test -f /mnt/card/startup.sh then /bin/sh /mnt/card/startup.sh fi |
|
11-05-2006, 09:29 AM | #85 | |
Enthusiast
Posts: 28
Karma: 73
Join Date: Jul 2006
|
Quote:
(The daemon.sh is the one that's not exiting. I copy that to /tmp so it won't run from a file system that will be unmounted.) Edit: But I found it makes more sense to check for a startup.sh on the card first, in case the startup.sh in the internal memory was corrupted (bad edit or so). Changed the script and added a warning on the "dangerous" scripts. Last edited by Henry Loenwind; 11-05-2006 at 09:32 AM. |
|
11-26-2006, 04:31 PM | #86 |
iLiad fan
Posts: 210
Karma: 3864
Join Date: Oct 2006
Device: iRex iLiad
|
First: After the .sh extension, much of this is un-necessary. I've created a launcher that launches dropbear (and starts wlan while at it). This is way safer -- no risk of bricking your iliad (at least as far as I know), and better for battery life and security because you don't start dropbear until you are going to use it. If anyone is interested, I can post it here. But first I have to get it working, which leads nicely to the second paragraph:
I can't login. I get "Server refused our key". I've generated a 1024 bit RSA key using Putty (yes, I'm a windowsluser), saved it where it should be etc. Everything seems to be in order, but I still can't log in... Can anyone help me out here? What kind of key do you need to generate? DSA? RSA? Different bit length? Dropbear specific files? |
11-26-2006, 04:49 PM | #87 | |
iLiad fan
Posts: 210
Karma: 3864
Join Date: Oct 2006
Device: iRex iLiad
|
Quote:
So my key file had wrong contents... Will try again tomorrow, out of battery now Anyone else have similar problems with un-clean USB disconnections? Or are everybody but me either using Linux or disconnecting properly (disconnect hardware wizard etc... which I never use -- haven't seen this problem before) |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
A Huge Thank You | BurBunny | Amazon Kindle | 4 | 02-27-2009 01:36 PM |
Adobe Reader 9 new exploit in the wild | doctorow | News | 2 | 02-20-2009 03:38 PM |
Cybook not found in linux, found in win XP | fjf | Bookeen | 15 | 01-18-2008 06:57 PM |
Adobe Acrobat subject to remote exploit | Alexander Turcic | News | 3 | 09-16-2006 05:29 AM |
Serious exploit in Greasemonkey 0.4 | Alexander Turcic | Lounge | 2 | 07-19-2005 04:59 AM |