Navicat Keygen

This repository will tell you how Navicat offline activation works.

1. Keyword Explanation.

Navicat Activation Public Key

It is a RSA-2048 public key that Navicat used to encrypt or decrypt offline activation information.

It is stored in navicat.exe as a kind of resource called RCData. The resource name is "ActivationPubKey". You can see it by a kind of software Resource Hacker. The concrete content is:

-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAw1dqF3SkCaAAmMzs889I
qdW9M2dIdh3jG9yPcmLnmJiGpBF4E9VHSMGe8oPAy2kJDmdNt4BcEygvssEfginv
a5t5jm352UAoDosUJkTXGQhpAWMF4fBmBpO3EedG62rOsqMBgmSdAyxCSPBRJIOF
R0QgZFbRnU0frj34fiVmgYiLuZSAmIbs8ZxiHPdp1oD4tUpvsFci4QJtYNjNnGU2
WPH6rvChGl1IRKrxMtqLielsvajUjyrgOC6NmymYMvZNER3htFEtL1eQbCyTfDmt
YyQ1Wt4Ot12lxf0wVIR5mcGN7XCXJRHOFHSf1gzXWabRSvmt1nrl7sW6cjxljuuQ
awIDAQAB
-----END PUBLIC KEY-----

If you have the corresponding private key, please tell me. I would be very appreciated for your generous.

NOTICE:

Start from Navicat Premium 12.0.25, Navicat do not load this public key from resource in navicat.exe. Actually the public key is stored in libcc.dll and encrypted. And to avoid being replaced easily, the public key is split into 5 parts:

The content below is discovered from libcc.dll of Navicat Premium x64 12.0.25 Simplified Chinese version. SHA256 value is 607e0a84c75966b00f3d12fa833e91d159e4f51ac51b6ba66f98d0c3cbefdce0. I do not guaranteed that offset value is absolutely correct in other versions. But char string and immediate values is highly possible to be found.
1. At file offset + 0x1A12090 in libcc.dll, stored as char string:
  
  "D75125B70767B94145B47C1CB3C0755E
  7CCB8825C5DCE0C58ACF944E08280140
  9A02472FAFFD1CD77864BB821AE36766
  FEEDE6A24F12662954168BFA314BD950
  32B9D82445355ED7BC0B880887D650F5"
2. At file offset + 0x59D799 in libcc.dll, stored as immediate value in a instruction:
  
  0xFE 0xEA 0xBC 0x01
  
  In decimal: 29158142
3. At file offset + 0x1A11DA0 in libcc.dll, stored as char string:
  
  "E1CED09B9C2186BF71A70C0FE2F1E0AE
  F3BD6B75277AAB20DFAF3D110F75912B
  FB63AC50EC4C48689D1502715243A79F
  39FF2DE2BF15CE438FF885745ED54573
  850E8A9F40EE2FF505EB7476F95ADB78
  3B28CA374FAC4632892AB82FB3BF4715
  FCFE6E82D03731FC3762B6AAC3DF1C3B
  C646FE9CD3C62663A97EE72DB932A301
  312B4A7633100C8CC357262C39A2B3A6
  4B224F5276D5EDBDF0804DC3AC4B8351
  62BB1969EAEBADC43D2511D6E0239287
  81B167A48273B953378D3D2080CC0677
  7E8A2364F0234B81064C5C739A8DA28D
  C5889072BF37685CBC94C2D31D0179AD
  86D8E3AA8090D4F0B281BE37E0143746
  E6049CCC06899401264FA471C016A96C
  79815B55BBC26B43052609D9D175FBCD
  E455392F10E51EC162F51CF732E6BB39
  1F56BBFD8D957DF3D4C55B71CEFD54B1
  9C16D458757373E698D7E693A8FC3981
  5A8BF03BA05EA8C8778D38F9873D62B4
  460F41ACF997C30E7C3AF025FA171B5F
  5AD4D6B15E95C27F6B35AD61875E5505
  449B4E"
4. At file offset + 0x59D77F in libcc.dll, stored as immediate value in a instruction:
  
  0x59 0x08 0x01 0x00 (in decimal )
  
  In decimal: 67673
5. At file offset + 0x1A11D8C in libcc.dll, stored as char string:
  
  "92933"
Then output encrypted public key with format "%s%d%s%d%s", the order is the same as it list:

