Keeping Secret Information Secret

Go Beyond hiding your files

from WinCustomize Forums

When you encrypt a file, the filename & extension remain the same usually. If you want to really secure your sensitive information such as pictures, financial information, etc. to yourself, all you have to do is rename the file extension and file name.

You could legitimately rename an image such from "Image.jpg" to "Readme.txt". At first it appears to be corrupted. It isn't. If you rename it from "Readme.txt" to "Image.jpg", it will remain untouched. This isn't perfect, so use with encryption if possible.

There are some drawbacks. If somebody opens up that file in a text editor, nothing but scrambled symbols will appear. However, if even one character is altered and saved in the text editor, the whole file will become corrupted.

Here are some tips on what to do:

  • Rename the file to a common extension name. (Such as .jpg to .rtf, not .xxx)
  • Rename the first part to something not too suspicious or obvious. (Such as "My Windowblinds Skin.wba" to "Budget 2009.xlsx", not "My Windowblinds Skin.xlsx".)
  • Do NOT rename system files at all costs. Doing this may corrupt your system.

      • This security measure is meant to only keep other people you know out of your business. This won't keep Keyloggers, Hackers, or Cyberterrorists out of your business. Only do this if people can't keep out of your own personal business.

312 views 7 replies
Reply #1 from WinCustomize Forums Top
I wouldn't reccomend this method of "encryption"

For very good protection on many levels: TrueCrypt
Easy, secure, free.

What more could you ask for?   :CONGRAT: 
Reply #2 from WinCustomize Forums Top
What more could you ask for?


Pizza ;)
SoundPackager - Customize the Windows sound scheme
Reply #3 from WinCustomize Forums Top
Pizza
Hell yaeh!!   :CONGRAT: 
Reply #4 from WinCustomize Forums Top
What more could you ask for?


Bag of hundreds plz  :d  and a white russian.  :d 
Reply #5 from WinCustomize Forums Top
Bag of hundreds plz and a white russian.
And a smoke?
Reply #6 from JoeUser Forums Top
This really won't hide anything from anyone who would be looking for it.

It certainly won't keep people out of your person business. Take Zubaz advice and actually encrypt your drive if you actually want security.
Reply #7 from WinCustomize Forums Top
Version 6.0 of TrueCrypt was release earlier this month.  Check out the release ntoes:

6.0

July 4, 2008

      New features:

  • Parallelized encryption/decryption on multi-core processors (or multi-processor systems). Increase in encryption/decryption speed is directly proportional to the number of cores and/or processors.

    For example, if your computer has a quad-core processor, encryption and decryption will be four times faster than on a single-core processor with equivalent specifications (likewise, it will be twice faster on dual-core processors, etc.)

    [View benchmark results]

  • Ability to create and run an encrypted hidden operating system whose existence is impossible to prove (provided that certain guidelines are followed).  For more information, see the section Hidden Operating System.   (Windows Vista/XP/2008/2003)

    For security reasons, when a hidden operating system is running, TrueCrypt ensures that all local unencrypted filesystems and non-hidden TrueCrypt volumes are read-only. (Data is allowed to be written to filesystems within hidden TrueCrypt volumes.)

    Note: We recommend that hidden volumes are mounted only when a hidden operating system is running. For more information, see the subsection Security Precautions Pertaining to Hidden Volumes.

  • On Windows Vista and Windows 2008, it is now possible to encrypt an entire system drive even if it contains extended/logical partitions. (Note that on Windows XP you can encrypt an entire system drive as well, but it must contain only primary partitions.)

  • New volume format that increases reliability, performance and expandability:

    • Each volume created by this or later versions of TrueCrypt will contain an embedded backup header (located at the end of the volume). Note that it is impossible to mount a volume when its header is damaged (the header contains an encrypted master key). Therefore, embedded backup headers significantly reduce this risk. Also note that a backup header is not a copy of the original volume header because it is encrypted with a different header key derived using a different salt. For more information, see the subsection Tools > Restore Volume Header.

      Note: If the user fails to supply the correct password (and/or keyfiles) twice in a row when trying to mount a volume, TrueCrypt will automatically try to mount the volume using the embedded backup header (in addition to trying to mount it using the primary header) each subsequent time that the user attempts to mount the volume (until he or she clicks Cancel). If TrueCrypt fails to decrypt the primary header but it successfully decrypts the embedded backup header at the same time, the volume is mounted and the user is warned that the volume header is damaged (and informed as to how to repair it).

    • The size of the volume header area has been increased to 128 KB. This will allow implementation of new features and improvements in future versions and ensures that performance will not be impaired when a TrueCrypt volume is stored on a file system or device that uses a sector size greater than 512 bytes (the start of the data area will always be aligned with the start of a host-filesystem/physical sector).

    For more information about the new volume format, see the section TrueCrypt Volume Format Specification.

    Note: Volumes created by previous versions of TrueCrypt can be mounted using this version of TrueCrypt.

  • Parallelized header key derivation on multi-core processors (one algorithm per core/thread). As a result, mounting is several times faster on multi-core processors.  (Windows)

  • Ability to create hidden volumes under Mac OS X and Linux.

  • On Linux, TrueCrypt now uses native kernel cryptographic services (by default) for volumes encrypted in XTS mode. This increases read/write speed in most cases. However, the FUSE driver must still be used when the volume is encrypted in a deprecated mode of operation (LRW or CBC), or when mounting an outer volume with hidden-volume protection, or when using an old version of the Linux kernel that does not support XTS mode.  (Linux)


      Improvements:

  • Up to 20% faster resuming from hibernation when the system partition/drive is encrypted. (Windows Vista/XP/2008/2003)

  • Many other improvements.  (Windows, Mac OS X, and Linux)


      Removed features:

  • Encrypted system partitions/drives can no longer be permanently decrypted using the TrueCrypt Boot Loader (however, it is still possible using the TrueCrypt Rescue Disk). (Windows Vista/XP/2008/2003)

    Note: This was done in order to reduce the memory requirements for the TrueCrypt Boot Loader, which was necessary to enable the implementation of support for hidden operating systems.


      Bug fixes:

    • When Windows XP was installed on a FAT16 or FAT32 partition (as opposed to an NTFS partition) and the user attempted to encrypt the system partition (or system drive), the system encryption pretest failed. This will no longer occur.

  • Many other minor bug fixes and security improvements (preventing e.g. denial-of-service attacks). (Windows, Mac OS X, and Linux)