Thursday, May 14, 2009

Remember one word. Linux!

Using the GPG tool in Linux.

http://ask.slashdot.org/article.pl?sid=09/04/15/1743215

Any Linux professional can accomodate secure storage on a USB device.
Setup user or company department with a new gpg install on a new linux account.
create a gpg certificate - have them type in their email as recipient (email@me.com below) and a passphrase (the passphrase is yourpasswd below).
You then set their private key to level 5 ultimate trust.
If you were exchanging data with someone you would now export a public key for them to give to other IT for encrypting data to be sent.
In a simple archiving system creating a public key maybe unnecessary (though I've never tried it).
Hence forth in a cron/shellscript archive system you need only the two commands below:

Archive:
cat somefiletobearchived gpg -e -r email@me.com > somearchivedfile.gpg
Retrieve/Restore:
echo yourpasswd gpg --batch --passphrase-fd 0 -d somepreviouslyarchivedfile.gpg > somenewfilename
Remember to escape $ and other shell-misinterpreted characters in yourpasswd with \.
Do not ever use gpg option passphrase-fd with -e. Gpg will skip the first line of data with no warning and you'd never know since often only the recipient with the passphrase will ever extract the data.

Secure socket protocols such as WPA2 and the secure web protocol https are redundant. Both are limited to secure TRANSMISSION not secure storage. Wireless routers needn't have WEP WPA2 etc unless you are sharing a directory.
Finally some computer consultants and bloggers are saying this.
So verify https in all private website visits, do not share any directories in Windows File Manager, and be secure in your unsecured Access Point, wireless router or wireless modem!

The Sed command line stream editor tool in Linux installations is a great opportunity for young students to gain computer expertise and a foothold in the market. Know sed and regular expressions backwards and forwards. It is a complex data processing tool.

Apparently the pipe is not rendered in Blogspot. Of course you are piping (ASCII 124 Decimal)to gpg in the above samples.

0 comments: