/dev/random

I had a pretty interesting tease tease – I had to create a huge number of randomly generated passwords as I was required to be of a certain length to contain large lowercase letters and numbers, normal things. Sounds easy, doesn't it?. I used /dev/urandom for the main generation and then with a short pipeline I filtered to the desired number of characters and types of characters to be used. As long as I'm screwed into the main script is the pipeline :

cat /dev/urandom | tr -dc '[:alnum:]' | fold -w 20| head -n 1

So let's take a closer look at what's going on here. We take the output of cat / dev / urandom. Then we filter it to show only small ones, capital letters and numbers. Then with fold we limit the length of the strings to the desired number. Finally, we limit the display only 1 row of the entire output. Basically easy as 1-2-3. If you want to increase the complexity of the password and with special characters in the regular expression of tr can be used :graph: or :print: instead :scooping:, which include all characters without or with space.

cat /dev/urandom | tr -dc '[:graph:]' | fold -w 20 | head -n 1
Enhanced by Zemanta

My Debian people are still dirty with addictions. Ie they did not stain them but lost the ia32-libs package which is in the dependencies of skype. I will not comment on why they are in dependencies given that it is x64 version 😉 So in the end there are several applications that are directly deleted due to the removal of this package. For better or worse, I can't do without them, that the package needs to be restored. The easiest option is to add a testing repository and give priority to it in general is this in is so much again this 😀 The steps below look at the system when we have already updated it and ia32-libs is no more.

1. Добавяме testing хранилище или wheezy- това е кодовото име на следващия stable Debian. В /etc/apt/source.list добавете ред който изглежда по подобен начин

deb http://debian.ludost.net/debian/ wheezy main contrib non-free

2. Даваме приоритет на testing пакетите над тези на unstable хранилищата тъй като към момента пакета все още го има там. Създаваме файлът /etc/apt/preferences.d/apt (това си е лично мой избор) може да е в /etc/apt/preferences вместо /etc/apt/preferences.d/ и му добавяме следното съдържание

Package: *
Pin: release a=testing
Pin-Priority: 1010

3. apt-get update за да обнови новите хранилища и приоритети. Смъквате си skype на ново които към момента е версия 4.0.0.8.1 and install it dpkg and then fix the missing packages

dpkg -i skype-debian_4.0.0.8-1_amd64.deb

apt-get install -f

 

In general, this is a procedure for forcibly downloading versions of packages, but I have used it only for those for which I need you can later give priority to ia32-libs ia32-libs-gtk lib32v4l-0 to be downloaded only from the testing feeder.

English: This is a side view of the read head ...

Yesterday I had to boot a Windowds virtual machine NTFS my share. To my great surprise, the machine started dragging an awful lot when virtualbox started creating its virtual HDD. WFT ??? Immediately a quick top and the problem shone. ntfs-3g was crashed on 100% cpu usage 3 of my 6 cores. Hmmm foreign. After a contemplation in the following line, the problem shone through

/sbin/mount.ntfs-3g /dev/sda4 /media/disk1part4 -o rw

Obviously / dev / sda4 is mounted with default options only. In general, the ntfs driver has dirt with intensive writing and reading on the partition if it is not provided with some miraculous settings.

  1. big_writes – the most important option to drop the load intensity of your system using large block recording.
  2. noatime – speeds up the system by disabling inode updates access time if we don't need it. Personally, I don't need it at all
  3. windows_names – there is no acceleration here but on the other hand the file names are treated according to the MS conventions in which the file names, regardless of whether they are uppercase and lowercase, are the same.

After I fixed the options with which my partition is installed fstab the record looked like this

UUID=2213f519-f980-42bf-9e25-9201db38c458  /media/disk1part4  ntfs-3g  defaults,big_writes,windows_names,noatime 0 0

Enhanced by Zemanta

I had noticed for some time that it had stopped working for me gnome shell weather extension-and we. In general, he muttered that it was not an up-to-date version of my version of Gnome Shell. Strange because I updated it by updating my gnome shell version. Then I dropped it, because it's not a pain to die and I still have time to delve into such small mistakes. But today I decided it was high time I stopped doing this and fixed my miracles. I updated the git tree to the latest version, I installed a new one – no change. WTF. Then I hit him with a make uninstall and something shocking came up, the add-on was still disabled as not updated, and I had uninstalled it. In general, at this point I assumed that it is installed in some other folder for extensions and therefore makes a cut. From now on, things unfold in the following scenarios. Find the name of the add-on, find the add-on and remove. Getting the names of the installed add-ons in the gnome shell is done with the following command

gsettings get org.gnome.shell enabled-extensions

From whose outcome I understood, that I have activated an add-on named [email protected] Fun. The nice thing in this case is the name of the add-on folder and you can easily locate the location with the command

find / -name '[email protected]'

Here things have become easy. From the output of the find I understood, that it has in 2 papaki. A quick rm -rf of the 2 folders and everything fell into place. A quick installation of the add-on and restart of the gnome shell.

Enhanced by Zemanta

It came out a few days ago XAMPP 1.8.0 yesterday after upgrading from version 1.7.7 I had a pretty interesting problem. Phpmyadmin-а не ми се отваряше и изгърмяваше със 403

Access forbidden!


New XAMPP security concept:

Access to the requested object is only available from the local network.

This setting can be configured in the filehttpd-xampp.conf”.

Веднага отворих httpd-xampp.conf който при мен се намира в /opt/lampp/etc/extra/, на пръв поглед всичко изглеждаше наред. The LAN rules were fine. Apart from opening from localhost. WTF ??? I looked at the log and saw that my access was cut off from the configuration. Тука вече нещата ме ахнаха и честно казано донякъде малко на късмет открих проблема. След като преглеждах httpd.conf-а видях в Allow/Deny клаузите един последен ред Require all granted. О да еврика. This is the new control mechanism that has entered apache 2.4.x. It gives access or denies access to all required, it generally mimics the Allow / Deny functionality :). To fix the problem add Require all granted in the / opt / lampp / phpmyadmin folder directives. After the changes, it looks like this to me

<Directory “/opt / lampp / phpmyadmin”>
AllowOverride AuthConfig Limit
Order allow,deny
Allow from all
Require all granted
</Directory>

 

Viangi can try other savages, for example to rename the phpmyadmin folder to something else and make an alias to no. But it's uglier and not very meaningful 🙂

p.s I was asked why I use XAMPP and not a clean installation of all components as my Debian gave birth to them – the answer is very very simple – LAZINESS. I'm too lazy to write a few commands and then touch my conf and so on. It is much easier to download the whole package, unzip and burn 😉

Enhanced by Zemanta