D75125B70767B94145B47C1CB3C0755E7CCB8825C5DCE0C58ACF944E082801409A02472FAFFD1CD77864BB821AE36766FEEDE6A24F12662954168BFA314BD95032B9D82445355ED7BC0B880887D650F529158142E1CED09B9C2186BF71A70C0FE2F1E0AEF3BD6B75277AAB20DFAF3D110F75912BFB63AC50EC4C48689D1502715243A79F39FF2DE2BF15CE438FF885745ED54573850E8A9F40EE2FF505EB7476F95ADB783B28CA374FAC4632892AB82FB3BF4715FCFE6E82D03731FC3762B6AAC3DF1C3BC646FE9CD3C62663A97EE72DB932A301312B4A7633100C8CC357262C39A2B3A64B224F5276D5EDBDF0804DC3AC4B835162BB1969EAEBADC43D2511D6E023928781B167A48273B953378D3D2080CC06777E8A2364F0234B81064C5C739A8DA28DC5889072BF37685CBC94C2D31D0179AD86D8E3AA8090D4F0B281BE37E0143746E6049CCC06899401264FA471C016A96C79815B55BBC26B43052609D9D175FBCDE455392F10E51EC162F51CF732E6BB391F56BBFD8D957DF3D4C55B71CEFD54B19C16D458757373E698D7E693A8FC39815A8BF03BA05EA8C8778D38F9873D62B4460F41ACF997C30E7C3AF025FA171B5F5AD4D6B15E95C27F6B35AD61875E5505449B4E6767392933

This encrypted public key can be decrypted by my another repo: how-does-navicat-encrypt-password, while the key used is b'23970790'

Example:
```
E:\GitHub>git clone https://github.com/DoubleLabyrinth/how-does-navicat-encrypt-password.git
...
E:\GitHub>cd how-does-navicat-encrypt-password\python3
E:\GitHub\how-does-navicat-encrypt-password\python3>python
Python 3.6.3 (v3.6.3:2c5fed8, Oct  3 2017, 18:11:49) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> from NavicatCrypto import *
>>> cipher = Navicat11Crypto(b'23970790')
>>> print(cipher.DecryptString('D75125B70767B94145B47C1CB3C0755E7CCB8825C5DCE0C58ACF944E082801409A02472FAFFD1CD77864BB821AE36766FEEDE6A24F12662954168BFA314BD95032B9D82445355ED7BC0B880887D650F529158142E1CED09B9C2186BF71A70C0FE2F1E0AEF3BD6B75277AAB20DFAF3D110F75912BFB63AC50EC4C48689D1502715243A79F39FF2DE2BF15CE438FF885745ED54573850E8A9F40EE2FF505EB7476F95ADB783B28CA374FAC4632892AB82FB3BF4715FCFE6E82D03731FC3762B6AAC3DF1C3BC646FE9CD3C62663A97EE72DB932A301312B4A7633100C8CC357262C39A2B3A64B224F5276D5EDBDF0804DC3AC4B835162BB1969EAEBADC43D2511D6E023928781B167A48273B953378D3D2080CC06777E8A2364F0234B81064C5C739A8DA28DC5889072BF37685CBC94C2D31D0179AD86D8E3AA8090D4F0B281BE37E0143746E6049CCC06899401264FA471C016A96C79815B55BBC26B43052609D9D175FBCDE455392F10E51EC162F51CF732E6BB391F56BBFD8D957DF3D4C55B71CEFD54B19C16D458757373E698D7E693A8FC39815A8BF03BA05EA8C8778D38F9873D62B4460F41ACF997C30E7C3AF025FA171B5F5AD4D6B15E95C27F6B35AD61875E5505449B4E6767392933'))
-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAw1dqF3SkCaAAmMzs889I
qdW9M2dIdh3jG9yPcmLnmJiGpBF4E9VHSMGe8oPAy2kJDmdNt4BcEygvssEfginv
a5t5jm352UAoDosUJkTXGQhpAWMF4fBmBpO3EedG62rOsqMBgmSdAyxCSPBRJIOF
R0QgZFbRnU0frj34fiVmgYiLuZSAmIbs8ZxiHPdp1oD4tUpvsFci4QJtYNjNnGU2
WPH6rvChGl1IRKrxMtqLielsvajUjyrgOC6NmymYMvZNER3htFEtL1eQbCyTfDmt
YyQ1Wt4Ot12lxf0wVIR5mcGN7XCXJRHOFHSf1gzXWabRSvmt1nrl7sW6cjxljuuQ
awIDAQAB
-----END PUBLIC KEY-----
```
Request Code

