Solution:

wrap around your js code with {literal} {/literal}

Example:

{literal}

<script type=”text/javascript”>

var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-XXXXX-X']);
_gaq.push(['_trackPageview']);

(function() {
var ga = document.createElement(’script’); ga.type = ‘text/javascript’; ga.async = true;
ga.src = (‘https:’ == document.location.protocol ? ‘https://ssl’ : ‘http://www’) + ‘.google-analytics.com/ga.js’;
var s = document.getElementsByTagName(’script’)[0]; s.parentNode.insertBefore(ga, s);
})();

</script>

{/literal}

Options -Indexes

So here we are on how to update default gateway using command line:

netsh interface ip add address “local area connection” gateway=100.1.1.5
gwmetric=2

grep can simply be invoked: $ grep ‘STRING’ filename

This is OK but it does not show the true power of grep. First this only looks at one file. A cool example of using grep with multiple file would be to find all files in a directory that contains the name of a person. This can be easily accomplished using a grep in the following way :

$ grep ‘Nikesh J’ *

Notice the use of single quotes; This are not essential but in this example it was required since the name contains a space. Double quotes could also have been used in this example.

Grep Regular Expression

grep can search for complicated pattern to find what you need. Here is a list of some of the special characters used to create a regular expression:

`.’ The period `.’ matches any single character.

`?’ The preceding item is optional and will be matched at most once.

`*’ The preceding item will be matched zero or more times.

`+’ The preceding item will be matched one or more times.

So an example of a regular expression search would be: $ grep “\<[A-Za-z].*” file

This will search for any word which begins with a letter upper or lower case.

For more details check: $ man grep

[root@server /root]# date
Thu Sep 20 11:00:06 CDT 2001
[root@server /root]#

If your timezone is correct but the date and/or time needs updating, the following commands will update the date and time. The second command is needed in order to push the date and time into the PC clock.

[root@server /root]# date 092011082001
Thu Sep 20 11:08:00 CDT 2001
[root@server /root]# hwclock --utc --systohc
[root@server /root]#

You are who you hang around with, at least that is the way it is on the internet. If your site is on Green Tea and you keep linking to mountain dew, then your site is considered to be about dew, not tea to most search engines.

If you have a site that links to websites considered bad by search engines, you will be penalized and may not recover for years – at that point, you might as well start another site.

So what does this have to do with hidden code inside wordpress themes? The hidden code can contain links to inappropriate sites or worse, code that fetches links from a main server that are then placed on you site without your knowledge!

So, what do you look for when evaluating a wordpress theme? Start with the footer.php file and look for code like this:

<?php eval(gzinflate(base64_decode(’rZFNT8MwDIbP66+wcmCbBM3YBYml2QG4I4a
049Ru7oeUJlGc0u3f06wbaB2ICzk4ih0/r/NmKSOxqz5gq1KihOXGeHTsp+TG730oZA647
GMEIKycbKcwn80eQCxtaSFTpqh0biZjndY4ni5gKeNoNLrRGdnFRcwapRbX+e6ySKF0mCd
syHRE803jVM9l8kV7VyHB5G21mgqeyn9T2pq6Ru1pM5R8OhW+NQW3wYvLFQneefibk/f
ByrN06b195Ny6Svt4ryl2DZNrzOAZqSp0kIDsAFcSQ8C5td9D2y2QNZqMw10g3P3NOA5B/q
CwQ3AmX7/O/RjONEXpe9iwt23buLW+xBopd4hx5yFn4CuvMGFr43bWIRG8H290Txxkgk
J88u34HRF8Ag==’)));?>

Looks odd, doesn’t it? If not, then you need to step away from the computer right now

If you take this code, replace eval with print and place it in a file on your server called testme.php, you will see the hidden code. After you have created the file, access it by typing your websiteaddress/testme.php and then choose view source from your browser. Behold, the hidden code revealed. In the example above, the hidden code equates to something like this:

?>
<div class=”footer”>
<div class=”footer_txt”>
<br /><br />
<p>(c) 2007 <?php bloginfo(’name’); ?>.
<a href=”<?php bloginfo(’rss2_url’); ?>”>Entries (RSS)</a>.
<a href=”<?php bloginfo(’comments_rss2_url’); ?>”>Comments (RSS)</a></p>

</div>
<div class=”footer_txt1″>
<a href=”http://badsite. com”>Inappropriate Text</a> by Bad Site</a>.
</div><?php>

So next time you decide to use a free wordpress theme, make sure you check the theme files BEFORE you place it on your site! If there is encrypted code and it’s released under the GPL License (most are), then there should never be any need for encryption!

So after a little while I felt that I need msn to chat. Browsing the web the choice was done quickly by installing aMSN. Works fine with me. To tell the truth, I didn’t try camera and voice function, but the rest is fine.

So getting back to the topic. There are articles in the internet saying that there are better mp3 players that xmms. But taking in to the consideration the fact that I’m experienced MS user, so that it won’t changed my mind just like that.

sudo apt-get install xmms -didn’t work

Spending a bit more time on reading I’ve found a useful note that xmms has been replaced with audacious.

So what i did it was

sudo apt-get install audacious

Audacious looks very friendly and common for me. Hope this was useful.

1. RedHat 9. For that matter, you should not install any of the “classic” RedHats. They’re old and outdated. If you want commercially supported, look at RHEL. For free RedHat-like distributions, look at CentOS (Server) and Fedora Core (Workstation). If you run a RedHat 9 server that faces the internet, there is a good chance you will get rooted. It is NOT supported for security or otherwise.
2. Telnetd. [Edit: several people have pointed out that I did not make it clear if I meant the server or the client.  The telnet client is quite useful, it is the server that introduces many security concerns.] Telnet is unencrypted and unsecure. Would you send your credit card number over an unencrypted link? Then why send your passwords? SSH can do everything Telnet can, and more. SSH can do file transfers, encrypt other connections, compress your data stream, and allow you to connect without typing a password. Oh, and there are SSH clients for just about every system on earth, so no worries about incompatibilities.
3. rsh, rlogin, etc. The authentication mechanisms in rsh and rlogin can easily be defeated. Oh, and they use plaintext too, so everything that applies to Telnet applies here as well.

I can think of several more items, but these are the biggest for security. And while you’re configuring the SSH server, don’t forget to turn root logins off with “PermitRootLogin no”.

< Permissions and ownership – why? >

If you can’t access some of the files on your very own Linux system, it’s usually because of misconfigured file access permissions. If you are the only user on your Linux box, you may be wondering what’s the point of having all these permissions (or lack thereof) that restrict your access to your very own penguin OS. However, before pulling your hair off, you must keep in mind Linux is designed to be a multi-user environment. In an environment with more than one users, it is crucial to have a secure system for deciding which files are yours and who can fiddle with them.

Even if you’re the only user on an ordinary desktop system, file permissions help keeping your important files safe, both from outsiders and your own mistakes.

< Understanding file ownership >

Every file on your Linux system, including directories, is owned by a specific user and group. Therefore, file permissions are defined separately for users, groups, and others.

User: The username of the person who owns the file. By default, the user who creates the file will become its owner.

Group: The usergroup that owns the file. All users who belong into the group that owns the file will have the same access permissions to the file. This is useful if, for example, you have a project that requires a bunch of different users to be able to access certain files, while others can’t. In that case, you’ll add all the users into the same group, make sure the required files are owned by that group, and set the file’s group permissions accordingly.

Other: A user who isn’t the owner of the file and doesn’t belong in the same group the file does. In other words, if you set a permission for the “other” category, it will affect everyone else by default. For this reason, people often talk about setting the “world” permission bit when they mean setting the permissions for “other.”

< Understanding file permissions >

There are three types of access permissions on Linux: read, write, and execute. These permissions are defined separately for the file’s owner, group and all other users.

Read permission. On a regular file, the read permission bit means the file can be opened and read. On a directory, the read permission means you can list the contents of the directory.

Write permission. On a regular file, this means you can modify the file, aka write new data to the file. In the case of a directory, the write permission means you can add, remove, and rename files in the directory. This means that if a file has the write permission bit, you are allowed to modify the file’s contents, but you’re allowed to rename or delete the file only if the permissions of the file’s directory allow you to do so.

Execute permission. In the case of a regular file, this means you can execute the file as a program or a shell script. On a directory, the execute permission (also called the “search bit”) allows you to access files in the directory and enter it, with the cd command, for example. However, note that although the execute bit lets you enter the directory, you’re not allowed to list its contents, unless you also have the read permissions to that directory.

< How to view file permissions >

You can view the access permissions of a file by doing the long directory listing with the ls -l command. This is what a long directory listing might look like:

me@puter: /home/writers$ ls -l

total 17

drwxr-xr-x 3 nana writers 80 2005-09-20 21:37 dir
-rw-r—– 1 nana writers 8187 2005-09-19 13:35 file
-rwxr-xr-x 1 nana writers 10348 2005-07-17 20:31 otherfile

What does the output of ls -l mean? The very first column, the one that looks like a bunch of mumbo jumbo, shows the file type and permissions. The second column shows the number of links (directory entries that refer to the file), the third one shows the owner of the file, and the fourth one shows the group the file belongs to. The other columns show the file’s size in bytes, date and time of last modification, and the filename.

The first column, the one that shows the file’s permissions and looks like mumbo jumbo, is organized into four separate groups, although it certainly doesn’t look very organized.

The first group consists of only one character, and it shows the file’s type. For example, d means a directory and – means a normal file, so if you take a look at our example output, you’ll notice dir is a directory, while file and otherfile are regular files.

The first character can be any of these:

d = directory
- = regular file
l = symbolic link
s = Unix domain socket
p = named pipe
c = character device file
b = block device file

The next nine characters show the file’s permissions, divided into three groups, each consisting of three characters. The first group of three characters shows the read, write, and execute permissions for user, the owner of the file. The next group shows the read, write, and execute permissions for the group of the file. Similarly, the last group of three characters shows the permissions for other, everyone else. In each group, the first character means the read permission, the second one write permission, and the third one execute permission.

The characters are pretty easy to remember.

r = read permission
w = write permission
x = execute permission
- = no permission

What does this mean in practice? Let’s have an example. Remember the imaginary directory listing we did at the beginning? The output looked like this:

drwxr-xr-x 3 nana writers 80 2005-09-20 21:37 dir
-rw-r—– 1 nana writers 8187 2005-09-19 13:35 file
-rwxr-xr-x 1 nana writers 10348 2005-07-17 20:31 otherfile

As we already noticed, dir is a directory, because the first column begins with a d. The owner of this directory is user nana and the group owner is writers. The first three characters, rwx, indicate the directory’s owner, nana in this case, has full access to the directory. The user nana is able to access, view, and modify the files in that directory. The next three characters, r-x, indicate that all users belonging to group writers have read and execute permissions to the directory. They can change into the directory, execute files, and view its contents. However, because they don’t have write permissions, they can’t make any changes to the directory content. Finally, the last three characters, r-x, indicate that all the users who are not nana or don’t belong into group writers, have read and execute permissions in the directory.

How about file? Because the first column begins with a -, the file is a regular file, owned by user nana and group writers, just like the directory in our example. The first three characters, rw-, indicate the owner has read and write access to the file. According to the next three characters, r–, the users belonging to group writers can view the file but not modify or execute it. The final three characters, —, indicate no one else has any access to the file.

Similarly, you can see otherfile is a regular file and its owner has full access to it, while everyone else can read and execute the file but not modify it.

< How to set file permissions – symbolic mode >

You can set file permissions with the chmod command. Both the root user and the file’s owner can set file permissions. chmod has two modes, symbolic and numeric.

The symbolic mode is pretty easy to remember. First, you decide if you set permissions for the user (u), the group (g), others (o), or all of the three (a). Then, you either add a permission (+), remove it (-), or wipe out the previous permissions and add a new one (=). Next, you decide if you set the read permission (r), write permission (w), or execute permission (x). Last, you’ll tell chmod which file’s permissions you want to change.

Let’s have a couple of examples. Suppose we have a regular file called testfile, and the file has full access permissions for all the groups (long directory listing would show -rwxrwxrwx as the file’s permissions).

Wipe out all the permissions but add read permission for everybody:

$ chmod a=r testfile
After the command, the file’s permissions would be -r–r–r–

Add execute permissions for group:

$ chmod g+x testfile
Now, the file’s permissions would be -r–r-xr–

Add both write and execute permissions for the file’s owner. Note how you can set more than one permission at the same time:

$ chmod u+wx testfile
After this, the file permissions will be -rwxr-xr–

Remove the execute permission from both the file’s owner and group. Note, again, how you can set them both at once:

$ chmod ug-x testfile
Now, the permissions are -rw-r–r–

As a summary, have a look at this quick reference for setting file permissions in symbolic mode:

< How to set file permissions – numeric mode >

The other mode in which chmod can be used is the numeric mode. In the numeric mode, the file permissions aren’t represented by characters. Instead, they are represented by a three-digit octal number.

4 = read (r)
2 = write (w)
1 = execute (x)
0 = no permission (-)

To get the permission bits you want, you add up the numbers accordingly. For example, the rwx permissions would be 4+2+1=7, rx would be 4+1=5, and rw would be 4+2=6. Because you set separate permissions for the owner, group, and others, you’ll need a three-digit number representing the permissions of all these groups.

Let’s have an example.

$ chmod 755 testfile
This would change the testfile’s permissions to -rwxr-xr-x. The owner would have full read, write, and execute permissions (7=4+2+1), the group would have read and execute permissions (5=4+1), and the world would have the read and execute permissions as well.

Let’s have another example:

$ chmod 640 testfile
In this case, testfile’s permissions would be -rw-r—–. The owner would have read and write permissions (6=4+2), the group would have read permissions only (4), and the others wouldn’t have any access permissions (0).

The numeric mode may not be as straightforward as the symbolic mode, but with the numeric mode, you can more quickly and efficiently set the file permissions. This quick reference for setting file permissions in numeric mode might help:

You can change the owner and group of a file or a directory with the chown command. Please, keep in mind you can do this only if you are the root user or the owner of the file.

Set the file’s owner:
$ chown username somefile
After giving this command, the new owner of a file called somefile will be the user username. The file’s group owner will not change. Instead of a user name, you can also give the user’s numeric ID here if you want.

You can also set the file’s group at the same time. If the user name is followed by a colon and a group name, the file’s group will be changed as well.
$ chown username:usergroup somefile
After giving this command, somefile’s new owner would be user username and the group usergroup.

You can set the owner of a directory exactly the same way you set the owner of a file:
$ chown username somedir
Note that after giving this command, only the owner of the directory will change. The owner of the files inside of the directory won’t change.

In order to set the ownership of a directory and all the files in that directory, you’ll need the -R option:
$ chown -R username somedir
Here, R stands for recursive because this command will recursively change the ownership of directories and their contents. After issuing this example command, the user username will be the owner of the directory somedir, as well as every file in that directory.

Tell what happens:

$ chown -v username somefile
changed ownership of ’somefile’ to username

Here, v stands for verbose. If you use the -v option, chown will list what it did (or didn’t do) to the file.

The verbose mode is especially useful if you change the ownership of several files at once. For example, this could happen when you do it recursively:

$ chown -Rv username somedir
changed ownership of ’somedir/’ to username
changed ownership of ’somedir/boringfile’ to username
changed ownership of ’somedir/somefile’ to username

As you can see, chown nicely reports to you what it did to each file.

< chgrp – change the group ownership of a file >

In addition to chown, you can also use the chgrp command to change the group of a file or a directory. You must, again, be either the root user or the owner of the file in order to change the group ownership.

chgrp works pretty much the same way as chown does, except it changes the file’s user group instead of the owner, of course.
$ chgrp usergroup somefile
After issuing this command, the file somefile will be owned by a user group usergroup. Although the file’s group has changed to usergroup, the file’s owner will still be the same.

The options of using chgrp are the same as using chown. So, for example, the -R and -v options will work with it just like they worked with chown:

$ chgrp -Rv usergroup somedir
changed group of ’somedir/’ to usergroup
changed group of ’somedir/boringfile’ to usergroup
changed group of ’somedir/somefile’ to usergroup

chown nicely reports to you what it did to each file.