This one might just spare you about 2-3 hours of your time doing SVN+SSH kdesvn googling. One would think it would work out-of-the-box, but it doesn’t. To get kdesvn to work with SSH, there is one small undocumented trick – using an environment variable (as if you were using command line SVN+SSH). To do that, put the following line into your .bashrc:

If you try using SVN+SSH without it, kdesvn will try to login to remote server using your current username (the one you are using on your local machine). Of course, each time unsuccessfully because it’s not the right username. After that, go to Subversion->General->Checkout a repository, and enter:

…in the URL field. Also, choose the target directory and check any other desired options. After that, just bookmark the connection and you’re all set up.

Problem with using GEdit (v2.30.4 in the moment of writing this post) for FTP browsing/editing under KDE (if you don’t have Nautilus installed in your KDE) is that since it is a GNOME app – you need a way to somehow manage your connections which is usualy done through Nautilus by using GNOME bookmarks (the ones you would create by going to Places -> Connect to Server) and at the moment there is no way to create this bookmarks from within GEdit.

Anyway, you can do the same thing by editing .gtk-bookmarks file located in your home folder even if you don’t have Nautilus installed. Here’s a few examples of what you can put inside:

The first one is just a regular FTP login bookmark. The second one uses a different port than the default one. The third one is for usernames containing @ (like in the image below) which you have to replace with %40 to differentiate them from @ for domain association. The fourth one uses the folder_path_option like in picture below and the fifth one is for using sFTP. Of course, you can combine all this together depending on your needs…

Browsing/editing directly from GEdit is much faster than using Filezilla which prompts for uploading every time after you edit and save the file which is kinda annoying, or for example using Krusader which works well with FTP, but if you use sFTP – then it edits files localy instead of online so you have to save them as a new file and upload them again… You get the drift.

They’re quite cheap, and you can probably find one in your local electronics supply store for the price of about 5-8€. You could also get one for a very small price on eBay… After acquiring one, the question is – which application to use with PS gamepad? I found QJoyPad to work pretty well – it’s easy to configure and it will automaticaly recognize your gamepad, so that’s one less thing for you to worry about. Just get it from your distros repositories (or if you’re out of luck – get the source code and compile it by yourself).

I configured it for some basic desktop maneuvering. For example so that I could command VLC from my bed not having to get up each time to turn the volume up or down, or if I want to rewind a part of a video, put some music on, read email… This is how I configured the buttons, perhaps it will help:

Holding “shift” or “ctrl” buttons + “left” or “right” keyes is for rewinding videos, L2 and R2 buttons are for volume… You can even set zooming in your Compiz to work with ctrl+alt+left/right – so you could zoom in read all this tiny letters from a distance (for example if you want to choose a song in your favorite audio player or whatever). You also get “space” for pausing multimedia…

I also wanted to use analog stick instead of a mouse, but it was just too fast and too responsive in the beginning. But, what you can do is you can also set its sensitivity and treshold up to suit your needs. You’ll need some time to get used to clicking around with analog but it gets easier after aiming at everyones forheads during a few movies. :D

Sometimes after booting the machine up I would just get no sound in my browser / video player and sometimes it would be there working just perfectly. The only way to get the sound if it wasn’t there was to reboot the computer. A strange issue I ignored at first thinking it would go away after a few full system updates, but after a while the problem was still there and I got annoyed by it and thankfully found a cure.

The problem was the usb webcam. Turns out ALSA isn’t very smart when it comes to device assignment so sometimes it would make the snd_usb_audio (webcam) the first sound device instead of the soundcard. A workaround is just putting your soundcard module name before the snd_usb_audio in your /etc/rc.conf. In my case it was like this:

edit: I think there is one more situation when sound does not work – it’s when your skype autostarts on startup. It starts webcam of course and sometimes skype starts before you can hear the welcoming sound of entering into your WM.

What you will also need is GNU screen installed on the remote server. So, what is screen? “Screen is a full-screen window manager that multiplexes a physical terminal between several processes, typically interactive shells.” Basically what you can do with it is that you can run certain processes and put them into the background (detach from them), and than later see them again (attach to them) when you want to. If you don’t know how to use screen, take a look here, or use google to find a tutorial on using screen. There is plenty of them out there. You will need screen to put the running irssi into the background on your server so that you may disconnect from the remote server after you set irrsi up.