It is a Base64 string that represents 256-bytes-long data, while the 256-bytes-long data is the cipher text of the offline activation information encrypted by Navicat Activation Public Key.
Offline Activation Request Information

It is just a JSON-style ASCII string which contains 3 items. Respectively they are "K", "DI" and "P", which represent snKey, DeviceIdentifier (related with your machine), Platform (Appropriately speaking, it should be OS Type).

Like:

{"K": "xxxxxxxxxxxxxxxx", "DI": "yyyyyyyyyyyyy", "P": "WIN8"}
Activation Code

It is a Base64 string that represents 256-bytes-long data, while the 256-bytes-long data is the cipher text of the offline activation response information encrypted by Navicat Activation Private Key (so far, we don't know official activation private key).
Offline Activation Response Information

Just like Offline Activation Request Information, it is also a JSON-style ASCII string. But it contains 5 items. Respectively they are "K", "N", "O", "T", 'DI'.

"K" and "DI" has the same meaning mentioned in Offline Activation Request Information and must be same with the corresponding items in Offline Activation Request Information.

"N", "O", "T" represent Name, Organization, Time respectively. Name and Organization are string and the type of Time can be string or integer (Thanks for discoveries from @Wizr, issue #10).

"T" can be omitted.

snKey

It is a 4-block-long string, while every block is 4-chars-long.

snKey is generated by 10-bytes-long data. In order to explain it easily, I use uint8_t data[10] to represent the 10-bytes-long data.

data[0] and data[1] must be 0x68 and 0x2A respectively.

These two bytes are Naivcat signature number.
data[2], data[3] and data[4] can be any byte. Just set them whatever you want.

data[5] and data[6] are related with your Navicat product language.

Language	data[5]	data[6]	Discoverer
English	0xAC	0x88
简体中文	0xCE	0x32
繁體中文	0xAA	0x99
日本語	0xAD	0x82	@dragonflylee
Polski	0xBB	0x55	@dragonflylee
Español	0xAE	0x10	@dragonflylee
Français	0xFA	0x20	@Deltafox79
Deutsch	0xB1	0x60	@dragonflylee
한국어	0xB5	0x60	@dragonflylee
Русский	0xEE	0x16	@dragonflylee
Português	0xCD	0x49	@dragonflylee

According to symbol information in Navicat 12 for Mac x64, these two bytes are product language signature.

data[7] represents Navicat product ID. (Thanks @dragonflylee and @Deltafox79)

Product Name	Enterprise	Standard	Educational	Essentials
Navicat Report Viewer	0x0B
Navicat Data Modeler		0x47	0x4A
Navicat Premium	0x65		0x66	0x67
Navicat MySQL	0x68	0x69	0x6A	0x6B
Navicat PostgreSQL	0x6C	0x6D	0x6E	0x6F
Navicat Oracle	0x70	0x71	0x72	0x73
Navicat SQL Server	0x74	0x75	0x76	0x77
Navicat SQLite	0x78	0x79	0x7A	0x7B
Navicat MariaDB	0x7C	0x7D	0x7E	0x7F
Navicat MongoDB	0x80	0x81	0x82

High 4 bits of data[8] represents major version number. Low 4 bits is unknown, but we can use it to delay activation deadline. Possible value is 0000 or 0001.

Example:

For Navicat 12 x64: High 4 bits must be 1100, which is the binary of number 12.
For Navicat 11 x64: High 4 bits must be 1011, which is the binary of number 11.
data[9] is unknown, but you can set it 0xFD or 0xFC or 0xFB if you want to use not-for-resale license.

According to symbol information in Navicat 12 for Mac x64 version:
- 0xFB is Not-For-Resale-30-days license.
- 0xFC is Not-For-Resale-90-days license.
- 0xFD is Not-For-Resale-365-days license.
- 0xFE is Not-For-Resale license.
- 0xFF is Site license.

After that. Navicat use DES with ECB mode to encrypt the last 8 bytes which are from data[2] to data[9].

The DES key is:

unsigned char DESKey = { 0x64, 0xAD, 0xF3, 0x2F, 0xAE, 0xF2, 0x1A, 0x27 };

Then encode the 10-bytes-long data: (Use Base32 encode if you just want a conclusion.)

Regard uint8_t data[10] as a 80-bits-long data.

If uint8_t data[10] starts with 0x68 and 0x2A, so the 80-bits-long data is 01011000 00101010......
Divide the 80-bits-long data as 16 5-bits-long blocks.

If uint8_t data[10] starts with 0x68 and 0x2A, so the 80-bits-long data is 01011, 00000, 10101, 0...., ...
The values in every block are less than 32. Map them by a encode-table:
```
char EncodeTable[] = "ABCDEFGHIJKLMNOPQRSTUVWXYZ234567";
```
Then you will get a 16-char-long string.

If uint8_t data[10] starts with 0x68 and 0x2A, after encoded, it should starts with "N", "A", "V".
Divide the 16-char-long string to four 4-chars-long blocks, then you get snKey.

3. Activation Process

Check whether snKey that user inputs is legal.
After user clicks Activate, Navicat will start online activation first. If fails, users can choose offline activation.
Navicat will use the snKey that user inputs and some information collected from user's machine to generate Offline Activation Request Information, then encrypt it by Navicat Activation Public Key and return Base64-encoded string as Request Code.
In legal way, the Request Code should be sent to Navicat official activation server by a Internet-accessible computer. And Navicat official activation server will return a legal Activation Code.

But now, we use keygen to play the official activation server's role.
1. According to the Request Code, Get "DI" value and "K" value.
2. Fill Offline Activation Response Information with "K" value, name, organization name and "DI" value.
3. Encrypt Offline Activation Response Information by Navicat Activation Private Key and you will get 256-byte-long data.
4. Encode 256-byte-long data by Base64. The result is Activation Code.
Input Activation Code, then offline activation is done.

4. How to use

Download the latest release.

Replace Navicat Activation Public Key in navicat.exe or libcc.dll.

Example:

C:\Users\DoubleSine\Github\navicat-keygen\x64\Release>navicat-patcher.exe "C:\Program Files\PremiumSoft\Navicat Premium 12" RegPrivateKey.pem
Target has been found: navicat.exe
Solution0 has been done successfully.

Keyword0 has been found: offset = +0x02048200.
Keyword1 has been found: offset = +0x006C4E29.
Keyword2 has been found: offset = +0x02047F10.
Keyword3 has been found: offset = +0x006C4E0F.
Keyword4 has been found: offset = +0x02047F04.

@Offset +0x02048200, write string:
"D75125B70767B94145B47C1CB3C0755E7CCB8825C5DCE0C58ACF944E082801409A02472FAFFD1CD77864BB821AE36766FEEDE6A24F12662954168BFA314BD95032B9D82445355ED7784ADAC1C58775D2"

@Offset +0x006C4E29, write uint32_t:
0x0520738A

@Offset +0x02047F10, write string:
"20EEA059669FE4E949F414710A6C11CF68B5318B445D2D0CA85471E9DC382F271E974315F2F3645C2613BF60669584CF0A7531B1E5D2D281097E32A6B17286E8A9BDD06A17A036BC8949C9069CA3A166C251D325A7EAF81DB272CF4E277CC487D6BACB83C1059BBC0D45F49CBB6EA2C0E8033039CA575A939C8FF705FFA1FCA9DD53FD10447EE8D2F48128298E5DAB483F7A1500C455AFE33BB7FB280C39686CC45C7EC8C024EBF1089040D6636FF02E0E2A61092168A5CB105DBF3F5C6EB5C10D7392A46254B6E34DD4365F778ED199A52C6AB931416453CB8A677C90A6674BA5D546B25CDEC9C2E0B067729A6067FB1106B3BF7BBD56B888B5321484779570040B2095CD410D3B33F77BCFC9C24CA5A60003E342F110D35AA4714BFC8B3D9840BB3C8C286C5E353D5DEC4351A27E6E403AED2A21BBD0EA4194FB65B37F301A2E86BF9E9F8BBBFAA2400410ABC7833B3CCAAC66F27F873990E2D97BB36A70A5C9E4E3647C3AD0FAA716820A0BDC15CA8D7392"

@Offset +0x006C4E0F, write uint32_t:
0x00004708

@Offset +0x02047F04, write string:
"64308"

Solution1 has been done successfully.

Then in console:

C:\Users\DoubleSine\Github\navicat-keygen\x64\Release>navicat-keygen.exe RegPrivateKey.pem

You will be asked to select Navicat product, language and input major version number. After that an randomly generated snKey will be generated.

Example:

C:\Users\DoubleSine\Github\navicat-keygen\x64\Release>navicat-keygen.exe RegPrivateKey.pem
Select Navicat product:
0. DataModeler
1. Premium
2. MySQL
3. PostgreSQL
4. Oracle
5. SQLServer
6. SQLite
7. MariaDB
8. MongoDB
9. ReportViewer

(input index)> 1

Select product language:
0. English
1. Simplified Chinese
2. Traditional Chinese
3. Japanese
4. Polish
5. Spanish
6. French
7. German
8. Korean
9. Russian
10. Portuguese

(input index)> 0

(input major version number)> 12

Serial number:
NAVI-2ORL-MJQC-7WFO

Your name:

You can use this snKey to activate your Navicat preliminarily.

Then you will be asked to input Your name and Your organization. Just set them whatever you want, but not too long.

Example:

Your name: DoubleLabyrinth
Your organization: DoubleLabyrinth
Input request code (in Base64), input empty line to end:

After that, you will be asked to input the request code. Now DO NOT CLOSE KEYGEN.

Disconnect network and open Navicat. Find and click Registration. Fill Registration Key by snKey that keygen gave. Then click Activate.
Generally online activation will failed and Navicat will ask you do Manual Activation, just choose it.

Copy your request code and paste it in keygen. Input empty line to tell keygen that your input ends.

Example:

Your name: DoubleLabyrinth
Your organization: DoubleLabyrinth
Input request code (in Base64), input empty line to end:
J517hWX/29aQMITp5UfS/FarX6q8pFKmW1Cl7Nt2UpvmVxhZDn5YBdPw/htDsBbXacNpLtorxfZM
Jxv/SZMqHsr7/JqexaaAEfzn5mo6zpatcSRArFoQh2h9IcnjRqziZ8yihkMUesKgsWXvVXMEYk7u
D1rc/GhzTf6/2kn0gTKRAlJGsxt+e1p6SOhPuMyzt3AyNvJ2s0o607Nub7vC37FOJF69jN1nOvej
uy3bmr2HSPFsh10WqUUYi6F1lzzYIq6nDjQ5CeKrCT2jPfrhoFtRbwJyYDxQOxU/adrm1bg8VjrK
XNGeKS67R1nrbBM03IKzPP3pxEGFut4gZdskRw==

Request Info:
{"K":"NAVI2ORLMJQC7WFO", "DI":"Y2eJk9vrvfGudPG7Mbdn", "P":"WIN 8"}

Response Info:
{"K":"NAVI2ORLMJQC7WFO","DI":"Y2eJk9vrvfGudPG7Mbdn","N":"DoubleLabyrinth","O":"DoubleLabyrinth","T":1534251096}

License:
iFvqOkwsVq/Wutw/hELC5dyweDahl2v8R3bMWcNXS/V49CjpaDEJIHtRLddu/ldg
WVGdwdh3aHVJ5k8I6RkUicDvZJH2vLn3o5O9Q/A5ThED0AoYnwu0DLa1gEUlRO68
4+uXwo1nZ+xtjLOSxrVh+fLkcvKtd5RDgHS5957qUwjoYBiuePGomtt9mF4NtfaF
E7pnfP/OGp8xtWdUfGZ1fESWttKcVXcmOpyF4uTWtluUhFHRk+ZueST/ETyaSx33
Kv/zSLBbK8KaVqS2sh5WBs8xVaYxDV08EC8uCCp1euTFOPG5nlrcf7iyILsh6I67
xfGRliXvM67jvsxqD200fg==

Finally, you will get activation code which looks like a Base64 string. Just copy it and paste it in Navicat Manual Activation window, then click Activate. If nothing wrong, activation should be done successfully.

Name		Name	Last commit message	Last commit date
Latest commit History 35 Commits
navicat-keygen		navicat-keygen
navicat-patcher		navicat-patcher
openssl-lib		openssl-lib
rapidjson-lib		rapidjson-lib
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md
README.zh-CN.md		README.zh-CN.md
RegPrivateKey.pem		RegPrivateKey.pem
navicat-keygen.sln		navicat-keygen.sln

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Navicat Keygen

1. Keyword Explanation.

3. Activation Process

4. How to use

About

Releases

Packages

Languages

License

VeNoMouS/navicat-keygen

Folders and files

Latest commit

History

Repository files navigation

Navicat Keygen

1. Keyword Explanation.

3. Activation Process

4. How to use

About

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages