
WEIGHT: 59 kg
Breast: 38
1 HOUR:60$
NIGHT: +50$
Sex services: Tie & Tease, Photo / Video rec, Role playing, Striptease amateur, Massage professional
A few days ago I had to replace the old IP camera I use to watch over my dogs and cats, and found out that IP cam technology changed a lot since I bought that old camera. IP cameras are now low-price and ubiquitous.
I bought one of those generic models and installed it at my home, expecting to use the same software and network configuration I used before. However, these new cameras do not work the same way. They didn't gave me the same control I had over the old model.
This is the "wonderful" world of P2P camera. My old camera worked by providing an internet webserver where I should connect to receive the images. Simple, but a pain in the ass when you want to access your camera from outside your home LAN. P2P camera are different: Instead of you connecting to the camera, the camera itself connects to a server, and, to see the images, you need to connect your phone to the same server. No matter where you are in the world, if you have an internet connection, you can still receive your camera images.
Despite being easier to configure, this simplicity seemed to also bring some security concerns, and I gave up installing this thing at my home. However, that presented a good opportunity for reverse engineering a third party hardware, and maybe I could even get into the guts of the camera and change the things I didn't like in it. This series of posts will document this analysis.
This is a work in progress. I will add new posts whenever I advance in this study. This first difficulty was to find information about the camera. Despite having a company logo printed on its front, I could not find any information about this company on Google.