How-To Recover password under Ubuntu

If you forgot you password for your ubuntu system you can recover using the following steps Turn your computer on.
Press ESC at the grub prompt.
Press e for edit.
Highlight the line that begins kernel ………, press e
Go to the very end of the line, add rw init=/bin/bash
press enter, then press b to boot your system.
Your system will boot up to a passwordless root shell.
Type in passwd username
Posted by at No comments:

How to set grub 2 password protection

  1. Introduction to Grub 2 Basic Password Protection
    • This is basic password security. The username/password are unencrypted; anyone having physical access to the machine and more than an elementary knowledge of how Linux works will be able to access the configuration files and bypass this feature. Encrypted password protection is on the horizon and available in an experimental version of Grub 2 (see “The Future” section below).
    • Grub 2 can set password protection on specific menuentries and for specific users. For example, “John” can access Ubuntu but not the Windows recovery mode, which is only accessible by “Bill”, the superuser.
    • Automatic password protection has not yet been automated. Menuentries must be identified manually by editing the Grub 2 /etc/grub.d/ scripts such as 10_linux and 30_os-prober.
    • If password protection is enabled, even if for only one entry, and even if not for the superuser, the superuser name and password are required to gain access to the Grub 2 command line and menu-editing modes.
    • The username and/or password do not have to be the same as the Ubuntu logon name/password.
    Password protection in Grub 2 is still being developed and its behavior may change in future updates. In this guide, when the term “Grub 2″ is used it refers to the version of Grub 2 (grub-pc) available in the main Ubuntu repository. This is currently 1.97~beta4-1ubuntu4. Any time Grub 2 is updated, the user should note whether their password protection is still working as expected. These instructions are primarily for 1.97~beta. Advanced capabilities such as encrypted passwords which have been introduced in Grub 1.98 are still being worked on. Some of the advancements work well while others do not. The version of Grub found in Karmic is not expected to be updated to 1.97 or 1.98, although significant bugs will be fixed when possible.
  2. How It Works
    • To enable basic password protection, the user/administrator must add a superuser (and other users if desired) and password(s) to the /etc/grub.d/00_header file and manually designate which menuentries require a password in the /etc/grub.d/ files.
    • The Grub 2 menu can include both password-protected and non-protected entries.
    • Once the password feature is enabled the Grub 2 menu will appear as it does normally. When a selection requiring a password is required, the user will be prompted to enter the correct username and password. If entered correctly, the selected menuentry will continue to boot. If incorrect, the user will be returned to the Grub 2 menu.
    • If Grub 2 is set up to boot directly to a password-protected menuentry without displaying a menu, the username/password prompt will appear and booting will not occur until they are correctly entered.
    • Here is a sample menu with passwords enabled, provided by one of the Grub 2 developers:
      • user1 is the designated superuser. This user can boot any menuentry, edit items in the Grub 2 menu during boot, and use the Grub 2 command line.
      • Anyone can boot GNU/Linux
      • Only user2 and the superuser can boot Windows in this example.

      set superusers="user1"
password user1 password1
password user2 password2

menuentry "GNU/Linux" {
set root=(hd0,1)
linux /vmlinuz
}

menuentry "Windows" --users user2 {
set root=(hd0,2)
chainloader +1
}
  3. Warnings & Cautions
    • Errors in creating a password-protected Grub 2 menu may result in an unbootable system. To restore a system with broken passwords, access and edit the Grub 2 configuration files using the LiveCD or another OS.
    • If password protection is enabled, only the designated superuser can edit a Grub 2 menu item by pressing “e” or use the command line by pressing “c”.
    • Caution: If Grub 2 is set up to boot automatically to a password-protected menuentry the user has no option to back out of the password prompt to select another menuentry. Holding the SHIFT key will not display the menu in this case. The user must enter the correct username and password. If unable, the configuration files will have to be edited via the LiveCD or other means to fix the problem.
  4. Setting Up Password Protection
    1. Superuser & Password Designation (Required)
      2. A superuser must be designated. This superuser can access any menuentry, edit the menuentries in the Grub 2 menu by pressing “e”, or invoke the Grub 2 command line mode. Add the following the bottom of /etc/grub.d/00_header 
      cat << EOF
