i suggest you use a binvar and load it up with the needed text of the cookie using its asc values, but lead it off with a zero asc value (reason at bottom), also create a var called %1 and set its value to 1 and then later in the code inc it once so its value is 2 (reason at bottom), when u need to send it to the website use $bvar(&binvar,%1,999)
example, im going to use the text "DaveC" as what i want to *encrypt*
...
var %1 = 1
... other code ...
bset &binvar %1 0 68 97 118 101 67
... other code ...
inc %1
... other code ...
sockwrite ... $bvar(&binvar,%1,999).text
...
That should be enough to put the average browser of your script off from locating it, its not really encrypted, as any encryption can be just hacked at the point you send the cookie data with a simple //echo -s being added to the front of the sockwrite, or a duplicated line of it, if the sockwrite is needed etc.
* just to make it clear %1 holds the value 1 when its needed as 1 when you create the binvar, but later (hidden in other code if possable) you increment it to 2
* the binvar has a asc value of 0 as the first character, so if someone added a //echo -st $bvar(&binvar,1,999).text it wont show anything becuase 0 stops the text displaying
* the %1 is actually 2 at that time so displays from the 2nd character
This is of course just rudamentry jiggling to offset the average viewer, anyone with any scripting skill is going to see past it, and its still gonna get snapped by the "//echo -st" on the fornt of the socketwrite