Originally posted by sguerrini97
It's 3.50, also with the debug I can install 3.50 max?
i think so.
---------- Post added at 08:51 AM ---------- Previous post was at 08:11 AM ----------
Originally posted by rodq
You need to decrypt the SIG file to XML then add a simple line that specifies to get the IDPS data from your console. Then encrypt to SIG. The hard way is to decrypt (it took me allmost one hour and one more hour to build a program). The rest of the job is just google. Hint for decrypting... "O=O". THIS WILL JUST GET YOUR IDPS.
Well according to CONSOLE_SETUP_CEX.SIG.xml
Passege are:
COPY pd_label.txt ->request_idps_in.txt
APPEND TAB(TAB SPACE?)
APPEND kiban_id.txt
APPEND cid
APPEND ecid
APPEND config_version(idps_bbox_config_version.txt)
REQUESTIDPS request_idps.txt <-- request_idps_in.txt (target 61.213.etc.:63210)
INSERT pd_label_bin_ascii.txt(ASCII to BIN) -> request_idps.txt
DONE!
Problem1:
pd_label.txt
REQUESTLOGISTICLABEL from prd_serial_01.new (traget 61.213.....)
Problem2:
idps_bbox_config_version.txt
REQUESTIDPSCONFIG(getting request_idps_config.txt) from pd_label.txt (target 61.blablabla)
then divided to ipds_bbox.config_version.txt
Maybe setting target to pc connected ip should work? To handmade request_idps we need pd_label.
REQUESTIDPS function do what? Write something or just check?