frustated

then i try to find some answers to change remote desktop password from terminal by googling, so i found this solution for 8.04 :

- gconftool-2 -s -t bool /desktop/gnome/remote_access/enabled false
- gconf-editor
- paste encode password from: http://www.javazoom.net/services/base64/base64.jsp
- or use:
- gconftool-2 -s -t string /desktop/gnome/remote_access/vnc_password <encode_pwd>
- or use:
- System-> preferences-> Remote Desktop
- set pwd as desired…
- manual text edit of %gconf.xml does not seem to work!
- gconftool-2 -s -t bool /desktop/gnome/remote_access/enabled true
- verify .gconf/desktop/gnome/remote_access/%gconf.xml

but unfortunately the path for Intrepid seems to change, and i’m having this problem when i try to edit the file :

Failure listing entries in `/home/user1/.gconf/desktop/gnome/remote_access’: Bad key or directory name: “/home/user1/.gconf/desktop/gnome/remote_access”: Can’t have a period ‘.’ right after a slash ‘/’

soooo.. lets try to improvise :

locate remote_access
-> /home/user1/.gconf/desktop/gnome/remote_access
vim /home/user1/.gconf/desktop/gnome/remote_access/%gconf.xml

after looking at the %gconf.xml file, i found this line :

<entry name=”vnc_password” mtime=”1242031453″ type=”string”>
<stringvalue>ZW5jb2Rl</stringvalue>
</entry>

interesting…. so i go to HERE to decode the password (or you can find encode/decode function in php or any other programming language, then,Voilaaaa…i have change the remote desktop password then connect again using VNC.

The main issue in my mind now is, if the password is that easy to decode, then if u do have a remote desktop on your ubuntu desktop/server its VERY recomended to increase your level of security, like having firewall installed, change the default port for services installed (SSH,etc2),have a GOOD PASSWORD, and any other securities you can apply to your box.

Although aliases can easily be set up using the alias command, this command has the disadvantage that any alias created with it remains in effect only during the current login session (i.e., until the user logs out or the computer is shut down). This might not be much of a problem for systems that are rebooted (i.e., restarted) only infrequently (such as corporate database servers), but it can be a nuisance for systems that are frequently rebooted (e.g., home computers).

Fortunately, however, any alias can be made more enduring (i.e., until it is explicitly removed) by writing it to the appropriate configuration file with a text editor. The name and location of such file can vary according to the system and the shell. In the case of the bash shell (which is the default shell on

Linux) on Red Hat Linux, an alias for any user can be added to the .bashrc file in that user’s home directory.

Each alias is written in this file exactly the same as it would be written on the command line using the alias command (see The alias Command for examples). Because this configuration file is read at login, any changes to it will not take effect until the user has logged in again or opened a new terminal window (i.e., an all-text window in a GUI).

.bashrc is a hidden file, that is, a file whose name begins with a period and thus is not normally visible in a GUI (graphical user interface). However, it is easy to locate and open from the command line.

Because .bashrc is a plain_text file, it can easily be edited using any text editor, such as vi or gedit. For example, assuming that the user is currently in its home directory, the following could be used to open .bashrc with vi:

vi .bashrc

Likewise, the following could be used to open the same file with gedit:

gedit .bashrc

The alias should be typed in below the line that says # User specific aliases and functions. The pound sign at the start of this line indicates that the line is a comment, i.e., documentation for the convenience of humans rather than something on which the system acts.

Aliases for the root user (i.e., administrative account) can be made permanent by entering them in the .bashrc file in the root user’s home directory (which is /root), i.e., in /root/.bashrc. System-wide aliases can be put in the /etc/bashrc file. (Note that, at least on some systems, /etc/bashrc is not a hidden file.) The system needs to be restarted before system-wide aliases can take effect.

If the unalias command, which is used to remove or suppress aliases, is used on an alias which has been recorded in a .bashrc file, that alias is turned off for the duration of the current login session. However, the alias is not removed from the .bashrc file, and when the user logs in again, that alias is again in effect.

Created August 6, 2005.

Copyright © 2005 The Linux Information Project. All Rights Reserved. http://www.linfo.org/make_alias_permanent.html ]]> http://kriwelz.web.id/blog/permanent-aliases-in-bash-shell/feed/ 2 http://kriwelz.web.id/blog/amarok-with-mp3-support/ http://kriwelz.web.id/blog/amarok-with-mp3-support/#comments Tue, 28 Apr 2009 02:27:49 +0000 kriwelz http://kriwelz.web.id/blog/?p=110 After reinstalling my ubuntu to jaunty (yes, one day earlier i install ubuntu 8.10 then after googling i find out that ubuntu just released 9.04,arrghhh..) i want to burn in my newly bought LG earphone. Then when try to play mp3, amarok doesnt support mp3 for default!

After  searching information for amarok mp3 support (install-mp3) etc etc.. i found out that the easiest way to make amarok support mp3 is install the codec, simply after install amarok

sudo apt-get install amarok

(or u can go to Add / Remove – Sound and Video, tick on the Amarok)

then install the codec :

sudo apt-get install libxine1-ffmpeg

Thats it.. re-run ur amarok, then it should support mp3 now

If only amarok have the equalizer feature, i think it would be more cool