SpeedTouch THOMSON ST5x6v6 - Administrador Novis

Administrador novis dos Speedtouch THOMSON ST5x6v6, e possivelmente outros equipamentos:

NovisSU : n0v!5

Apenas necessário para login via telnet, e mesmo assim possivelmente o utilizador admin é suficiente para efectuar todas as alterações pretendidas.

Webmin Modules - Pure-FTPD

The latest version (0.55) of this third-party module has a typo, that renders the users display a nightmare, with users inside users inside users...
The official package, here, doesn't seem to be maintained anymore, and I didn't find a way to contact them to fix this, so I leave you with a patch for those of you who already have it, a the package with this fixed.
patch
pureftpd.wbm

source

Twinkle: USB Headset Microphone (Fedora/Linux)

My usb heaset (Halfmman Cobra HS-87, which are the same as the ozone oxid) worked perfectly in my Fedora Core 13 (2.6.34.7-63.fc13.x86_64) KDE 4.5.3, both output(speakers) as well as the input(microphone). That was until I've tried to use it with twinkle.
Didn't have any problems getting it to work in skype, just plugged it in and it was automatically detected and added to the system.
Went to System Settings -> Multimedia -> Phono and could see it there. Gave it higher priority over the other devices, and after that it worked perfectly in my system.

The problem appeared when I tried to use it in twinkle, though I could ear perfectly, it wasn't using my headset's microphone, instead it was using my laptop's.

Since I use pulse audio (default in Fedora) I noticed that twinkle uses directly alsa. So after a litle search (not so little) I came across this thread, and it saved me =)

Since I only needed the micro to work, I created the following .asoundrc in my home directory:


pcm.usb_in {
type pulse
device alsa_input.usb-04d9_0020_832R-00-U0x4d90x20.analog-mono
hint {
description "halfmman Cobra Micro"
}
}


To find the device value use:
pactl list
And search for the device you want, which in my case was: alsa_input.usb-04d9_0020_832R-00-U0x4d90x20.analog-mono.

After that open twinkle -> Edit -> System Settings -> Audio

On the Microphone select ALSA: other device
and on the other device field put: usb_in

It should be working now!

Fedora: Java JRE from SUN (64 Bit)

This was shamelessly "stolen" and adapted from backtrack forum

System

Fedora release 13 (Goddard)

Linux shinigami 2.6.34.7-61.fc13.x86_64 #1 SMP Tue Oct 19 04:06:30 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux



Download the .bin file

sudo sh jre-6u22-linux-x64-rpm.bin

sudo update-alternatives --install "/usr/bin/java" "java" "/usr/java/jre1.6.0_22/bin/java" 1

sudo update-alternatives --set java /usr/java/jre1.6.0_22/bin/java

sudo ln -s /usr/java/jre1.6.0_22/lib/amd64/libnpjp2.so /usr/lib64/mozilla/plugins/

Restart Firefox



kde - network manger plasmoid and wpa-wpa2

I had a problem connecting to my enterprise wireless network. They use WPA-WPA2 Enterprise with TTLS authentication and PAP as inner authentication.

I use the plasma widget of network manager, running on kubuntu 10.04

I figured it was a problem with reading/parsing the certificate file, from my syslog i got this message:

Aug 5 10:31:46 namikaze wpa_supplicant[848]: OpenSSL: tls_connection_ca_cert - Failed to parse ca_cert_blob error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag

I got on-line...with other means =)

and got to this bug report:

Bug 209673 - knetworkmanager applet (NOT THE PLASMOID) can't connect to WPA PEAP when validating by CA certificate

Well...they do say it's not related to the plasmoid...but i figured it should be similar...

They say it has something to do with network manager not feeding the certificate to the wpa_supplicant in the correct form/way (comment #21).

I've tried their workaround (comment #25)...well i failed...

~ #cat cacert.pem | grep -v "CERTIFICATE" | base64 -d > cacert.dem
base64: dados de entrada inválidos

so I thought to use openssl to convert the certificate to dem:

openssl x509 -in cacert.pem -outform der > cacert.dem

...and that did work!

I've just changed the configuration of the network...to point to the new certificate....and that actually did the trick =)