Digital Workshop

Hi

I've been using one of my (perhaps a little too original) solutions and had what appeared to be an intermittent problem. To store info about the publication activation, I've been encrypting a string and placing it in the registry. The thing is that it doesn't always come out the same as it goes in. The problem is usually part of the way through the string, from which point all the characters are wrong.

I have used the Opus' encryption facility to produce the encryption, writing to a temp file then reading it back before placing in the registry.

I've no idea how the web will deal with this bit of text:

AHHHH!!!

Strangely enough, pasting the text in here uncovered the problem. Opus encryption seems to make use of a new line (\r) character which the registry removes, hence messing up the encryption. It probably uses other similar characters as well.

New problem....

Does anyone know how to avoid use of the characters the registry doesn't like (presuming this is the problem)? I have tried writing a script to replace \r with something else, but I couldn't get it to work. I have switched to a simple encryption key, but I have no idea whether this is likely to work once dates and activation info change.

Maybe need another solution?

Thanks
Dan

Actually, I have just knocked something up for this. I like puzzles, so it was quite interesting seeing how nasty I could be. It probably wouldn't take Bletchley Park long to decipher, but is good enough for the said purpose.

Cheers anyway
Dan