set superusers="user1"
password user1 password1
EOF
      Example: 
      cat << EOF
set superusers="superman"
password superman 1234
EOF
    2. Other Users (Optional)
      3. Other users can be identified and given a password. A designated user can access unprotected and his/her own menuentries. Add the following the bottom of /etc/grub.d/00_header 
      cat << EOF
set superusers="user1"
password user1 password1
password user2 password2
EOF
      Example: 
      cat << EOF
set superusers="superman"
password superman 1234
password bill 5678
EOF
    3. Designating Menuentries for Password Protection
      • Password protect all Linux kernels on the main partition: /etc/grub.d/10_linux (approximately line 59):
        • From: 
        menuentry "$1" {
To allow the superuser only:
        menuentry "$1" --users user1 {
        Example to permit access by only the superuser (superman): 
        menuentry "$1" --users superman {
        Example to permit access by the superuser (superman) and bill: 
        menuentry "$1" --users bill {
      • Password protect the memtest86+ option: /etc/grub.d/20_memtest[/B] (approximately line 27). Make the change as described in the /etc/grub.d/10_linux section above.
        • menuentry "Memory test (memtest86+)" --users superman {
        Additional memtest86+ entries (from other partitions) may also be located in this file. The line will start with “menuentry”. Change these lines as desired.
      • Password protect kernels/operating systems on other partitions: /etc/grub.d/30_os-prober. Make the change(s) as described in the /etc/grub.d/10_linux section above.
        • Linux entries on other partitions (approximately line 136): 
        menuentry "${LLABEL} (on ${DEVICE})" --users superman {
        Other Operating Systems, including Windows (approximately line 100): 
        menuentry "${LONGNAME} (on ${DEVICE})" --users superman {
        OSX entries (in the macosx) section, approximately line 156): 
        menuentry "${LONGNAME} (on ${DEVICE})" --users superman {
      Once the superuser/other users and their password(s) are established, the entries to be protected must be identified. Currently Grub 2 adds no password protection to any entries upon establishment of a superuser and password in /etc/grub.d/00_header. (Note: This may change. See “The Future” section below.) Each menuentry must be identified and modified. Scripts can be used to tailor entries for specific menuentries. See the “Scripts” section for examples. The remainder of this section will explain how to change the main script files in /etc/grub.d/ to set up password protection for entire classes of menuentries (Linux on the main partition, OSs on other partitions, memtest86+, etc). Remember that editing the /boot/grub/grub.cfg file directly is discouraged. For protecting specific menuentries, another option is to add entries to the /etc/grub.d/40_custom file and disable the applicable script file in the same folder. For example, copy the Windows entries from /boot/grub/grub.cfg to 40_custom, add “–users user1″ to the desired entry (such as the Windows recovery partition) and then remove the executable bit from /etc/grub.d/30_os-prober. Save the files, run “sudo update-grub”, and reboot.
    There are three steps to enabling Grub 2 password protection. The user must set up the authorized users, designate the password(s), and identify the password-protected menuentries in the /etc/grub.d/ scripts.
  5. Protecting All Entries
    • The way Grub 2 assigns password protection may change. Currently the default is for menuentries to be unlocked. The developers are considering making the passwords mandatory for all entries once a superuser is designated. The superuser would then be able to unlock entries. If this feature is incorporated in the Ubuntu version of Grub 2 I will update these instructions.
    • The first two ccommands make backups of the files to be modified.
    • filename(s) should be replaced by the specific script file names you wish to change. These files are located in /etc/grub.d/ and include 10_linux, 20_memtest86+, and 30_os-prober. You can include one or more in the commands.
    Grub 2 password protection is still evolving. Currently password protection must be assigned to each menuentry. Protecting the entire menu from editing can be accomplished by adding the superuser and password without designating a specific menuentry. For now, there is no automatic method in Grub 2 to password-protect every menu item. At some point it is expected that this feature will be incorporated in grub-mkconfig. For now this can be accomplished by running the following command(s). Before rebooting make sure you have added the “superuser” and password to etc/grub.d/00_header and inspect /boot/grub/grub.cfg to ensure you achieved the desired results. Notes: 
    sudo mkdir /etc/grub.d.backup
sudo cp /etc/grub.d/* /etc/grub.d.backup
sudo sed -i -e '/^menuentry /s/ {/ --users user1 {/' filename(s)
    Example: 
    sudo sed -i -e '/^menuentry /s/ {/ --users superman {/' /etc/grub.d/10_linux  /etc/grub.d/20_memtest86+ /etc/grub.d/30_os-prober /etc/grub.d/40_custom
    To undo the previous command, run: 
    sudo sed -i -e '/^menuentry /s/ --users user1 {/ {/' filename(s)
    Example: 
    sudo sed -i -e '/^menuentry /s/ --users superman[/B] {/ {/' /etc/grub.d/10_linux  /etc/grub.d/20_memtest86+ /etc/grub.d/30_os-prober /etc/grub.d/40_custom
    Save the files, run “sudo update-grub”, and reboot. At the Grub 2 menu, you will be presented with the normal menu. When you make a selection, a prompt will ask for the username and password.
  6. Examples
    1. Determine the Windows Recovery partition (sda1, sda2, etc).
    2. Add the desired username and password as described in Section 4A and 4B to /etc/grub.d/00_header.
    3. Open /etc/grub.d/30_os-prober for editing:
      4. cd /etc/grub.d/
sudo cp 30_os-prober 30_os-prober.bak # Make a backup copy
sudo chmod -x 30_os-prober.bak        # Remove executable bit
gksu gedit 30_os-prober &
      Change the following (approximately line 100) From: 
      cat << EOF
menuentry "${LONGNAME} (on ${DEVICE})" {
EOF
      To: 
      if [ ${DEVICE} = "/dev/sdXY" ]; then
cat << EOF
menuentry "${LONGNAME} (on ${DEVICE})" --users user1 {
EOF
else
cat << EOF
menuentry "${LONGNAME} (on ${DEVICE})" {
EOF
fi
      Example setting protection on sda2 for user superman: 
      if [ ${DEVICE} = "/dev/sda2" ]; then
cat << EOF
menuentry "${LONGNAME} (on ${DEVICE})" --users superman {
EOF
else
cat << EOF
menuentry "${LONGNAME} (on ${DEVICE})" {
EOF
fi
    4. Save the file, then run:
      5. sudo update-grub
    Password Protect the Windows Recovery Partition Note: See the Grub 2 Title Tweaks thread if you want to remove the Windows Recovery option from the menu entirely. You can use the same concept on other menuentries. Rather than using the partition designation {DEVICE}, you could use other unique identifying variables, such as . The title variable depends on the operating system. Examples include {LONGNAME} or {LLABEL}.
  7. Password Encryption
    • Encrypted password protection using PBKDF2 is available but for me still a bit buggy in Lucid (Grub 1.9. If you are going to experiment with encrypted passwords, make sure you have at least one good non-password protected menuentry to boot or you may not be able to log on if you encounter problems. To generate an encrypted password:
      • grub-mkpasswd_pbkdf2
      The format for an encrypted password entry in /etc/grub.d/00_header would look similar to: 
      set superusers="drs305"
password_pbkdf2 drs305
    • Note: I have been able to get the password function to work in Grub 1.98-20100128 only by using the console mode. With the default gfxmenu mode I have been experiencing hang-ups at the Grub 2 menu. I recently filed this bug report.
      • To enable the console mode, use this line in /etc/default/grub: GRUB_TERMINAL=console
Posted by at 3 comments:

How To Reset Windows Password Using Ubuntu

I have a funny experience. Few days ago, my senior (at my office) ask me to change his computer password (Windows XP Professional). He said, "...please tell me how to change my password. Just tell me the way and I'll change the password by myself...". When I asked him the reason, his answer is "...so you can't use my computer anymore..." :D
Yesterday, he called me. "...panoet, do you know my new password?..." and of course "NO" is my answer. "...Why you ask to me? Yesterday you've changed your password. Right?...". Guess, what his answer?
"I've forgotten my new password!"! LOL, I think. Yesterday you want to change your password so I can't use your computer and know you ask me the password because you've forgotten your new password. Is it sounds silly, right?
Have you ever experienced anything like that? Lost your Windows password? If you have, how to fix that?

How to reset your Windows password?

To reset your Windows password is very easy, as easy as resetting your Ubuntu password. What you need is bootable Ubuntu system (ie. USB, CD or anything) and software called chntpw.
This is step-by-step to reset your Windows password:
  1. Boot from your bootable device (Ubuntu Live Session)
    2. Shutdown your computer and boot up using your bootable system. So you run Ubuntu on Live Session that means you run your system without install it!
  2. Set your repository
    3. Goto Synaptic Package Manager → Settings → Repositories → Ubuntu Software and check the "Software restricted by copyright or legal issues" checkbox. And don't forget to reload synaptic.
    setting repository synaptic package manager
  3. Install CHNTPW
    4. Install from Synaptic Package Manager or use this command on shell: 
    sudo apt-get install chntpw
  4. Resetting Windows password
    • Mount your "Windows installed" device
      • It's depending on your system, example: 
      sudo mkdir /media/WINDOWS
sudo mount /dev/sda1 /media/WINDOWS
      On my system Windows installed on /dev/sda1 and I want to mount it to /media/WINDOWS that I've created before.
    • Goto your Windows system configuration folder
      • Located at [WINDOWS_DEVICE]/WINDOWS/system32/config/: 
      cd /media/WINDOWS/WINDOWS/system32/config/
    • Cracking the SAM file
      • There a SAM file on Windows system configuration folder. That's the file we're looking for. Let's crack it :) (sounds cool) 
      chntpw SAM
      And if you see the output similar with image below, it's mean you can crack the SAM file.
      reset windows password using chntpw
      As you see, there is 5 choices. Just type "1" and press "ENTER" to reset your password.
      Note: I've try this on my system and work well! But I've never try another choices (2-4) yet, you can try yourself.
DONE!!! It's easy, right? But if you've more easy step to reset Windows password, you can share here :)
Posted by at 1 comment:

How to reset forgotten Ubuntu password

Login as root

There is two possible ways to login as root :

* Common method

You can login with root mode just by pressing ESC button when system starting up. That’ll take you to Grub Screen, when you can select mode that you’ll be used while booting. If you have double OS or more on your system (dual boot), you don’t need to do this step. It’s automatically go to Grub Screen when system starting up.

Then choose the “recovery mode”, usually found right below your default option. Press enter, and at the next screen, choose “drop to root sheel prompt” and you’ll login to the system as root :)
* Advanced method

On some system, maybe you can’t find “recovery mode” on Grub Screen menu. So? You need to do a “little hack” to the Grub Loader. Looks cool right? In fact its very easy :)

On Grub Screen menu, select default loader (first choice) and press “E” key that means you’ll edit manually that loader. Wow :)
On the next screen, find row that contains this word :

ro quiet splash

Then replace that with this :

rw init=/bin/bash

After that, press “CTRL”+”X” (or maybe “B” key on your system, depend to your kernel) to boot the system with “hacked” loader :)

Done! You’re logged in as root on your system now, and you can do anything you want. Including resetting your password!
Resetting your password

Use this command to reset your password :

passwd [username]

Fill username with username that you want to reset its password. You’ll prompt new password twice.

In this step, you’re almost done! Now, make sure the change you’ve made will be written to disk by :

sync

Reboot your system :

reboot -f

You’re done! Your password has been reset, and you can login to your system now :)

I’ve been using this method on my Ubuntu Lucid system and its work. I hope this post is useful for you all. If you have problem when implementing this article, leave a comment and I’ll be glad to help you.
Posted by at No comments:

connect to local server share location command

"sudo mount //server/share /tmp/smb/ -t cifs -o username=user,password=password"
Posted by at No comments:
Command to find bluetooth device from command line in UBUNTU

hcitool scan

Sending file to bluetooth device from command line

gnome-obex-send -d $device /path/to/file

NAME
obexpushd - receive files with OBEX protocol via Bluetooth, IrDA or
network connection

SYNOPSIS
obexpushd [-B [[[address]:]channel]] [-I[app]] [-N [[[address]:]port]]
[-p file] [-a file] [-r file] [-s file] [-n | -d] [-h | -v]

DESCRIPTION
obexpushd is a program that can be used to receive files using OBEX
(OBject EXchange) protocol over Bluetooth, IrDA or network connection.
It can be used to receive files from mobile phones and other devices.

When run without -d or -n options obexpushd puts itself to the
background and starts to listen for incoming connections via Bluetooth
(default) and/or IrDA and/or network connection(TCP). obexpushd saves
all received files to it´s current directory but can alternativly
forward all received data to a script for further processing.

OPTIONS
-B
Listen to Bluetooth connections. It is possible to specify an
address of a local adapter and a channel number to listen to.
Default is to use channel 9. The address can be either a bluetooth
adapter interface name (e.g. "hci0"), only the number of that
interface (e.g. "0") or the interface address enclosed in brackets
(e.g. "[11:22:33:44:55:66]").

-I
Listen to IrDA connections on the default inbox and, in addition
and optionally, to the inbox identified by app (example: IrXfer)

-N
Listen to network connections. If compiled with TcpOBEX support
(openobex > 1.3), it is possible to specify an address and a port
number to listen to (default: *:650). Note that to bind to the
default TCP OBEX port, you need root priviledges. The address can
either be an IPv4 address in quad-dot-notation (e.g. "127.0.0.1"),
an IPv6 address enclosed in brackets (e.g. "[::1]") or a "*" as
alias for "[::]".

-p
Write the process ID of the daemon to file

-a
Read user:password pairs from each line of file. Note that many
client cannot handle authentication and will stop working when
using this option. A realm of "obexpushd" will be sent to the
client. Note that no encoding is used, the plain byte sequence will
be matched. The user identifier must not be longer than 20 bytes
and the password must not be longer than 128 bytes. If file starts
with a pipe symbol, the file after the pipe symbol will be executed
with one argument, the user name. The output shall be the same as a
file line.

-r
Read realm:user:password triples from each line of file. This is
only needed if a client wants a server that authenticates itself.
The realm is a value sent by the client. User and password from the
first realm match are used. The value of realm can have zero
length, else it must be encoded in UTF-8. The values for user and
password to not have any encoding, the plain byte sequence will be
used. The user identifier must not be longer than 20 bytes and the
password must not be longer than 128 bytes. If file starts with a
pipe symbol, the file after the pipe symbol will be executed with
one argument, the realm. The output shall be the same as a file
line.

-s
Open pipes to the script or program specified by file. These pipes
are seen by the program as stdin and stdout. There is one
parameter, that can be either "put" or "get".

Further parameters are fed to the script via stdin. With the first
parameter being "put", data optionally follows on stdin. With
"get", parameters and data are read via stdout. Parameters that are
transmitted via stdin or stdout have the form "Parameter: value".
The first empty line seperates parameters and data. The empty line
can be the first line. In this case, no parameters are present.
Line delimiter is system specific. The possible parameters are:

· "From: type/client-identifier" which specifies the client
address. Currently, types can be "bluetooth", "irda" or "tcp".
The client identifier is an address (embraced in brackets) with
optionally a port (seperated by a colon).

· "Name: utf8-string" (required on "get" output) which specifies
the file name,

· "Length: uint32" (required on "get" output) which specifies the
amount of data in bytes in the data section that follows, and

· "Type: ascii-string" which specifies the mime type of the data.
Unknown parameters shall be ignored. With "put", obexpushd is
waiting for an ok after the list of parameters. The script must
either print a line with "OK" to stdout to accept the input or
a line with any other content to reject it.

-n
Do not detach from terminal.

-d
Enable debug messages (implies -n).

-h
Show summary of options.

-v
Show version of program.

AUTHORS
Hendrik Sattler
Author.

Eugeniy Meshcheryakov
texted the first version of the manpage
Posted by at No comments:

samba blocking in Karmi Koala 

sudo ufw allow 445

solves this 
problem in Karmic Koala
Posted by at No comments:
Subscribe to: Posts (Atom)