So, after you have got your irssi configured and running under screen, you will have to load the proxy plugin for irssi, set a password for your future pidgin-to-irssi connection and bind one free port to irssi for sharing server connection. Here is how to do it:

where the parameter is a network name you configured earlier, and

Edit your .xinitrc and add the following line before the exec part:

Also, uncomment the following line in /etc/hibernate/common.conf

After you suspend to disk, vlock will lock all virtual terminals and sessions and again later after unsuspending will it prompt you for your username and password.

Execute the following in your terminal as root:

and then replace “en” layout with the one you need (in my example hr):

I couldn’t find the option in nautilus preferences to get the left pane appear. I also couldn’t find the solution through google, but somehow managed to get it working. So, here is it:

1. Run gconf-editor
2. Go to: /apps/nautilus/preferences
3. Check the "always_use_browser" option

There you go, happy browsing.

Pozivamo sve zainteresirane na radionicu o sigurnosti bežičnih mreža koja će se održati u nedjelju u prostoru Udruge obitelji poginulih hrvatskih branitelja iz Domovinskog rata – Osijek. Radionicu će održati članovi Hrvatske udruge Linux korisnika Osijek u suradnji s Klubom Info Junior.

Teme su sljedeće: Legalni aspekti napada na WEP i WPA enkriptirane bežične mreže, lažna sigurnost pri filtriranju MAC adrese (postavljanje lažne MAC adrese), praćenje i sniffing prometa, cracking WEP-om zaštićene pristupne točke sa i bez klijenta te WPA cracking.

Svrha radionice je edukacija kako bi se uvidjelo koliko je današnja tehnologija ranjiva te kako sami možete što bolje zaštititi svoje bežičnu mrežu i podatke. Želimo potaknuti sve da razmisle o nesavršenosti sustava koji se danas koriste te čiju “sigurnost” uzimaju zdravo za gotovo. Najlakši način obrane je poznavanje nedostataka i ranjivosti onoga što koristimo.

Molimo one koji posjeduju vlastita prijenosna računala da ih ponesu sa sobom na radionicu kako bi i pomoću njih, ukoliko podržavaju packet injection, mogli odraditi praktični dio radionice. Onima koji su zainteresirani za radionicu, ali nisu toliko upoznati s ovim područjem, a kako bi lakše pratili teorijski dio te lakše sudjelovali u praktičnom dijelu radionice, preporučamo da pročitaju ponešto o ovim temama na nekim od sljedećih linkova:

MAC adresa
WEP enkripcija
WPA enkripcija
Probijanje WEP zaštite
Cracking WEP i WPA bežične mreže

Sniffing prometa ili analiza paketa

Također, kako bismo se mogli prostorno organizirati, molimo sve zainteresirane da se prijave za radionicu slanjem e-maila pod naslovom “WEP/WPA cracking radionica” na adresu info@linux-osijek.org This e-mail address is being protected from spambots. You need JavaScript enabled to view it ili da se prijave na ovom threadu našeg foruma. Ukoliko se pokaže veliki interes za ovu temu, radionica će se ponoviti kako bi ju svi zainteresirani mogli odslušati.

First of all, download and burn the backtrack image to a CD, and then reboot to your live CD.
Login as root and download the installer which I found somewhere on the web, and then start it…
(If the installer opens in your browser and shows just a bunch of code, make a new file and name it BT3.kmdr an c/p the code into that file and then run the file)

You’ll get this window:


There are a few things that need setting up:
Source (BackTrack CD) – leave this as it is.
Install BackTrack to – put a name of the partition you want to use for BackTrack installation.
Write new MBR (lilo.mbr) to – also leave this as it is.
Installation method – set to “Real”.
I use GRUB instead of LILO, so I had to check “Restore Original MBR after lilo”.

After the installation has finished, boot to your main distribution and edit GRUB
Add the following lines to your GRUB:

If you wish to login to console instead of KDE, use the following:

Keep in mind that root (hd0,5) will probably be different for you since we almost sure don’t have the same partition order.

If you liked the fancy bootsplash from the live cd, you’ll have to make it work for your installation first.
If you used the GRUB options for KDE, when the GRUB boots, navigate to “BackTrack3 KDE” and pres “e” to temporarily edit the GRUB only for this one session so you can enable the bootsplash. Then delete the initrd line with “d”, and also edit (with “e” again) the kernel line to look like showed in “BackTrack3 console”.
After that, boot to BackTrack and run the following command in your terminal as root:

and reboot.

There you go, you’re ready to use BackTrack3.