Jump to content
Sign in to follow this  
killercode

what is HERE map encryption system?

Recommended Posts

I think yes, based on Nissan Connect LCN2 manual map data on HERE SD-Card are encrypted by Bosch company, therefore user can't change data on SD-Card, but I'm still working on it, I'm looking for a way how can I copy OpenstreetMap on HERE SD-Card, moreover I believe for solve this problem I'll know what encryption method used by Bosch for encryption, as well as I did many research and then I think they used Advance Data Encryption tools and may be they used AES-256 encryption method(this is a my guess), anyway I'll know who has same experience, about this issue

Share this post


Link to post
Share on other sites

Lurker I didn't understand what is you mean, if you mean is any more information, I can say I analysed files in HERE sd-card I found a xml this is content of that file: all file encrypted by Bosch company, I'm trying decrypt files, I guess these files encrypted by AES-cbc-256 bit by "Advance File Encryption" software

<?xml version="1.0" encoding="utf-8"?>
<RBCM_SIGNATURE>
    <META_INFO timestamp="2016-05-20T07:25:41">
        <OPERATOR name="LCN2KAI" />
        <PROGRAM name="sd_sign2" major="1" minor="18" />
    </META_INFO>
    <REVOKED_KEYS timestamp="2017-04-04T10:00:00">
        <LIST>
        </LIST>
        <BOSCH_SIGNATURE length="48">
            0xf8, 0x17, 0xd5, 0x45, 0xc4, 0x0a, 0x63, 0x12,
            0xe2, 0xec, 0xa9, 0x49, 0x84, 0xe7, 0xd0, 0x4a,
            0x45, 0xdb, 0x2b, 0x33, 0x00, 0x00, 0x00, 0x00,
            0x46, 0x68, 0xf4, 0xc9, 0x85, 0xb5, 0x65, 0xe9,
            0x18, 0x36, 0xa2, 0x72, 0x31, 0xd4, 0x8a, 0x4f,
            0x4b, 0xef, 0x89, 0x5a, 0x00, 0x00, 0x00, 0x00
        </BOSCH_SIGNATURE>
    </REVOKED_KEYS>
    <PARTITION title="Partition #1">
        <ID cid="" vin="" did="" />
        <LIFETIME start="2016-05-20T07:25:41" end="" />
        <HASH_FILE_LIST>
            <HASH_FILE offset="0" numberofbytes="0" filename="\CRYPTNAV\MEDIUM.CFG" />
            <HASH_FILE offset="0" numberofbytes="0" filename="\CRYPTNAV\DATA\DATA\MISC\TP_META.DAT" />
            <HASH_FILE offset="0" numberofbytes="2048" filename="\CRYPTNAV\DATA\DATA\MISC\CONTENT.DAT" />
            <HASH_FILE offset="0" numberofbytes="2048" filename="\CRYPTNAV\DATA\CONNECT\RNW\NAV_ROOT.DAT" />
            <HASH_FILE offset="0" numberofbytes="2048" filename="\CRYPTNAV\DATA\CONNECT\LID\CONNECT.DAT" />
            <HASH_FILE offset="0" numberofbytes="0" filename="\CRYPTNAV\DATA\CONNECT\MAP\IDX_CNT.TBL" />
            <HASH_FILE offset="0" numberofbytes="0" filename="\CRYPTNAV\DATA\CONNECT\MAP\RPITABLE.RPI" />
            <HASH_FILE offset="0" numberofbytes="0" filename="\CRYPTNAV\DNL\BIN\NAV\CHKSUMS.MD5" />
        </HASH_FILE_LIST>
        <OPERATOR_PUBLIC_KEY>
            <KEY length="40">
                0xb5, 0x7b, 0x8b, 0x2f, 0x5d, 0x9c, 0xce, 0xb9,
                0x3c, 0x52, 0x15, 0xcc, 0xbc, 0x68, 0x6c, 0xf9,
                0x4d, 0x34, 0xfe, 0xa0, 0xc2, 0xe7, 0xfc, 0xf0,
                0x7f, 0x72, 0x85, 0x83, 0x04, 0x63, 0x59, 0xe8,
                0x8d, 0x1a, 0x91, 0xa1, 0xaf, 0x56, 0x6c, 0x2d
            </KEY>
            <BOSCH_SIGNATURE length="48">
                0xee, 0x5e, 0x09, 0xae, 0x50, 0xef, 0x7f, 0x55,
                0xeb, 0x61, 0x0f, 0xc0, 0x7e, 0x6e, 0x85, 0x0d,
                0x7c, 0xdd, 0x09, 0x07, 0x00, 0x00, 0x00, 0x00,
                0x77, 0x42, 0x9d, 0x0c, 0x3f, 0x72, 0x80, 0x97,
                0xd5, 0xa2, 0x73, 0x4f, 0x70, 0x20, 0xea, 0x29,
                0x16, 0x16, 0x86, 0x85, 0x00, 0x00, 0x00, 0x00
            </BOSCH_SIGNATURE>
        </OPERATOR_PUBLIC_KEY>
        <OPERATOR_SIGNATURE length="48">
            0xd0, 0x0d, 0xb4, 0x03, 0x09, 0xd6, 0x2f, 0x77,
            0x77, 0xd2, 0x7b, 0x90, 0x2c, 0xf3, 0x6c, 0x61,
            0xfb, 0x5b, 0xbd, 0x08, 0x00, 0x00, 0x00, 0x00,
            0x92, 0x88, 0x59, 0xb4, 0x21, 0x04, 0xf6, 0xb9,
            0xef, 0xb2, 0x46, 0xfe, 0x84, 0x15, 0xc2, 0xb6,
            0x7b, 0x4b, 0xb2, 0x2b, 0x00, 0x00, 0x00, 0x00
        </OPERATOR_SIGNATURE>
    </PARTITION>
</RBCM_SIGNATURE>
 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.