Active Topics
-
The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 11 hrs, 32 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 7 hrs ago - more...
 |
|
2008-11-02
, 18:31
|
|
Posts: 17 |
Thanked: 2 times |
Joined on Sep 2008
@ France
|
#162
|
Thanks it works !
i didn"t get the double dash !!
i didn"t get the double dash !!
|
|
2008-11-02
, 21:08
|
|
Posts: 17 |
Thanked: 2 times |
Joined on Sep 2008
@ France
|
#163
|
IT IS ANSOME !
here is my script on my computer :
next i add the following line with visudo:
for the next section you need ssh on tablet, computer with keys working (so ssh can connect without password but with secure keys)
i run on my tablet :
and now i can connect on my computer without touch it 
so fun
Thanks guys.
here is my script on my computer :
Code:
#!/bin/bash sudo hidd --connect 00:XX:XX:XX:XX:XX
Code:
myuser ALL = NOPASSWD: /usr/bin/hidd
i run on my tablet :
Code:
]sudo bluemaemo & sleep 10 && ssh myuser@mycomputer_ip /home/myuser/software/scripts/bluemaemo.sh
so fun
Thanks guys.
| The Following 2 Users Say Thank You to Kytrix For This Useful Post: | ||
 |
|
2008-11-02
, 21:43
|
|
Posts: 3,397 |
Thanked: 1,212 times |
Joined on Jul 2008
@ Netherlands
|
#164
|
Good one.
Here is a guide to set up SSH RSA keys (don't have to contain a password, but that is recommended). You have to set this up on the NIT.
I suppose some people use Windows or MacOS X on their computer. It'd be interesting if there are some command line utilities for setting this up remotely on these OSes. A guide like the one by Kytrix is appreciated.
Here is a guide to set up SSH RSA keys (don't have to contain a password, but that is recommended). You have to set this up on the NIT.
I suppose some people use Windows or MacOS X on their computer. It'd be interesting if there are some command line utilities for setting this up remotely on these OSes. A guide like the one by Kytrix is appreciated.
__________________
Goosfraba! All text written by allnameswereout is public domain unless stated otherwise. Thank you for sharing your output!
Goosfraba! All text written by allnameswereout is public domain unless stated otherwise. Thank you for sharing your output!
|
|
2008-11-03
, 03:15
|
|
Posts: 4,556 |
Thanked: 1,624 times |
Joined on Dec 2007
|
#165
|
I've never been able to get past this step.
ssh-copy-id -i ~/.ssh/id_rsa.pub username@host
I've tried the command both from the server (my tablet using username@host being my laptop or desktop). And vice versa my laptop or desktop to the server (thus username@host being my tablet). Neither works..
ssh-copy-id -i ~/.ssh/id_rsa.pub username@host
I've tried the command both from the server (my tablet using username@host being my laptop or desktop). And vice versa my laptop or desktop to the server (thus username@host being my tablet). Neither works..
__________________
Originally Posted by ysss
They're maemo and MeeGo...
"Meamo!" sounds like what Zorro would say to catherine zeta jones... after she slaps him for looking at her dirtily...
|
|
2008-11-03
, 09:17
|
|
Posts: 17 |
Thanked: 2 times |
Joined on Sep 2008
@ France
|
#166
|
you have to clean on server files .ssh/authorized_keys and authorized_keys2 if never used before
in state of ssh-copy-id you can scp your key.pub from client to .ssh/ on server
then connect on server and do : cat key.pub > authorized_keys
sometimes it's authorized_keys2
on the client do cleaning in .ssh/know_hosts .. duplicate keys can doing mess.
.. try to connect and look at /var/log/auth.log on server
on client do ssh -vv user@server and look messages
you can also try a DSA key by : ssh-keygen -r dsa
first times it's sometimes not easy to get it works, but after it works like a charm !
Kytrix.
in state of ssh-copy-id you can scp your key.pub from client to .ssh/ on server
then connect on server and do : cat key.pub > authorized_keys
sometimes it's authorized_keys2
on the client do cleaning in .ssh/know_hosts .. duplicate keys can doing mess.
.. try to connect and look at /var/log/auth.log on server
on client do ssh -vv user@server and look messages
you can also try a DSA key by : ssh-keygen -r dsa
first times it's sometimes not easy to get it works, but after it works like a charm !
Kytrix.
|
|
2008-11-03
, 12:33
|
|
Posts: 3,397 |
Thanked: 1,212 times |
Joined on Jul 2008
@ Netherlands
|
#167
|
Kytrix you are using > this means the file is erased. You need to use >> in case the user already made her own authorized_keys. In general, one doesn't have to delete these unless one knows what one is doing.
Originally Posted by Laughing Man
On the NIT you create your key. Then you copy this to your server (with scp or ssh-copy-id). Then you add the content to ~/.ssh/authorized_keys. Then you might have to enable public key authentication in the server SSHd: make sure PubkeyAuthentication is set to yes in /etc/ssh/sshd_config and restart SSHd with /etc/init.d/ssh restart (might differ a bit per OS but in general this is the way to Rome).
I've never been able to get past this step.
ssh-copy-id -i ~/.ssh/id_rsa.pub username@host
I've tried the command both from the server (my tablet using username@host being my laptop or desktop). And vice versa my laptop or desktop to the server (thus username@host being my tablet). Neither works..
__________________
Goosfraba! All text written by allnameswereout is public domain unless stated otherwise. Thank you for sharing your output!
Goosfraba! All text written by allnameswereout is public domain unless stated otherwise. Thank you for sharing your output!
|
|
2008-11-03
, 23:44
|
|
Posts: 4,556 |
Thanked: 1,624 times |
Joined on Dec 2007
|
#168
|
Hmm, not sure if it's using it though (Pubkeyauthentication is set to yes in the ssdh_config).And I did copy the key (though manually by hand over [opened text editors for both and copied and pasted]. I just don't know if it's actually using it or not.
__________________
Originally Posted by ysss
They're maemo and MeeGo...
"Meamo!" sounds like what Zorro would say to catherine zeta jones... after she slaps him for looking at her dirtily...
|
|
2008-11-04
, 00:45
|
|
Posts: 3,397 |
Thanked: 1,212 times |
Joined on Jul 2008
@ Netherlands
|
#169
|
Aha. Then, ssh -v to the host, and check what it says. Or read the syslog on the sshd host.
__________________
Goosfraba! All text written by allnameswereout is public domain unless stated otherwise. Thank you for sharing your output!
Goosfraba! All text written by allnameswereout is public domain unless stated otherwise. Thank you for sharing your output!
|
|
2008-11-04
, 04:00
|
|
Posts: 4,556 |
Thanked: 1,624 times |
Joined on Dec 2007
|
#170
|
Code:
vforviktor@vendetta-laptop:~$ ssh user@192.168.1.104 -v -p 666 OpenSSH_5.1p1 Debian-3ubuntu1, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 192.168.1.104 [192.168.1.104] port 666. debug1: Connection established. debug1: identity file /home/vforviktor/.ssh/identity type -1 debug1: identity file /home/vforviktor/.ssh/id_rsa type -1 debug1: identity file /home/vforviktor/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7p1 Debian-12.maemo2 debug1: match: OpenSSH_4.7p1 Debian-12.maemo2 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-3ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host '[192.168.1.104]:666' is known and matches the RSA host key. debug1: Found key in /home/vforviktor/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Trying private key: /home/vforviktor/.ssh/identity debug1: Trying private key: /home/vforviktor/.ssh/id_rsa debug1: Trying private key: /home/vforviktor/.ssh/id_dsa debug1: Next authentication method: password
I'm guessing that it's not working since it's trying the next authentication method?
And on a sidenote: Bah, stupid Vista. I uninstalled the drivers for my bluetooth dongle, and now it won't reinstall.
__________________
Originally Posted by ysss
They're maemo and MeeGo...
"Meamo!" sounds like what Zorro would say to catherine zeta jones... after she slaps him for looking at her dirtily...
Or follow this procedure: first, install the package bluez-compat using your package manager. Now, put BlueTooth on the N810 visisble. Then use hcitool to scan. After you got the BlueTooth address, write it down (in case for usage next time). Now use hidd to connect.
One could put something like
Then chmod this +x
And put this on the desktop or in ~/bin
Then you can easily make it work.
Goosfraba! All text written by allnameswereout is public domain unless stated otherwise. Thank you for sharing your output!