Showing posts with label Recovery. Show all posts
Showing posts with label Recovery. Show all posts

Tuesday, December 20, 2011

Password recovery on the Cisco Asa safety Appliance

In this article, I'll illustrate how to achieve a password "reset" on your Cisco Asa security appliance. The more ordinarily used term for this course is "password recovery" which is left over from the days when you could of course view passwords in configuration files in plain text. Today, such passwords are encrypted and not of course recoverable. Instead, you will gain way to the appliance via the console port and reset the password(s) to known values.

This course requires corporeal way to the device. You will power-cycle your appliance by unplugging it at the power strip and plugging it back in. You will then interrupt the boot process and convert the configuration register value to forestall the appliance from reading its stored configuration at boot. Since the gismo ignores its saved configuration on boot, you are able to way its configuration modes without passwords. Once you're in configuration mode, you will load the saved configuration from flash memory, convert the passwords to a known value, convert the configuration register value to tell the gismo to load its saved configuration on boot, and reload the device.

SECURITY

Caution: As with all configuration procedures, these procedures should be tested in a laboratory environment prior to usage in a production environment to ensure suitability for your situation.

The following steps were designed using a Cisco Asa 5505 Security Appliance. They are not approved for a Cisco Pix Firewall appliance.

1. Power-cycle your security appliance by removing and re-inserting the power plug at the power strip.

2. When prompted, press Esc to interrupt the boot process and enter Rom Monitor mode. You should immediately see a rommon prompt (rommon #0>).

3. At the rommon prompt, enter the confreg command to view the current configuration register setting: rommon #0>confreg

4. The current configuration register should be the default of 0x01 (it will of course display as 0x00000001). The security appliance will ask if you want to make changes to the configuration register. Write back no when prompted.

5. You must convert the configuration register to 0x41, which tells the appliance to ignore its saved (startup) configuration upon boot: rommon #1>confreg 0x41

6. Reset the appliance with the boot command: rommon #2>boot

7. Notice that the security appliance ignores its startup configuration during the boot process. When it finishes booting, you should see a generic User Mode prompt: ciscoasa>

8. Enter the enable command to enter Privileged Mode. When the appliance prompts you for a password, plainly press (at this point, the password is blank): ciscoasa>enable Password: ciscoasa#

9. Copy the startup configuration file into the running configuration with the following command: ciscoasa#copy startup-config running-config Destination filename [running-config]?

10. The previously saved configuration is now the active configuration, but since the security appliance is already in Privileged Mode, privileged way is not disabled. Next, in configuration mode, enter the following command to convert the Privileged Mode password to a known value (in this case, we'll use the password system): asa#conf t asa(config)#enable password system

11. While still in Configuration Mode, reset the configuration register to the default of 0x01 to force the security appliance to read its startup configuration on boot: asa(config)#config-register 0x01

12. Use the following commands to view the configuration register setting: asa(config)#exit asa#show version

13. At bottom of the production of the show version command, you should see the following statement: Configuration register is 0x41 (will be 0x1 at next reload)

14. Save the current configuration with the copy run start command to make the above changes persistent: asa#copy run start Source filename [running-config]

15. Reload the security appliance: asa# reload law config has been modified. Save? [Y]es/[N]o:yes

Cryptochecksum: e87f1433 54896e6b 4e21d072 d71a9cbf

2149 bytes copied in 1.480 secs (2149 bytes/sec) strike for home with reload? [confirm]

When your security appliance reloads, you should be able to use your newly reset password to enter privileged mode.

Copyright (c) 2007 Don R. Crawley

Password recovery on the Cisco Asa safety Appliance

SECURITY

Thursday, August 11, 2011

File Recovery to Fix Windows Vista Operating System Crash Problems

Blue Screen and Stop errors are quite common and frequent in Microsoft Windows operating system. These problems are with all versions of Windows operating system, including Microsoft Windows 7 and Microsoft Windows Vista. They are generally caused by corrupt, missing, or inaccessible system data structures. When such problems occur, your system may become unbootable and inaccessible. In such cases, you cannot access your significant files from Windows hard drive and run across file loss situations. In order to get your files recovered in such cases, file recovery software come for your rescue if there is no backup in place.

As a real-world example of this problem, consider the following scenario:

MICROSOFT SECURITY ESSENTIALS LATEST VERSION

You switched over to Windows Vista from Windows 7 due to lots of Stop and blue screen errors.

You are unable to install device drivers on your computer, running Microsoft Windows Vista.

Every time you try to install the driver, process is terminated automatically.

Whenever you unplug your external hard drive from the problem Windows computer, you encounter
the below blue screen error:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 2057

Additional information about the problem:
BCCode: a
BCP1: 0000000000000010
BCP2: 000000000000000C
BCP3: 0000000000000000
BCP4: FFFFF80001C86489
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1
Root of the issue

This problem generally occurs after adding a new hardware component or due to missing device drivers and system data structures. Windows data structures, like file system, boot loader, and master boot record, may corrupt because of virus infection, improper system shutdown, and system crash like situations.

Resolution

You can try fixing this behavior using any of the below methods:

Remove the recently added hardware component.

Reinstall corrupt device drivers.

Restore your Microsoft Windows Vista operating system-based computer to the last good configuration. But, this method removes the file added after creation of the last restore point.

Restore data from the current backup. For assured file recovery, the backup must be valid and updated.

When all else fail, file recovery software help you to get your precious data recovered. The applications are incorporated with interactive and self-descriptive graphical user interface to ensure quick and easy file recovery. They use high-end scanning techniques to carry out in-depth scan of entire Windows hard drive and extract all lost, missing, inaccessible, and deleted files from it.

File Recovery to Fix Windows Vista Operating System Crash Problems

Tom patrick is an repository editor and tech freak who loves to explores latest happening in the world of data recovery. Chosen data recovery for research as it's the most talked about issue these days and also challenging enough. In progression written this article about file recovery software.

MICROSOFT SECURITY ESSENTIALS LATEST VERSION