UniKey User Manual - Revision history

Mapril: /* Popular License types */

2018-04-10T00:29:58Z

Popular License types

← Older revision		Revision as of 11:29, 10 April 2018
Line 851:		Line 851:
	UniKey Security Keys support many different licensing models by giving you the power to ensure software license compliance, allowing you to choose how to grow your business:		UniKey Security Keys support many different licensing models by giving you the power to ensure software license compliance, allowing you to choose how to grow your business:

			* <b>Perpetual</b>: Upfront one off payment for all functionality of the product.
	* <b>Feature Based</b>: Enables or disables product features according to customer needs and charges only for the functionality they use.		* <b>Feature Based</b>: Enables or disables product features according to customer needs and charges only for the functionality they use.
	* <b>Rental</b>: Offers software rentals and charges periodically for software applications, modules or features.		* <b>Rental</b>: Offers software rentals and charges periodically for software applications, modules or features.
Line 898:		Line 899:
	====Serial Number/CD keys====		====Serial Number/CD keys====
	Licensing software with a serial number is a widely used method, but if the computation is performed in memory, it can be easily cracked. We can move this computation into a UniKey dongle, taking advantage of User-Defined Algorithms and the MD5 hashing function. We suggest that serial numbers should work in addition to MD5 making cracking extremely difficult.		Licensing software with a serial number is a widely used method, but if the computation is performed in memory, it can be easily cracked. We can move this computation into a UniKey dongle, taking advantage of User-Defined Algorithms and the MD5 hashing function. We suggest that serial numbers should work in addition to MD5 making cracking extremely difficult.


	===Distributing and protecting software===		===Distributing and protecting software===

Mapril at 23:49, 9 April 2018

2018-04-09T23:49:17Z

← Older revision		Revision as of 10:49, 10 April 2018
Line 92:		Line 92:
	: Operation of this product is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.		: Operation of this product is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
	<br><br><br>		<br><br><br>
	[[File:USB Logo.png\|left\|100px\|top]] The equipment of ~~UniMate~~ is USB based.		[[File:USB Logo.png\|left\|100px\|top]] The equipment of UniKey is USB based.
	<br><br><br>		<br><br><br>
	; Conformity to ISO 9001<nowiki>:</nowiki>2000		; Conformity to ISO 9001<nowiki>:</nowiki>2000

Cynthia: /* UniKey PRO */

2018-03-15T00:29:14Z

UniKey PRO

← Older revision		Revision as of 11:29, 15 March 2018
Line 191:		Line 191:

	====UniKey PRO====		====UniKey PRO====
	If your application can work over a LAN, and you need to control a number of concurrent users, then you should select UniKey PRO. The maximum number of concurrent remote clients can be set ~~up to~~ 65535.		If your application can work over a LAN, and you need to control a number of concurrent users, then you should select UniKey PRO. The maximum number of concurrent remote clients can be set is 65535.

	<div style="clear:both;"></div>		<div style="clear:both;"></div>

Cynthia at 00:27, 15 March 2018

2018-03-15T00:27:46Z

← Older revision		Revision as of 11:27, 15 March 2018
Line 85:		Line 85:
	; CE Attestation of Conformity		; CE Attestation of Conformity
	[[File:CE Attestation.png\|left\|100px\|top]]		[[File:CE Attestation.png\|left\|100px\|top]]
	: ~~UniMate~~ is in conformity with the protection requirements of CE Directives 89/336/EEC Amending Directive 92/31/EEC. ~~UniMate~~ satisfies the limits and verifying methods: EN55022/CISPR 22 Class B, EN55024: 1998.		: UniKey is in conformity with the protection requirements of CE Directives 89/336/EEC Amending Directive 92/31/EEC. UniKey satisfies the limits and verifying methods: EN55022/CISPR 22 Class B, EN55024: 1998.
	<br><br><br>		<br><br><br>
	; FCC Standard		; FCC Standard
Line 100:		Line 100:
	; ROHS		; ROHS
	[[File:ROHS.png\|left\|100px\|top]]		[[File:ROHS.png\|left\|100px\|top]]
	: All ~~UniMate~~ products are environmentally friendly with ROHS certificates.		: All UniKey products are environmentally friendly with ROHS certificates.
	<br><br><br><br>		<br><br><br><br>

