|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ifdown eth0 and then brining it back up with ifup
eth0, which will cause the system to try to obtain an address via
DHCP.
hiberfil.sys
from the Windows Vista laptop's hard disk drive to an external USB drive to
analyze it on another system. I removed the drive from the laptop and put it
into a
Thermaltake Black Widow hard dirve eSATA + USB Docking Station, which
I attached the system I would use for the backup. I was unable to boot that
system from a BartPE boot
disc, so I booted the system instead from a
Knoppix Linux Live CD. However, when
I connected the docking station with the laptop drive in it to the system,
I received the message below:| Error - Konqueror |
|
Windows is hibernated, won't mount. Failed to mount '/dev/sdb1': Operation not permitted The NTFS partition is hibernated. Please resume WIndows and turned it off properly, so mounting could be done safely.
|
I only needed to mount the drive in read-only mode to copy
hiberfil.sys from it, so I obtained a command prompt and opened
a Bash shell,
switched to the root account and mounted the device in read-only mode. I had
another external USB drive attached, which was to hold the backup, as
/dev/sda1. The laptop drive had two partitions on it: the Windows
Vista partition, which was /dev/sdb1 and a recovery partition,
which was /dev/sdb2.
knoppix@Knoppix:~$ sudo bash root@Knoppix:~# mount -r /dev/sdb1 /media/sdb1
After copying hiberfil.sys from the laptop drive to the other
external USB drive, I unmounted the laptop drive.
root@Knoppix:~# umount /dev/sdb2 root@Knoppix:~# umount /dev/sdb1
I checked the contents of the backup copy of hiberfil.sys
with the od command. I saw that the first 4 bytes of the file
were "HIBR", which indicates the system containing the file was last shutdown
into hibernate mode rather than to a normal shutdown state.
To view just the first 8 bytes of the file with od, you can use
od -a -N 8.
root@Knoppix:~# od -a -N 8 /mnt/hdd/hiberfil.sys
0000000 w a k e ht nul nul nul
0000010References:
Since Mozilla Firefox understands how to use SOCKS proxies, you can configure it to go through the SOCKS proxy. You can configure it to use a SOCKS proxy by clicking on Edit, then Preferences, and then the Network tab. Click on Settings and then select Manual proxy configuration. For a SOCKS proxy, put the address of the SOCKS proxy server in the SOCKS Host field and the port that is being used on that server in the Port field.
If I establish a SOCKS proxy server using the ssh command,
e.g. ssh -D 8055 jdoe@192.168.1.1, then I'm tunneling connections
to the SOCKS proxy through the encrypted SSH connection and I will use
127.0.0.1 in the SOCKS host field and 8055
in the Port field, rather than the default SOCKS proxy port of
1080.
After downloading the proxychains package with Mozilla Firefox, aka iceweasel,
I used dpkg to install it.
root@Knoppix:/home/knoppix# dpkg --install proxychains_2.1-5_i386.deb Selecting previously deselected package proxychains. (Reading database ... 0 files and directories currently installed.) Unpacking proxychains (from proxychains_2.1-5_i386.deb) ... dpkg: dependency problems prevent configuration of proxychains: proxychains depends on libc6 (>= 2.3.2.ds1-21); however: Package libc6 is not installed. dpkg: error processing proxychains (--install): dependency problems - leaving unconfigured Errors were encountered while processing: proxychains
Proxychains looks for its configuration file in the following order:
I copied the sample file /etc/proxychains.conf.dpkg-new
to /etc/proxychains.conf.
root@Knoppix:/home/knoppix# cp /etc/proxychains.conf.dpkg-new /etc/proxychains.conf
The following default information appears in that file:
# ProxyList format
# type host port [user pass]
# (values separated by 'tab' or 'blank')
#
#
# Examples:
#
# socks5 192.168.67.78 1080 lamer secret
# http 192.168.89.3 8080 justu hidden
# socks4 192.168.1.49 1080
# http 192.168.39.93 8080
#
#
# proxy types: http, socks4, socks5
# ( auth types supported: "basic"-http "user/pass"-socks )
#
http 10.0.0.5 3128
http 10.0.0.3 3128
http 10.0.0.5 3128
#socks5 192.168.1.4 1080
#socks4 10.5.81.143 1080
#http 192.168.203.18 8080I commented out the http lines with the 10.0.0.5
address by placing a "#" at the beginning of the line. I then removed
the "#" from the socks5 line and changed the address
from 192.168.1.4 to 127.0.0.1, since I was establishing a socks proxy
using the ssh command. I changed the port from the default SOCKS port of 1080
to the one I used when I established the SOCKS proxy with
ssh -D 8055 jdoe@192.68.1.1, i.e. port 8055.
I then had the following lines in proxychains.conf.
# http 10.0.0.5 3128
# http 10.0.0.3 3128
# http 10.0.0.5 3128
socks5 127.0.0.1 8055
#socks4 10.5.81.143 1080
#http 192.168.203.18 8080I also commented out "random_chain" and "chain_len" and uncommented "strict_chain".
I was then able to use proxychains with gpg to
import a public key for a package repository into the public keyring for the
root account.
root@Knoppix:/home/knoppix# proxychains gpg --keyserver wwwkeys.eu.pgp.net --rec v-keys 9AA38DCD55BE302B gpg: requesting key 55BE302B from hkp server wwwkeys.eu.pgp.net ProxyChains-2.1 (http://proxychains.sf.net) random chain (1):....127.0.0.1:5555....194.171.167.98:11371..OK gpg: /root/.gnupg/trustdb.gpg: trustdb created gpg: key 55BE302B: public key "Debian Archive Automatic Signing Key (5.0/lenny) <ftpmaster@debian.org>" imported gpg: no ultimately trusted keys found gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1)
I was also able to use proxychains for apt-get update
by using proxychains apt-get update.
References:
/etc/debian_version.
root@Knoppix:~# cat /etc/debian_version
lenny/sidpump. As root, you can
issue the commands below:
ifconfig eth0 up
pump -i eth0The options available for pump are shown below:
root@Knoppix:~# pump --help
Usage: pump [OPTION...]
-c, --config-file=STRING Configuration file to use instead of
/etc/pump.conf
-h, --hostname=hostname Hostname to request
-i, --interface=iface Interface to configure (normally eth0)
-k, --kill Kill daemon (and disable all interfaces)
-l, --lease=hours Lease time to request (in hours)
-L, --leasesecs=seconds Lease time to request (in seconds)
--lookup-hostname Force lookup of hostname
-r, --release Release interface
-R, --renew Force immediate lease renewal
-v, --verbose Log verbose debug info
-s, --status Display interface status
-d, --no-dns Don't update resolv.conf
--no-gateway Don't set a gateway for this interface
--no-setup Don't set up anything
--no-resolvconf Don't set up resolvconf
--no-bootp Ignore non-DHCP BOOTP responses
--script=STRING Script to use
--win-client-ident Set the client identifier to match Window's
Help options:
-?, --help Show this help messageThe problem is apparently due to the other distributions of Linux not recognizing the Serial ATA chipset on the motherboard of the system, at least for the versions that I was using. The system has a PCChips A31G V:1.0 motherboard According to Serial ATA (SATA) chipsets ? Linux support status, "Some SATA chipsets have been supported since practically forever, as their programming interfaces are unchanged from PATA predecessors. Others are brand-new and require new drivers from scratch.
Refererences:
