Shockwave Habbo - Camera checksum

Quote:

---

Originally Posted by Moogly

There are some people we could ask, but if they answer it would be anonymous, though maybe @Nillus if he ever came back could answer, I'm sure he has some idea? Would be fun to see that camera redone, especially since the current camera is completely different.

---

The current camera sucks. I doubt @Nillus ever comes back to answer. I think the closest I would get maybe is @vista4life if he's still active on Skype and answers. But then again, I doubt anybody has answers, and I doubt anybody is willing to spend time on it since Shockwave is dead (I have to run an old version of Firefox in order for Shockwave to work). Maybe the v13 version needs to have some shit done to 'decrypt' the content (which is weird, since the rest of the packet is correctly decoded just like in Blunk), but I'm unsure. No doubt that making it work in v26 will be even harder. (I assume in v36 Habbo had removed the camera)

Quote:

---

Originally Posted by Glaceon

The current camera sucks. I doubt @Nillus ever comes back to answer. I think the closest I would get maybe is @vista4life if he's still active on Skype and answers. But then again, I doubt anybody has answers, and I doubt anybody is willing to spend time on it since Shockwave is dead (I have to run an old version of Firefox in order for Shockwave to work). Maybe the v13 version needs to have some shit done to 'decrypt' the content (which is weird, since the rest of the packet is correctly decoded just like in Blunk), but I'm unsure. No doubt that making it work in v26 will be even harder. (I assume in v36 Habbo had removed the camera)

---

That was around the time where they removed the camera completely yes. I always loved the Beta versions of Habbo cause they were really limited, it made me feel like I was playing v13 with a full screen.

Quote:

---

Originally Posted by Moogly

That was around the time where they removed the camera completely yes. I always loved the Beta versions of Habbo cause they were really limited, it made me feel like I was playing v13 with a full screen.

---

Anyways, if somehow you get in contact with somebody who knows how camera works, please let me know. You can also contact me on my new Skype (if I remember correctly, I had you on my old Skype joshua_develop). My new Skype is mr.josh.97, I'm not so active here anymore.

BETA was okay. I loved how BETA looked, the hotelview, the navigator (the R34/R35 one), overal it was just pretty cool, but then they changed things too much. Yet, if only Shockwave wouldn't be dead...

Quote:

---

Originally Posted by Glaceon

The current camera sucks. I doubt @Nillus ever comes back to answer. I think the closest I would get maybe is @vista4life if he's still active on Skype and answers. But then again, I doubt anybody has answers, and I doubt anybody is willing to spend time on it since Shockwave is dead (I have to run an old version of Firefox in order for Shockwave to work). Maybe the v13 version needs to have some shit done to 'decrypt' the content (which is weird, since the rest of the packet is correctly decoded just like in Blunk), but I'm unsure. No doubt that making it work in v26 will be even harder. (I assume in v36 Habbo had removed the camera)

---

Hey! I never bothered to figure out the 'cs' checksum for photos. Grab and persist, retrieve and provide.

Seems like it was some image integrity protection, provided by Shockwave itself. No idea how it is computed.

Regarding the credentials in the MUS 'Logon' message for V13: I think it could be an identifier provided to the client at login, or the Shockwave 'machine ID', or perhaps some hash computed from the SSO ticket. It's not like the V13 'SSO login' mode provided other means of identification.

Quote:

---

Originally Posted by Nillus

Hey! I never bothered to figure out the 'cs' checksum for photos. Grab and persist, retrieve and provide.

Seems like it was some image integrity protection, provided by Shockwave itself. No idea how it is computed.

Regarding the credentials in the MUS 'Logon' message for V13: I think it could be an identifier provided to the client at login, or the Shockwave 'machine ID', or perhaps some hash computed from the SSO ticket. It's not like the V13 'SSO login' mode provided other means of identification.

---

The MUS Logon according to the guy from Puomi has the machine ID of the player using the camera in it, which you can use to get the player.

@Cecer may know something about this - if I remember correctly he had camera working.

Quote:

---

Originally Posted by Navine

@larsxd1234 Using camera the same way as in v5 doesn't work... I ported Blunk's v5 MUS to Woodpecker C# and at the LOGIN packet I receive as content string:

1 7580690011900000

In Blunk, the content string is split like:

String[] credentials = request.contentString.split(" ", 2);

Where index 0 is the username and index 1 is the password. I'm curious about what the content string means.

---

The first ID is your user ID, the second is your machine ID. :):

Code:

---

on checkConnection(me)
  if not multiuserExists(pConnectionId) then
    return(error(me, "MUS connection not found:" && pConnectionId, #checkConnection, #minor))
  end if
  if getMultiuser(pConnectionId).connectionReady() and pHandshakeFinished then
    tUserID = getObject(#session).GET(#user_user_id)
    tMachineID = getSpecialServices().getMachineID()
    if pUseCrypto then
      tUserID = pCrypto.encipher(tUserID)
      tMachineID = pCrypto.encipher(tMachineID)
    end if
    getMultiuser(pConnectionId).send("LOGIN" && tUserID && tMachineID)
    me.next()
  else
    me.delay(1000, #checkConnection)
  end if
  exit
end

---