Cynthia: /* Trouble shooting and FAQs */

2018-02-12T04:26:38Z

Trouble shooting and FAQs

← Older revision		Revision as of 15:26, 12 February 2018
Line 946:		Line 946:

	<b>Q: Can I modify the password of a UniKey dongle?</b>		<b>Q: Can I modify the password of a UniKey dongle?</b>
	: Yes. Each UniKey dongle can only generate a new password <b><u>TWICE</u></b>.		: Yes. Each UniKey dongle can only generate a new password <b><u>TWICE</u></b>. Dongle will have to be sent back to SecuTech for resetting if password has to be reset again.

	<b>Q: Can others duplicate my UniKey dongle?</b>		<b>Q: Can others duplicate my UniKey dongle?</b>
	: No. Please keep ~~your~~ seed for your passwords in a safe place. Without knowing the seed, no one can generate the same password.		: No. Please keep the seed for your passwords in a safe place. Without knowing the seed, no one can generate the same password.

	<b>Q: What operating system does UniKey support?</b>		<b>Q: What operating system does UniKey support?</b>
Line 958:		Line 958:

	<b>Q; How can learn about using a UniKey?</b>		<b>Q; How can learn about using a UniKey?</b>
	: In the SDK, you can find a Quick Start file, which gives you a quick guide ~~about~~ how to use the UniKey.		: In the SDK, you can find a Quick Start file, which gives you a quick guide of how to use the UniKey.

	<b>Q: What is driverless?</b>		<b>Q: What is driverless?</b>

Cynthia at 06:00, 9 February 2018

2018-02-09T06:00:10Z

← Older revision		Revision as of 17:00, 9 February 2018
Line 2:		Line 2:
	==<b>UniKey Manual</b>==		==<b>UniKey Manual</b>==

	<b><i>Version 8.4</i></b>		<b><i>Version 8.5</i></b>

	<table class="wikitable">		<table class="wikitable">
Line 26:		Line 26:
	<td>8.3</td>		<td>8.3</td>
	<td>8.4</td>		<td>8.4</td>
			<td>8.5</td>
	</tr>		</tr>
	<tr>		<tr>
Line 48:		Line 49:
	<td>2016.7</td>		<td>2016.7</td>
	<td>2017.4</td>		<td>2017.4</td>
			<td>2018.2</td>
	</tr>		</tr>
	</table>		</table>

Cynthia: /* Programming Languages */

2018-02-09T05:59:10Z

Programming Languages

← Older revision		Revision as of 16:59, 9 February 2018
Line 923:		Line 923:

	====Programming Languages====		====Programming Languages====
	The choice of programming language is important in software protection. A compiled programming language ~~is the best choice,~~ such as C++ and Delphi. When using these types of programming languages, you do not need to worry too much about decompiling the source code, resulting in better software protection. An interpreted programming language such as FoxPro is somewhat weak, since it can be decompiled to obtain the source code or semi-source code. Only calling UniKey APIs is not strong enough to protect your software, ~~here~~ we offer 3 solutions:		The choice of programming language is important in software protection. A compiled programming language such as C++ and Delphi is highly recommended. When using these types of programming languages, you do not need to worry too much about decompiling the source code, resulting in better software protection. An interpreted programming language such as FoxPro is somewhat weak, since it can be decompiled to obtain the source code or semi-source code. Only calling UniKey APIs is not strong enough to protect your software, hence we offer 3 solutions:

	* <b>Save software credentials in the UniKey dongle</b>: Take advantage of ~~the~~ user-defined and seed algorithms, ~~this~~ is totally separate to reading/writing and checking the dongle attachment. Involving the UniKey dongle in computations will greatly strengthen your software protection.		* <b>Save software credentials in the UniKey dongle</b>: Take advantage of user-defined and seed algorithms in UniKey, which is totally separate to reading/writing and checking the dongle attachment. Involving the UniKey dongle in computations will greatly strengthen your software protection.
	* <b>Pack certain functions into a DLL file to enhance software protection</b>: A DLL file is compiled and is difficult to decompile. We avoid the weaknesses of interpreted programming languages and take advantage of compiled programming languages via a DLL.		* <b>Pack certain functions into a DLL file to enhance software protection</b>: A DLL file is compiled and is difficult to decompile. We avoid the weaknesses of interpreted programming languages and take advantage of compiled programming languages via a DLL.
	* <b>Make a stub/packer for the interpreter</b>: The interpreter interprets high level code into machine code. In general, a compiled programming language compiles an interpreter. Making a stub/packer will add software protection codes into it and make the interpreter work with the UniKey dongles. This solution applies with Flash or e-Book etc.		* <b>Make a stub/packer for the interpreter</b>: The interpreter interprets high level code into machine code. In general, a compiled programming language compiles an interpreter. Making a stub/packer will add software protection codes into it and make the interpreter work with the UniKey dongles. This solution applies with Flash or e-Book etc.

