How to Understand Remote Key Injection - Revision history

Mahong: Replaced content with "{{Migrating|https://smartpossdk.gitbook.io/cloudpossdk/faq/key-injection/understand-remote-key-injection}}"

2024-04-08T05:13:49Z

Replaced content with "{{Migrating|https://smartpossdk.gitbook.io/cloudpossdk/faq/key-injection/understand-remote-key-injection}}"

← Older revision		Revision as of 05:13, 8 April 2024
Line 1:		Line 1:
	~~== PCI PIN 3.1 Certified OTA Remote Key Injection Anywhere ==~~		{{Migrating\|https://smartpossdk.gitbook.io/cloudpossdk/faq/key-injection/understand-remote-key-injection}}
	~~=== Overview ===~~
	* WizarPOS has developed a Remote Key Injection (RKI) system that is PCI PIN 3.1 certified, meeting the needs for secure, remote key injection.
	* This system allows customers to inject keys into their terminals remotely and securely, particularly useful for those without their own key injection systems or a secure key injection environment.
	~~=== Benefits of WizarPOS RKI: ===~~
	* '''Enhanced Security:''' Prevents interception or manual manipulation of keys and data.
	* '''Cost-Effective:''' Reduces the need for personnel training and certification, lowering overall costs.
	* '''Scalability:''' Ideal for distributors or service providers needing to inject keys into multiple POS terminals at different locations.
	* '''PCI PIN 3.1 Approval:''' Ensures compliance with industry security standards.
	~~=== Key Features ===~~
	* '''Mutual Authentication:''' Ensures a secure channel between devices and servers.
	* '''Protocol Support:''' Complies with TR31 and TR34 key exchange block protocols.
	* '''Key Type Support:''' Compatible with all major key types.
	~~=== [http~~://~~ftp~~.~~wizarpos~~.~~com~~/~~advanceSDK~~/~~RemoteKeyManagementSystem.pdf Remote Key Injection (RKI) solution] ===~~
	~~=== [http://ftp.wizarpos.com~~/~~advanceSDK/RKMSUserManual.pdf RKMS user manual] ===~~
	~~== Developing Remote Key Injection ==~~
	~~=== Integrating to Existing Host Server ===~~
	* For integrating with an existing host server, provide documentation on how the server works with the terminal side for customized agent adaptor development.
	* AIDL Interface: WizarPOS offers two terminal AIDL interfaces, as demonstrated in ''''For Systems Without an Existing Host Server''''.
	~~<syntaxhighlight lang="java">~~
	~~int importKeyInfo(in byte[] keyInfo);~~
	~~byte[] getAuthInfo();~~
	~~</syntaxhighlight>~~
	~~=== For Systems Without an Existing Host Server: ===~~
	* Developing a remote key injection ~~system from scratch is time~~-~~consuming and typically uncertified by PCI, making it suitable only for testing or internal use.~~
	* WizarPOS offers a remote key injection ~~demo system for reference, including:~~
	** [http://ftp.wizarpos.com/advanceSDK/cloudPOS_remote_key_injection_demo_system.pdf cloudPOS_remote_key_injection_demo_system manual], it describes the whole demo system, and the detail information for the certificates, core process.
	** [https://github.com/SmartPOSSamples/InjectKeyDemo.git Terminal APP]
	** [https://github.com/SmartPOSSamples/RemoteKeyInjectServer.git Server Project]
	*** ''Remote_Key_Inject_Deployment.docx'', it describes how to deploy and run the keyinjection jar in server.
	* The demo uses a certificate that replaces the original terminal certificate. Download the [http://ftp.wizarpos.com/advanceSDK/InitCertForRemotekeyInject_201903131833.apk initialize certificate APK] and run it to initialize the demo certificate. [http://sdkwiki.wizarpos.com/index.php?title=How_to_Clear_Terminal_Certificates Clearing the demo certificate] is necessary after use.
	~~'''Note:'''~~
	While WizarPOS provides a comprehensive RKI solution, the demo system is for reference and testing purposes only. When deploying in a live environment, ensure to replace the demo certificate with a valid, secure certificate.

Mahong at 07:41, 31 January 2024

2024-01-31T07:41:05Z

← Older revision		Revision as of 07:41, 31 January 2024
Line 27:		Line 27:
	** [http://ftp.wizarpos.com/advanceSDK/cloudPOS_remote_key_injection_demo_system.pdf cloudPOS_remote_key_injection_demo_system manual], it describes the whole demo system, and the detail information for the certificates, core process.		** [http://ftp.wizarpos.com/advanceSDK/cloudPOS_remote_key_injection_demo_system.pdf cloudPOS_remote_key_injection_demo_system manual], it describes the whole demo system, and the detail information for the certificates, core process.
	** [https://github.com/SmartPOSSamples/InjectKeyDemo.git Terminal APP]		** [https://github.com/SmartPOSSamples/InjectKeyDemo.git Terminal APP]
	** [https://github.com/SmartPOSSamples/~~InjectKeyDemo~~.git Server Project]		** [https://github.com/SmartPOSSamples/RemoteKeyInjectServer.git Server Project]
	*** ''Remote_Key_Inject_Deployment.docx'', it describes how to deploy and run the keyinjection jar in server.		*** ''Remote_Key_Inject_Deployment.docx'', it describes how to deploy and run the keyinjection jar in server.
	* The demo uses a certificate that replaces the original terminal certificate. Download the [http://ftp.wizarpos.com/advanceSDK/InitCertForRemotekeyInject_201903131833.apk initialize certificate APK] and run it to initialize the demo certificate. [http://sdkwiki.wizarpos.com/index.php?title=How_to_Clear_Terminal_Certificates Clearing the demo certificate] is necessary after use.		* The demo uses a certificate that replaces the original terminal certificate. Download the [http://ftp.wizarpos.com/advanceSDK/InitCertForRemotekeyInject_201903131833.apk initialize certificate APK] and run it to initialize the demo certificate. [http://sdkwiki.wizarpos.com/index.php?title=How_to_Clear_Terminal_Certificates Clearing the demo certificate] is necessary after use.
	'''Note:'''		'''Note:'''
	While WizarPOS provides a comprehensive RKI solution, the demo system is for reference and testing purposes only. When deploying in a live environment, ensure to replace the demo certificate with a valid, secure certificate.		While WizarPOS provides a comprehensive RKI solution, the demo system is for reference and testing purposes only. When deploying in a live environment, ensure to replace the demo certificate with a valid, secure certificate.

Mahong at 07:35, 31 January 2024

2024-01-31T07:35:44Z

← Older revision		Revision as of 07:35, 31 January 2024
Line 24:		Line 24:
	=== For Systems Without an Existing Host Server: ===		=== For Systems Without an Existing Host Server: ===
	* Developing a remote key injection system from scratch is time-consuming and typically uncertified by PCI, making it suitable only for testing or internal use.		* Developing a remote key injection system from scratch is time-consuming and typically uncertified by PCI, making it suitable only for testing or internal use.
	* WizarPOS offers a [http://ftp.wizarpos.com/advanceSDK/~~remotekeyinjectiondemosystem_20240117~~.~~zip demo system~~] ~~for reference, including:~~		* WizarPOS offers a remote key injection demo system for reference, including:
	** ''Terminal APP'' and ''Server Application''.		** [http://ftp.wizarpos.com/advanceSDK/cloudPOS_remote_key_injection_demo_system.pdf cloudPOS_remote_key_injection_demo_system manual], it describes the whole demo system, and the detail information for the certificates, core process.
	** Documentation:		** [https://github.com/SmartPOSSamples/InjectKeyDemo.git Terminal APP]
	*** ''wizarPOS_remote_key_injection_demo_system.docx'', it describes the whole demo system, and the detail information for the certificates, core process.		** [https://github.com/SmartPOSSamples/InjectKeyDemo.git Server Project]
	*** ''Remote_Key_Inject_Deployment.docx'', it describes how to deploy and run the keyinjection jar in server.		*** ''Remote_Key_Inject_Deployment.docx'', it describes how to deploy and run the keyinjection jar in server.
	* The demo uses a certificate that replaces the original terminal certificate. Download the [http://ftp.wizarpos.com/advanceSDK/InitCertForRemotekeyInject_201903131833.apk initialize certificate APK] and run it to initialize the demo certificate. [http://sdkwiki.wizarpos.com/index.php?title=How_to_Clear_Terminal_Certificates Clearing the demo certificate] is necessary after use.		* The demo uses a certificate that replaces the original terminal certificate. Download the [http://ftp.wizarpos.com/advanceSDK/InitCertForRemotekeyInject_201903131833.apk initialize certificate APK] and run it to initialize the demo certificate. [http://sdkwiki.wizarpos.com/index.php?title=How_to_Clear_Terminal_Certificates Clearing the demo certificate] is necessary after use.
	'''Note:'''		'''Note:'''
	While WizarPOS provides a comprehensive RKI solution, the demo system is for reference and testing purposes only. When deploying in a live environment, ensure to replace the demo certificate with a valid, secure certificate.		While WizarPOS provides a comprehensive RKI solution, the demo system is for reference and testing purposes only. When deploying in a live environment, ensure to replace the demo certificate with a valid, secure certificate.

Mahong: /* For Systems Without an Existing Host Server: */

2024-01-17T01:59:40Z

For Systems Without an Existing Host Server:

← Older revision		Revision as of 01:59, 17 January 2024
Line 24:		Line 24:
	=== For Systems Without an Existing Host Server: ===		=== For Systems Without an Existing Host Server: ===
	* Developing a remote key injection system from scratch is time-consuming and typically uncertified by PCI, making it suitable only for testing or internal use.		* Developing a remote key injection system from scratch is time-consuming and typically uncertified by PCI, making it suitable only for testing or internal use.
	* WizarPOS offers a [http://ftp.wizarpos.com/advanceSDK/~~remotekeyinjectiondemosystem_20220307~~.zip demo system] for reference, including:		* WizarPOS offers a [http://ftp.wizarpos.com/advanceSDK/remotekeyinjectiondemosystem_20240117.zip demo system] for reference, including:
	** ''Terminal APP'' and ''Server Application''.		** ''Terminal APP'' and ''Server Application''.
	** Documentation:		** Documentation:

Simon no use: Simon moved page Remote Key Injection to How to Understand Remote Key Injection: Normalize the title

2024-01-14T02:18:13Z

Simon moved page Remote Key Injection to How to Understand Remote Key Injection: Normalize the title

← Older revision

Revision as of 02:18, 14 January 2024

Simon no use at 02:15, 14 January 2024

2024-01-14T02:15:57Z

← Older revision		Revision as of 02:15, 14 January 2024
Line 1:		Line 1:
	== PCI PIN 3.1 Certified OTA Remote Key Injection Anywhere ==		== PCI PIN 3.1 Certified OTA Remote Key Injection Anywhere ==
	~~In order to meet~~ the needs ~~of customers~~ for ~~remote key injection~~, ~~we have developed a~~ remote key injection ~~system and passed PCI authentication~~. ~~Customers can directly use this~~ system to inject keys into their terminals~~. For customers who do not have~~ their own key injection ~~system and do not have~~ a secure ~~environment for~~ key injection~~, we recommend using WizarPOS RKI~~.		=== Overview ===
	~~The~~ WizarPOS ~~Remote Key Injection (~~RKI~~) solution turbocharges data encryption in a hassle-free and cost-effective manner. Remote Key Injection is a process for the secure transfer~~ of ~~encryption~~ keys ~~between a payment terminal~~ and ~~a remote server~~. ~~Compared to its on~~-~~premises counterpart~~, ~~RKI prevents keys or data from interception or manual manipulation~~. ~~It is also scalable when a distributor~~ or service ~~provider injects~~ keys ~~to unlimited~~ POS terminals in different locations~~. In addition, RKI eliminates personnel training and certification costs.~~		* WizarPOS has developed a Remote Key Injection (RKI) system that is PCI PIN 3.1 certified, meeting the needs for secure, remote key injection.
	* WizarPOS RKMS allows you remote key injection of your devices.		* This system allows customers to inject keys into their terminals remotely and securely, particularly useful for those without their own key injection systems or a secure key injection environment.
	* ~~WizarPOS RKMS is~~ PCI PIN 3.1 ~~approved~~.		=== Benefits of WizarPOS RKI: ===
	* ~~All~~ devices and servers ~~are connected in mutual authenticated secure channel~~.		* '''Enhanced Security:''' Prevents interception or manual manipulation of keys and data.
	* Support TR31 and TR34 key exchange block ~~protocol~~.		* '''Cost-Effective:''' Reduces the need for personnel training and certification, lowering overall costs.
	* Support all major key types.		* '''Scalability:''' Ideal for distributors or service providers needing to inject keys into multiple POS terminals at different locations.
			* '''PCI PIN 3.1 Approval:''' Ensures compliance with industry security standards.
			=== Key Features ===
			* '''Mutual Authentication:''' Ensures a secure channel between devices and servers.
			* '''Protocol Support:''' Complies with TR31 and TR34 key exchange block protocols.
			* '''Key Type Support:''' Compatible with all major key types.
	=== [http://ftp.wizarpos.com/advanceSDK/RemoteKeyManagementSystem.pdf Remote Key Injection (RKI) solution] ===		=== [http://ftp.wizarpos.com/advanceSDK/RemoteKeyManagementSystem.pdf Remote Key Injection (RKI) solution] ===
	=== [http://ftp.wizarpos.com/advanceSDK/RKMSUserManual.pdf RKMS user manual] ===		=== [http://ftp.wizarpos.com/advanceSDK/RKMSUserManual.pdf RKMS user manual] ===
	== Developing Remote Key Injection ==		== Developing Remote Key Injection ==
	=== Integrating to ~~existed host server~~ ===		=== Integrating to Existing Host Server ===
	~~==== Agent Adaptor ====~~		* For integrating with an existing host server, provide documentation on how the server works with the terminal side for customized agent adaptor development.
	~~Please~~ provide ~~the document about~~ how the ~~host~~ server works with terminal side~~. Then we can develop and provide the~~ agent adaptor.		* AIDL Interface: WizarPOS offers two terminal AIDL interfaces, as demonstrated in ''''For Systems Without an Existing Host Server''''.

	~~====~~ AIDL Interface~~====~~
	~~We have provided~~ two terminal AIDL interfaces~~. Please refer to that demo system~~ in ~~[[No existed host server]], which provides detailed instructions on how to call these two interfaces~~.
	<syntaxhighlight lang="java">		<syntaxhighlight lang="java">
	int importKeyInfo(in byte[] keyInfo);		int importKeyInfo(in byte[] keyInfo);
	byte[] getAuthInfo();		byte[] getAuthInfo();
	</syntaxhighlight>		</syntaxhighlight>
			=== For Systems Without an Existing Host Server: ===
	=== ~~No existed host server~~ ===		* Developing a remote key injection system from scratch is time-consuming and typically uncertified by PCI, making it suitable only for testing or internal use.
	~~If developing~~ a remote injection ~~key~~ system from scratch~~, both the server and terminal injection applications need to be developed simultaneously, which will be a very~~ time-consuming ~~task. Moreover, the developed system has not been certified~~ by PCI ~~and can~~ only ~~be used~~ for testing or internal use. ~~Therefore, it is recommended to use a~~ WizarPOS ~~Remote Key Injection. But we also provide~~ a [http://ftp.wizarpos.com/advanceSDK/remotekeyinjectiondemosystem_20220307.zip demo system] ~~that can be used as a~~ reference ~~for development needs.~~		* WizarPOS offers a [http://ftp.wizarpos.com/advanceSDK/remotekeyinjectiondemosystem_20220307.zip demo system] for reference, including:
			** ''Terminal APP'' and ''Server Application''.
	~~In the demo system zip package includes~~:		** Documentation:
			*** ''wizarPOS_remote_key_injection_demo_system.docx'', it describes the whole demo system, and the detail information for the certificates, core process.
	''Terminal APP''		*** ''Remote_Key_Inject_Deployment.docx'', it describes how to deploy and run the keyinjection jar in server.
			* The demo uses a certificate that replaces the original terminal certificate. Download the [http://ftp.wizarpos.com/advanceSDK/InitCertForRemotekeyInject_201903131833.apk initialize certificate APK] and run it to initialize the demo certificate. [http://sdkwiki.wizarpos.com/index.php?title=How_to_Clear_Terminal_Certificates Clearing the demo certificate] is necessary after use.
	''Server Application''		'''Note:'''
			While WizarPOS provides a comprehensive RKI solution, the demo system is for reference and testing purposes only. When deploying in a live environment, ensure to replace the demo certificate with a valid, secure certificate.
	~~''Documents~~:''

	''wizarPOS_remote_key_injection_demo_system.docx'', it describes the whole demo system, and the detail information for the certificates, core process.

	''Remote_Key_Inject_Deployment.docx'', it describes how to deploy and run the keyinjection jar in server.

	* ~~'''In the~~ demo ~~system, we use~~ the ~~demo~~ certificate~~, so download~~ the [http://ftp.wizarpos.com/advanceSDK/InitCertForRemotekeyInject_201903131833.apk initialize certificate APK] and run it to initialize the demo certificate.~~'''~~
	~~Note: the demo above will replace the original certificate of the terminal. When you no longer need demo, you need to~~ [http://sdkwiki.wizarpos.com/index.php~~/How_to_clear_terminal_certificate clear~~ the demo certificate].

Mahong: /* Integrating to existed host server */

2023-09-13T07:51:31Z

Integrating to existed host server

← Older revision		Revision as of 07:51, 13 September 2023
Line 12:		Line 12:
	=== Integrating to existed host server ===		=== Integrating to existed host server ===
	==== Agent Adaptor ====		==== Agent Adaptor ====
	Please provide the document about how the ~~backend processing system~~ works with terminal side. Then we can develop and provide the agent adaptor.		Please provide the document about how the host server works with terminal side. Then we can develop and provide the agent adaptor.

	==== AIDL Interface====		==== AIDL Interface====
Line 20:		Line 20:
	byte[] getAuthInfo();		byte[] getAuthInfo();
	</syntaxhighlight>		</syntaxhighlight>

	=== No existed host server ===		=== No existed host server ===
	If developing a remote injection key system from scratch, both the server and terminal injection applications need to be developed simultaneously, which will be a very time-consuming task. Moreover, the developed system has not been certified by PCI and can only be used for testing or internal use. Therefore, it is recommended to use a WizarPOS Remote Key Injection. But we also provide a [http://ftp.wizarpos.com/advanceSDK/remotekeyinjectiondemosystem_20220307.zip demo system] that can be used as a reference for development needs.		If developing a remote injection key system from scratch, both the server and terminal injection applications need to be developed simultaneously, which will be a very time-consuming task. Moreover, the developed system has not been certified by PCI and can only be used for testing or internal use. Therefore, it is recommended to use a WizarPOS Remote Key Injection. But we also provide a [http://ftp.wizarpos.com/advanceSDK/remotekeyinjectiondemosystem_20220307.zip demo system] that can be used as a reference for development needs.

Mahong: /* Agent Adaptor */

2023-09-13T07:51:04Z

Agent Adaptor

← Older revision		Revision as of 07:51, 13 September 2023
Line 12:		Line 12:
	=== Integrating to existed host server ===		=== Integrating to existed host server ===
	==== Agent Adaptor ====		==== Agent Adaptor ====
	Please provide the document about how it works with terminal side. Then we can develop and provide the agent adaptor.		Please provide the document about how the backend processing system works with terminal side. Then we can develop and provide the agent adaptor.

	==== AIDL Interface====		==== AIDL Interface====
	We have provided two terminal AIDL interfaces. Please refer to that demo system in [[No existed host server]], which provides detailed instructions on how to call these two interfaces.		We have provided two terminal AIDL interfaces. Please refer to that demo system in [[No existed host server]], which provides detailed instructions on how to call these two interfaces.

Mahong at 08:43, 11 September 2023

2023-09-11T08:43:05Z

← Older revision		Revision as of 08:43, 11 September 2023
Line 1:		Line 1:
	== PCI PIN 3.1 Certified OTA Remote Key Injection Anywhere ==		== PCI PIN 3.1 Certified OTA Remote Key Injection Anywhere ==
			In order to meet the needs of customers for remote key injection, we have developed a remote key injection system and passed PCI authentication. Customers can directly use this system to inject keys into their terminals. For customers who do not have their own key injection system and do not have a secure environment for key injection, we recommend using WizarPOS RKI.
	The WizarPOS Remote Key Injection (RKI) solution turbocharges data encryption in a hassle-free and cost-effective manner. Remote Key Injection is a process for the secure transfer of encryption keys between a payment terminal and a remote server. Compared to its on-premises counterpart, RKI prevents keys or data from interception or manual manipulation. It is also scalable when a distributor or service provider injects keys to unlimited POS terminals in different locations. In addition, RKI eliminates personnel training and certification costs.		The WizarPOS Remote Key Injection (RKI) solution turbocharges data encryption in a hassle-free and cost-effective manner. Remote Key Injection is a process for the secure transfer of encryption keys between a payment terminal and a remote server. Compared to its on-premises counterpart, RKI prevents keys or data from interception or manual manipulation. It is also scalable when a distributor or service provider injects keys to unlimited POS terminals in different locations. In addition, RKI eliminates personnel training and certification costs.
	* WizarPOS RKMS allows you remote key injection of your devices.		* WizarPOS RKMS allows you remote key injection of your devices.
Line 8:		Line 9:
	=== [http://ftp.wizarpos.com/advanceSDK/RemoteKeyManagementSystem.pdf Remote Key Injection (RKI) solution] ===		=== [http://ftp.wizarpos.com/advanceSDK/RemoteKeyManagementSystem.pdf Remote Key Injection (RKI) solution] ===
	=== [http://ftp.wizarpos.com/advanceSDK/RKMSUserManual.pdf RKMS user manual] ===		=== [http://ftp.wizarpos.com/advanceSDK/RKMSUserManual.pdf RKMS user manual] ===
	== ~~Develop remote~~ Key Injection ==		== Developing Remote Key Injection ==
	=== ~~Integrated~~ to existed host server ===		=== Integrating to existed host server ===
	==== Agent ~~adaptor~~ ====		==== Agent Adaptor ====
	Please provide the document about how it works with terminal side. Then we can develop and provide the agent adaptor.		Please provide the document about how it works with terminal side. Then we can develop and provide the agent adaptor.
	==== AIDL ~~API~~ ====		==== AIDL Interface====
	~~The terminal~~ provided ~~the~~ two ~~apis, detail information, please~~ refer to [[No host server]].		We have provided two terminal AIDL interfaces. Please refer to that demo system in [[No existed host server]], which provides detailed instructions on how to call these two interfaces.
	<syntaxhighlight lang="java">		<syntaxhighlight lang="java">
	int importKeyInfo(in byte[] keyInfo);		int importKeyInfo(in byte[] keyInfo);
	byte[] getAuthInfo();		byte[] getAuthInfo();
	</syntaxhighlight>		</syntaxhighlight>
	=== No host server ===		=== No existed host server ===
	If ~~develop~~ from ~~starting~~, ~~need develop~~ server and terminal injection ~~apk~~, ~~here~~ is a [http://ftp.wizarpos.com/advanceSDK/remotekeyinjectiondemosystem_20220307.zip demo system]~~, but it is only~~ a demo system~~, don't suggest to use it directly.~~		If developing a remote injection key system from scratch, both the server and terminal injection applications need to be developed simultaneously, which will be a very time-consuming task. Moreover, the developed system has not been certified by PCI and can only be used for testing or internal use. Therefore, it is recommended to use a WizarPOS Remote Key Injection. But we also provide a [http://ftp.wizarpos.com/advanceSDK/remotekeyinjectiondemosystem_20220307.zip demo system] that can be used as a reference for development needs.
	~~The~~ zip package includes:
			In the demo system zip package includes:

	''Terminal APP''		''Terminal APP''
Line 32:		Line 34:
	''Remote_Key_Inject_Deployment.docx'', it describes how to deploy and run the keyinjection jar in server.		''Remote_Key_Inject_Deployment.docx'', it describes how to deploy and run the keyinjection jar in server.

	* '''In ~~our~~ demo system, we use the demo certificate, so download the [http://ftp.wizarpos.com/advanceSDK/InitCertForRemotekeyInject_201903131833.apk initialize certificate APK] and run it to initialize the demo certificate.'''		* '''In the demo system, we use the demo certificate, so download the [http://ftp.wizarpos.com/advanceSDK/InitCertForRemotekeyInject_201903131833.apk initialize certificate APK] and run it to initialize the demo certificate.'''
	Note ~~that~~ the demo above will replace the original certificate of the terminal. When you no longer need demo, you need to [http://sdkwiki.wizarpos.com/index.php/How_to_clear_terminal_certificate clear the demo certificate].		Note: the demo above will replace the original certificate of the terminal. When you no longer need demo, you need to [http://sdkwiki.wizarpos.com/index.php/How_to_clear_terminal_certificate clear the demo certificate].

Mahong: /* Develop remote Key Injection */

2023-09-11T08:08:16Z

Develop remote Key Injection

← Older revision		Revision as of 08:08, 11 September 2023
Line 11:		Line 11:
	=== Integrated to existed host server ===		=== Integrated to existed host server ===
	==== Agent adaptor ====		==== Agent adaptor ====
	Please provide the document about how it works with terminal side. Then we can develop and provide the agent adaptor.		Please provide the document about how it works with terminal side. Then we can develop and provide the agent adaptor.
	==== AIDL API ====		==== AIDL API ====
	The terminal provided the two apis, detail information, please refer to [[No host server]].		The terminal provided the two apis, detail information, please refer to [[No host server]].
	<syntaxhighlight lang="java">		<syntaxhighlight lang="java">
	int importKeyInfo(in byte[] keyInfo);		int importKeyInfo(in byte[] keyInfo);