Re: Introducing BlueMaemo
 

Unfortunately, the BlueTooth applet in Intrepid's GNOME is a bit broken. Intrepid just came out, so expect some rough edges to be fixed. If you know what package the KDE program you're using is in you could install that package on Ubuntu and use this applet in Ubuntu's GNOME.

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

In a file called btnit.sh
Then chmod this +x
And put this on the desktop or in ~/bin

Then you can easily make it work.

Re: Introducing BlueMaemo
 

Thanks it works !

i didn"t get the double dash !!

Re: Introducing BlueMaemo
 

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.

Re: Introducing BlueMaemo
 

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.

Re: Introducing BlueMaemo
 

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..

Re: Introducing BlueMaemo
 

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.

Re: Introducing BlueMaemo
 

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.

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).

Re: Introducing BlueMaemo
 

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.

Re: Introducing BlueMaemo
 

Aha. Then, ssh -v to the host, and check what it says. Or read the syslog on the sshd host.

Re: Introducing BlueMaemo
 

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.