Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
certs error in sb6190 but not in sb6141
#1
i get that error when using sb6121 certs in sb6190. Ive never seen it before. anyone knows why or how can it be fix?

[ERROR] [DOCSIS.BPI(pid=263)]: Decrypt Auth Key: Couldn't format PKCS#8 private key into PKCS#1 format!
[WARNING] [DOCSIS.BPI(pid=263)]: Decryption of Auth key failed
[ERROR] [COMMON_COMPONENTS.TLV_PARSER(pid=263)]: The apply handler, before handling sub-TLVs: type 7 return error
[ERROR] [COMMON_COMPONENTS.TLV_PARSER(pid=263)]: ApplyTlvParseHandlers Failed.
[ERROR] [DOCSIS.BPI(pid=263)]: BPI CheckAuthReply: Tlv Parse Failed, -8
[ERROR] [DOCSIS.BPI(pid=263)]: BPI: Auth Reply failed validity check!!
Reply
#2
the problem lies in liball_docsis.so.. This stupid arris modem just accepts private keys of 688 bytes... moto private keys are 672 or so. Anyone is an expert in C that can reverse the entire liball_docsis.so?

Come on lets work to make sb6190 better... Im starring to learn C, but it will take me years to be proficient enough to decompile this.

Code:
*(_WORD *)(v1 + 3364) = v4;
  close(v3);
  sprintf(&s, "%s/%s", &v43, "cm_key_prv.bin");
  v6 = open(&s, 0);
  v7 = v6;
  if ( v6 == -1 )
  {
    logger_build_send_log_msg(&unk_B6474, 0, "Failed to open CM certificate file!\n", 0);
    return v7;
  }
  v8 = read(v6, &buf, 0x2B0u);
  if ( v8 == 688 )
  {
    v40 = 0;
    v35 = 0;
    ptr = 0;
    v28 = 0;
    v36 = 0;
    v37 = 0;
    v38 = 0;
    v39 = 0;
    v31 = 0;
    v32 = 0;
    v33 = 0;
    v34 = 0;
    printf("\n%s: **** privateKey retrieved from NVRAM (len: %d):\n", &unk_B6480, 688);
    if ( ProdDb_GetLanMacAddr(v29) )
Reply
#3
Cant you add 00000000000000000000000 before/after the file to match the byte count?
Reply
#4
(01-09-2017, 10:35 PM)ricktendo Wrote: Cant you add 00000000000000000000000 before/after the file to match the byte count?
you can Decrypt it .like the way in forceware.
Reply
#5
undefined
undefined
Reply
#6
(01-09-2017, 11:04 PM)bx8055 Wrote:
(01-09-2017, 10:35 PM)ricktendo Wrote: Cant you add 00000000000000000000000 before/after the file to match the byte count?
you can Decrypt it .like the way in forceware.

Which way you mean?
Reply
#7
Anyway to share how you put cert into 6190 ??
Reply
#8
(31-08-2017, 01:30 PM)christianrodher Wrote: i get that error when using sb6121 certs in sb6190. Ive never seen it before. anyone knows why or how can it be fix?

[ERROR] [DOCSIS.BPI(pid=263)]: Decrypt Auth Key: Couldn't format PKCS#8 private key into PKCS#1 format!
[WARNING] [DOCSIS.BPI(pid=263)]: Decryption of Auth key failed
[ERROR] [COMMON_COMPONENTS.TLV_PARSER(pid=263)]: The apply handler, before handling sub-TLVs: type 7 return error
[ERROR] [COMMON_COMPONENTS.TLV_PARSER(pid=263)]: ApplyTlvParseHandlers Failed.
[ERROR] [DOCSIS.BPI(pid=263)]: BPI CheckAuthReply: Tlv Parse Failed, -8
[ERROR] [DOCSIS.BPI(pid=263)]: BPI: Auth Reply failed validity check!!

Christian, did you glitch the bootloader to gain access to it? Also, are you using the firmware that is available on github to check out the c source code?
Reply
#9
bitware?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)