Unflappings

Photo Courtesy of ZDnet

So you want the new 2.1 update for your Droid but you don’t want to wait for the Over the Air (OTA) update. Maybe you rooted your phone and you simply want to mess around with the files for development purposes. Well you can grab the download here and also get installation instructions below.

NOTE* this is for Droid phones which are not rooted and are running 2.0.1 ***CONFIRMED*** This works on Rooted and Unrooted Droids. Proceed at your own Caution while applying this update with a Rooted Droid. If you have applied any custom ROM’s you may run into problems. In addition it may be better to go back to stock before you proceed with this tutorial.

Continue Reading »

It is a hassle when you are messing with customizing your phone and you lose all your important data. Luckily, the good thing about the Android OS is the ability to upload all your data to the “cloud”. Unfortunately, this does not entail the backup of your system settings, text messages and phone logs.

Don’t fear, and don’t buy any expensive solutions that claim to be the one touch backup king. Not that the PPU solutions won’t work nicely, because they do. However, in times like these, its much better to go the free route.

To backup your Call Logs and restore them, follow the steps below:

1. Go to the Android market, and download “Call Logs Backup & Restore”
2. Install the Application
3. Open the application, and select “Backup Call Logs”
4. Wait patiently, at times this process can take a few moments

To backup your Call Logs backup to your local machine (The extra care procedure, not needed)

1. Plug your phone into a computer via a USB cable
2. Go to your notification bar, and select “USB Connected” and then select “Mount”
3. Navigate to your computer and open your Android SD card. This will show up as a Removable Device
4. Open the folder named CallLogBackupRestore and copy that file to a protected drive or simply that computer for future use

To restore your Call Logs simply open the Call Logs Backup & Restore application and select “Restore Call Logs” If your phone crashed or SD card malfunctioned, place your backed up file on your computer back into the CallLogBackupRestore Directory.

Also See: Backup Text Messages on Android

It is a hassle when you are messing with customizing your phone and you lose all your important data. Luckily, the good thing about the Android OS is the ability to automatically upload all your data (contacts etc.) to the “cloud”. Unfortunately, this does not entail the backup of your system settings, text messages and phone logs.

Don’t fear, and don’t buy any expensive solutions that claim to be the one touch backup king. Not that the PPU solutions won’t work nicely, because they do. However, in times like these, its much better to go the free route.

To backup your text messages and restore them, follow the steps below:

1. Go to the Android market, and download “SMS Backup & Restore”
2. Install the Application
3. Open the application, and select “Backup SMS Messages”
4. Wait patiently, at times this process can take a few moments

To backup your text message backup to your local machine (The extra care procedure, not needed)

1. Plug your phone into a computer via a USB cable
2. Go to your notification bar, and select “USB Connected” and then select “Mount”
3. Navigate to your computer and open your Android SD card. This will show up as a Removable Device
4. Open the folder named SMSBackupRestore and copy that file to a protected drive or simply that computer for future use

To restore your messages, simply open the SMS backup & restore application and select “Restore SMS Messages” If your phone crashed or SD card malfunctioned, place your backed up file on your computer back into the SMSBackupRestore Directory.

Also See Backup Phone Logs on Droid

Background

While I have been a pfSense user for about 2 years, I decided to see how the FreeBSD base OS would stack up against Vyatta, a Linux base free router software package. Without going into too much detail, main differences currently is a more CLI centric interface (close to JunOS “set” syntax) for Vyatta in comparison to a comprehensive WebGUI for pfSense. Beyond that there are many features betwene the two which I will not get into here, as my primary question here is speed.

Purpose

The goal here is to just test IP forwarding speed between the two platforms in completely stock configuration. I’m sure there are tweaks I could have made either way, but in order to be consistent, no changes were made from the base install on either platform. The hardware used is a low power Jetway mini PC. I am fully aware this is not server class hardware by any means, but until I have unlimited funds, this will have to do. Hardware specifications listed below.

Continue Reading »

For anyone who is trying to access file shares inside local VM’s running windows Vista or Windows 7, the following article does a great job explaining what needs to be done in order to change the “Location” of the VMware NICs. Apparently by default Windows cannot figure out what or where they are, so it shoves them off in the Public location and disables most of their abilities. I tried the registry key fix and it worked flawlessly (albeit after a reboot).

This issue also arises if your virtual environment has a different domain than your physical host workstation, which was the case for me. This will prompt you to authenticate, but no matter what credentials you enter, the share login will be unsuccessful. Anyway, give this a shot.

http://aspoc.net/archives/2008/10/30/unidentified-network-issue-with-vmwares-virtual-nics-in-vista/

Bold indicates a button clicked or key pressed.
“quotes” indicates a value which has been entered.

Grey block quote is a command typed directly into the console.

If you happen to come across the following error:

Joined ‘LOCALHOST’ to realm ‘test.lcl’
[2010/03/04 14:39:39,     0] utils/net_ads.c:1080(net_update_dns_internal)   net_update_dns_internal: Failed to connect to our DC!
DNS update failed!

This simply means that your FQDN entry for the Linux system you are trying to join is incorrect as far as AD is concerned. In this case the box LOCALHOST.LOCAL.LCL was trying to join the domain TEST.LCL and there was an obvious mismatch. However not quite as obvious of an error message. Update this information in your /etc/hosts file and you should be set!

Bold indicates a button clicked or key pressed.
“quotes” indicates a value which has been entered.

Grey block quote is a command typed directly into the console.

Purpose

The following steps allow you to convert a PFX certificate file in Windows Server to a PEM file. This is important since most Linux/Unix systems prefer a PEM format for certificate use, especially something like an Apache web server.

1. Download and install the Win32 OpenSSL (v0.9.8i) package from http://www.slproweb.com/products/Win32OpenSSL.html
2. Create the folder C:\certs and copy your exported PFX certificate file inot the C:\certs folder. The name yourcert.pfx is used in this example.
3. Go to Start, then click Run and type in “cmd” and press enter. This should bring up a command prompt which you can use to change into the OpenSSL bin directory.

cd %homedrive%\OpenSSL\bin

openssl pkcs12 -in C:\certs\yourcert.pfx -out c:\certs\newcertname.pem -nodes

4. This should convert the file from a PFX format to a PEM format, feel free to substitute your own name instead of “newcertname.pem”. Also be sure this command is entered as one line, regardless of how it appears on this site. When prompted, enter the password you used when exporting the PFX file from the Windows certificate store. You should then receive the message “MAC verified OK”.
5. Open “newcertname.pem” in notepad, and cut out the private key into C:\OpenSSL\bin\private\privatekey.pem (or another path and name as you see fit).
6. Also cut out the CA Certificate into C:\OpenSSL\bin\cacert.pem
7. Modify c:\OpenSSL\bin\openssl.cfg configuration file and change the [alt_names] to whichever alternative names you wish.
8. Create a new request, by typing the following commands.

openssl req -new -nodes -keyout privatekey.pem -out cert-request.pem

openssl ca -out issued-cert -in cert-request.pem

9. This should have created a new request and signed it with the CA’s private key. Keep in mind the path to these certificate files are not included here so make sure you are in the proper directory (i.e. the same directory) for those files.
10. If you get errors during this procedure, clear the index.txt and serial files within the OpenSSL directory to be sure it is working with a fresh batch. Below is the configuration file for OpenSSL and is to be used as reference. Not all of the configuration is the same, so be sure to double check names of certificates and paths.

Continue Reading »