Ini file access barred to script only?

[Realm]

I am creating a script that will auto open my emails and some of my other favorite websites, and automatically log me in. My buddy wants a copy as well. So I want to create an ini file or another type, that the script and only the script can access. Basically, I dont want the file to be opened and easily read with a text editor or another similar program. Any Ideas or suggestions?

[Melba23]

Realm,

Use the Crypt UDF to encrypt the data before you write it and to decrypt it once you have read it back in. The file can still be opened, but not read.

Although it is impossible to completely secure your data, this would be a pretty good beginning.

M23

[jchd]

You can embark any file you want using FileInstall (look in the Help file). You may obfuscate it somehow; that won't be NSA grade security but probably enough for layman application.

[Fulano]

@jchd: I used FileInstall() to embark in the good ship 'settings.ini' on a long journey 'round the world.

[Realm]

jchd, I was looking at fileinstall, If I understand it correctly, the file to be compiled in the exe, must have all the varaiables declared, and cannot be added to by the end user. This would be a difficult situation, for I don't believe my buddy wants share his passwords with me. But I appreciate the pointer, It gives me an idea for another script I am currently working on, Thanks

Melba23. As long as the file cannot be easily read, this should be great. I took a quick look at '_Crypt_EncryptData', plz correct me if i am wrong, this will encrypt, the data in the file, making it almost impossible to retrieve from outside sources, unless you have the key. and the key will be store in the compiled exe?

[Fulano]

Well, it could be stored in the compiled exe, or it could be given as a master password by your friend. Depends on what you prefer.

[GEOSoft]

Another simple way is to use Binary.

$sKey = "Key"
$sData = "This is some sample data."
$sIni = "Somefile.ini"

IniWrite($sIni, $sKey, StringToBinary($sData))

Then to read it

$Val = IniRead($sIni, $sKey, BinaryToString($sData), "Ooops")

You can use the same Binary trick for $sKey to make it even more confusing.

Again, it's not industrial strength but it's also not plain text.

EDIT: I forgot to mention that it's not always a great idea to store the ini in @ScriptDir. First it's easier to find it and secondly you may run into a security issue with Windows. @AppDataDir or @AppDataDir & "\Somefolder\" are generally good places. Also take a look at

@AppDataDir & "\" & StringTrimLeft(Binary(@UserName), 2)

Edited April 28, 2010 by GEOSoft

[Realm]

GEOsoft, Thanks for your example, that may be useful in another project I am working on.

Fulano, I think for this project using a key set by the end user, my buddy, would be best, making it more difficult for an outside user to decrypt his info.

Thanks to everyone for their input, even though some were less suitable to my needs for this project, the rest gave me some great ideas for some of my other projects.

Cheers!

After taking another look at GEOsoft's example, maybe it would be another step to obfuscating it more, Thanks again!

Edited April 28, 2010 by Realm

[GEOSoft]

No problem but check the edit I made to it regardless of the method you use

[jchd]

@Realm

You got it about the Crypt part. Granted, files enclosed in compiled scripts can't be easily modified.

@Fulano,

Yep, and a pair of microSD cards can fit inside a coin (yes) and hold Ghosts images of the system on one and the data partition one the other. This way you can travel light, just having any basic system on your laptop and the Ghost restore stuff (and a popular game to divert attention). No more hassle at boundaries, being searched for dubious files and answering silly questions.

[Realm]

GEOsoft, as for your edit, I was already considering that but was confused on the options of it, thanks to your edit, it does open some clarity and doors.