pv2challenger-linux

pv2challenger-linux
EDIT:::: THIS IS NO LONGER THE PREFERRED METHOD/MY SITE IS DOWN. PLEASE USE THE STAND ALONE APP FOR RECEIVING YOUR PV2'S CHALLENGE. http://jeff.crowell.googlepages.com/pv2challenger-0.2.tar.gz thanks SaturnNiGHTS for the sticky! step 1 wget http://theironknuckle.com/CVS/unlock_camera.c step 2 copy unlock_camera.c into your pv2tool-for-linux folder step 3 change into your pv2tool-linux directory and make step 4 now pv2tool for linux will read your challenge to you for easy unlocking!

Project Plan/Map My main goal of this project (pv2challenger) is to create an application separate from pv2tool that simply extracts the challenge, in making it easier to unlock your pv2 in linux! This project was started due to the lack of showing what the challenge in pv2tool-for-linux was. The final goal of this is creating a spearage app that 1) Opens your pv2 2) Requests challenge (similar to unlock_camera.c modification that I have done) 3) Shows user challenge 4) Spits challenge into a separate file 5) (might never happen due to PD's request) Generates a pv2keys.txt file using cronus 6) Because I will write this in C, hopefully it will cross platform, but I dont have access to a windows or mac box, so when I am done, I will need others to compile for me.

enigma-, It looks like I'm trying to do the same thing. I was thinking along the lines of a stand-alone app. I was trying to sort through the source code for OPS, Ceres, and the son Uranus(while trying to learn C at the same time) but I'm still having compile problems. The only C I've done is NQC, which isn't really that complex. What I was trying to make (admins - feel free to delete this if you deem it "questionable" material) is an app that would 1. Unlock the camera 2. Grab the challenge 3. "Find" the correct response pair 4. Unlock the camera/camcorder 5. Change the C/R's to the reset key, or permanatley patch the firmware (depending on if camera or camcorder) 6. Close Camera/Camcorder Kinda like a Ceres on steroids... (Titan, maybe?) I'm on windows, so we can work this from both ends if you want to

enigma-, It looks like I'm trying to do the same thing. I was thinking along the lines of a stand-alone app. I was trying to sort through the source code for OPS, Ceres, and the son Uranus(while trying to learn C at the same time) but I'm still having compile problems. The only C I've done is NQC, which isn't really that complex. What I was trying to make (admins - feel free to delete this if you deem it "questionable" material) is an app that would 1. Unlock the camera 2. Grab the challenge 3. "Find" the correct response pair 4. Unlock the camera/camcorder 5. Change the C/R's to the reset key, or permanatley patch the firmware (depending on if camera or camcorder) 6. Close Camera/Camcorder Kinda like a Ceres on steroids... (Titan, maybe?) I'm on windows, so we can work this from both ends if you want to I would like to see your source, I am trying to look at saturndownload, ops-for-linux, pv2tool, and pv2tool for linux in my attempt for this. The farthest that I can get is is to open camera, I dont have any C knowledge, i read a book on c++ but thats about it for programming knowledge except shell. hit me up on aim/msn ngenigma (aim) jeff.crowell@gmail.com (MSN)

I would like to see your source I'll take a another look at it tonight, I have to take care of somethings during the day. I was going off of ceres source, since it appears BillW already joined the open and unlock routines together. Right now I am just trying to make Ceres dump the challenges to a text file. Eventually it would be nice to roll the Cronus code right into the unlock routine, but more as a POC to me, I want it in a text file. The unlock portion looks like another graft from Ceres. The reset keys/Patch Firmware part might be kinda a dream at this point. That would have to come from OPS/PV2Tool. Then the close function can come again from Ceres. For the still camera, PV2Fetch is does similar tasks as Ceres. I am too learning C, I have a microscopic background in it from maybe 4 years ago. I'm just trying to plow through it and trying to make sense of every little part. (The only way to get better is to put yourself with better people)

I took it down to the most basic thing I could think of, just adding this after it gets the cam unlocked:

fopen("output.txt","a");
printf(challenge);
fclose("output.txt);

As far as I read, this should just spit the variable challenge to output.txt right? Then I get this when I try to compile (even an unmodified source for Ceres): Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland saturn2.c: Error E2451 saturn2.c 68: Undefined symbol 'cam' in function saturn_open Warning W8057 saturn2.c 195: Parameter 'imgsizex' is never used in function satu rn_process_cfa Warning W8057 saturn2.c 195: Parameter 'datalen' is never used in function satur n_process_cfa Warning W8057 saturn2.c 195: Parameter 'image' is never used in function saturn_ process_cfa Error E2451 saturn2.c 257: Undefined symbol 'cam' in function saturn_bulkread Error E2451 saturn2.c 269: Undefined symbol 'cam' in function saturn_bulkwrite Error E2451 saturn2.c 280: Undefined symbol 'cam' in function saturn_controlmess ageread Error E2451 saturn2.c 292: Undefined symbol 'cam' in function saturn_controlmess agewrite Error E2451 saturn2.c 328: Undefined symbol 'keyfile' in function saturn_getkey Error E2451 saturn2.c 329: Undefined symbol 'keyfound' in function saturn_getkey Warning W8057 saturn2.c 374: Parameter 'offset' is never used in function saturn _putkey *** 7 errors in Compile *** This is the free compiler from Borland. Can I use this or do I have to use something else? (When I poked around, it mentioned something about Microsoft) Thanks

hmm... I use gcc for compiling, and you need to add the -lusb flag, for example, once i have cd into ceres' directory i do gcc -o nameofexecutable *.c -lusb http://www.google.com/search?q=gcc+for+windows&start=0&ie=utf-8&oe=utf-8&client=firefox&rls=Swiftfox:en-US:unofficial please tell me your aim/msn so i can check your source, and try to imlement new stuff, as I am kind of stuck

I'll try GCC for Windows. My AIM is JRDavid01, I'm not on very much, but I'll try to be on later tonight. EDIT: I ended up installing cygwin

Ceres was compiled with the free Borland 5.5 compiler. I expect that most of it should be pretty easy to port elsewhere. Well, I can't get Borland or cygwin to take it. I'm sure I included all of the necessary files, and ran out of ideas. Once I am able to compile Ceres all by itself, I'll continue on.

Building with BCC should just be a matter of being in the source directory in a cmd window and typing "make". If that doesn't work for you, ensure that your C:\Borland\BCC\bin directory is set in the PATH variable before anything else.

Shoot, I just sent you a PM, so I guess you answered it here. Thanks a lot, I'll give it a try now. EDIT: I'm still getting the same two errors I quoted in the PM

All right, I got rid of cygwin (sorry enigma- :) ) and Borland is working for me. I'll take another jab at it tonight. I was thinking and instead of using fopen, maybe cout instead. It won't produce a txt file, but it will output to a DOS window, which is fine for now. Thanks again BillW for the help

Project Plan/Map My main goal of this project (pv2challenger) is to create an application separate from pv2tool that simply extracts the challenge, in making it easier to unlock your pv2 in linux! This project was started due to the lack of showing what the challenge in pv2tool-for-linux was. The final goal of this is creating a spearage app that 1) Opens your pv2 2) Requests challenge (similar to unlock_camera.c modification that I have done) 3) Shows user challenge 4) Spits challenge into a separate file 5) (might never happen due to PD's request) Generates a pv2keys.txt file using cronus 6) Because I will write this in C, hopefully it will cross platform, but I dont have access to a windows or mac box, so when I am done, I will need others to compile for me. I don't see why you can't reimplement Cronus in your new application. Cronus primarily called the openssl functions to perform its magic, so it shouldn't be difficult to massage that into another program. Also, I believe the last version doesn't even call the openssl libraries, so you might be able to reuse those encryption algorithms. Of course, if you did, you might not be able to discuss it here - but that's your call.

Alright, my first baby step is done. :P I have got a working version of Ceres that dumps the challenge into "output.txt". I used this code added right after Ceres fetches the challenge:

pFile = fopen ("output.txt","w");
fprintf(pFile, "%s\n", challenge);
fclose(pFile);

and I had to add this to the top in when it is initalizing everything: FILE * pFile; Of course, I couldn't explain to you what half of the flags in there do, but I'm learning! I uploded my source here, saturn.c. Here is the compiled version of it, Ceres.exe. Finally this is what an output looks like, output.txt. Its in Hex, so it will look wierd in Notepad (sorry BillW, I cannot make sense of those annoying boxes and squibblys :D ). Is there a better location I can dump the challenge, or will cronus be able to read the Hex? Next Step: Strip out the opening and mass storage mode of Ceres.

Okay, I got a little farther. I stripped out all of the Mass Storage Code and cleaned up any functions that we didn't need. Sorry, BillW if I'm butchering up your code :wink: It is uploaded here, Challenger.zip Basically, it: 1. Opens the cam 2. Finds the challenge and response 3. Dumps it via fprintf to output.txt 4. And closes the camera. Next step, spit out the challenge in hex instead of gobbly-gook that has to be read in WinHex

View Full Version: pv2challenger-linux