Okay, now for some technical questions.

I'm assisting AWJunkies in this conversion of JUpload (albeit remotely so much of what I found out/tested is second hand).
The issue we're seeing is that the sessions isn't correctly being reinstantiated when JUpload uploads the images, which makes complete sense since each upload transaction is down through the Java piece w/out the original cookie. To get around this JUpload crypts the current _COOKIE[] data and sends it across as a _GET parameter.
In 1.3.5, HTTP_COOKIE_VARS contained the _uid, _pass and _data of the cookie. This worked since it also contained both the _uid and _pass which allowed JUpload to just plug in a few values to make it work across the board. However, in 1.4.3/4 _COOKIE[] no longer contains the _user and _pass fields.
Was _user and _pass entered by the CopperMine script itself? I don't see where this would have been added by JUpload from looking at the old 1.3.5 install instructions.
Now, tracing back and doing some code dumps of data, I'm trying to figure out how we can get the session reinstanciated w/out making much/any modifications to the CopperMine code itself.
In 1.3.5, when I decrypted the cookie that JUpload got using
$cookieEnc = base64_encode(serialize($HTTP_COOKIE_VARS)); I got the following values:
Array
(
[cpg133_data] => klEIj7czoxOO30zYDE0c0WY5YSnOTU3ZjY5NjI6tjZoYmYyOiJhbITU5tzOjMyOiI52ZiII7aNDNjdjYToyxOWMTY2N=
[cpg133_uid] => 3
[cpg133_pass] => 902c6ca51933f3532e50e77b31aebafc
)
However, in 1.4.3, it's different, same line
$cookieEnc = base64_encode(serialize($_COOKIE)); Different output:
Array
(
[cd86eb178b708127f36c62fb2479c20f] => 4943a6889a7b9c0203db5466f6927760
[cpg143_data] => klEIjtzOjMyOiI2NzOjI6I0YiI7czoyOiWI4Q0MGM6aXNoIjhbSI7aToxO3RlOTkzWM3YmZlNjIYTuZyNNDoibGFzQ5YJ2Z2I7mdsozOntMzc1czo3OiJlbMDUt9
)
We're trying to figure out what that odd array key is....and what it's value is. Is that some kind of cryptic session handling that CM is using? Is there a way to use cookie_extraction() to our advantage to decrypt/use that odd session key to properly restore the session to allow JUpload to work properly?
I'm thinking, just looking over code (unable to fully test myself) that it's possible to use $this->client_id within cookie_extraction(), right? If so, is that odd key the client_id and the value the password? If that's the case then, things are solved. If not, then we're back at the start.
PS: All data as be shuffled to prevent decryption or attempts to gain insight as to what the real values are.