Cynthia: /* Software Development */

2018-02-09T05:55:17Z

Software Development

← Older revision		Revision as of 16:55, 9 February 2018
Line 920:		Line 920:

	====Software Development====		====Software Development====
	As discussed, the person who is developing the software protection code should be trusted. To avoid future problems, please refer to the source code in the UniKey SDK CD. In most cases, you do not need to compose a lot of code, you only need to modify the samples in the SDK, and then ~~refactor~~ that into your source code.		As discussed, the person who is developing the software protection code should be a trusted personnel. To avoid future problems, please refer to the source code in the UniKey SDK CD. In most cases, you do not need to compose a lot of code, you only need to modify the samples provided in the SDK, and then include that into your source code.

	====Programming Languages====		====Programming Languages====

Cynthia: /* Dongle Passwords */

2018-02-09T05:54:03Z

Dongle Passwords

← Older revision		Revision as of 16:54, 9 February 2018
Line 913:		Line 913:

	====Dongle Passwords====		====Dongle Passwords====
	SecuTech ~~Solution Inc.~~ thinks from a customer ~~point of view~~, by breaking the tradition of burning passwords at the dongle distributor side. Software vendors can burn their own passwords on their end and handle password storage by themselves, which is a far more ~~secure~~ solution. In order to burn a UniKey dongle password, you need to input a seed, and the password will be generated based on that seed.		SecuTech thinks from a customer viewpoint, by breaking the tradition of burning passwords at the dongle distributor side. Software vendors can burn their own passwords on their end and handle password storage by themselves, which is a far more secured solution. In order to burn a UniKey dongle's password, you need to input a seed value, and the password will be generated based on that seed.

	The password generation algorithm is irreversible, i.e. no one can generate the same password without knowing your seed. When a new password is generated, a file containing the date, seed and newly generated password will be created in the working directory. Please keep this file in a safe place.		The password generation algorithm is irreversible, i.e. no one can generate the same password without knowing your seed. When a new password is generated, a file containing the date, seed and newly generated password will be created in the working directory. Please keep this file in a safe place.

	Please note that each UniKey dongle can only generate a new password twice. If this fails or you want to change the password, you have to return the UniKey dongle to SecuTech ~~Solution Inc~~.		Please note that each UniKey dongle can only generate a new password twice. If this fails or you want to change the password, you will have to return the UniKey dongle to SecuTech for resetting.

	====Software Development====		====Software Development====

Cynthia: /* People */

2018-02-09T05:49:04Z

People

← Older revision		Revision as of 16:49, 9 February 2018
Line 910:		Line 910:

	====People====		====People====
	~~The individual who makes~~ the software protection ~~work is important and should be trusted~~. If the software protection source code is open to others or the public, the software protection is exposed and others can attempt to crack the protected software. Another solution is to divide the software protection into several parts and have each developer ~~take one~~ part. Since they do not communicate or share source code with each other, the software protection as a whole is harder to ~~leak~~. ~~We suggest~~ that only trusted ~~personnels~~ have access to the code.		Only specific personnel should be entrusted with the software protection tasks. If the software protection source code is open to others or the public, the software protection is exposed and others can attempt to crack the protected software. Another solution is to divide the software protection into several parts and have each developer responsible for only part of the task. Since they do not communicate or share source code with each other, the software protection as a whole is harder to crack. However, SecuTech suggests that only trusted personnel have access to the code.

	====Dongle Passwords====		====Dongle Passwords====