Add some notes on signing configuration while building Servo on OpenHarmony platform

[RichardTjokroutomo]

Added some additional notes on signing configuration step for those who intend to use Linux to develop Servo for OpenHarmony platform.

This will be helpful since the signing configuration step needs DevEco Studio to complete (at least if you're developing Servo for HarmonyOS devices), meanwhile DevEco Studio is presently only available on Windows & MacOS.

[RichardTjokroutomo]

cc @jschwe

[jschwe]

Perhaps add a disclaimer here that the signing information is tied to the bundlename, so you can't just copy it from any other test app you might have, the bundlename needs to match (which it does for the linked ServoDemo).

[jschwe]

This will be helpful since the signing configuration step needs DevEco Studio to complete, meanwhile DevEco Studio is presently only available on Windows & MacOS.

So for OpenHarmony DevEco Studio is not required, the secret is essentially public, and one can trvially generate the signing material as documented in the OpenHarmony docs. (It's not a security issue, since upstream OpenHarmony is essentially a demo platform, and any downstream distribution would change the signing keys (or leave them away in the first place).

For HarmonyOS DevEco is the easiest way. I've seen that there is now documentation how to generate signing configs via commandline and a website for HarmonyOS, but I haven't tried it out. I'd probably

[RichardTjokroutomo]

This will be helpful since the signing configuration step needs DevEco Studio to complete, meanwhile DevEco Studio is presently only available on Windows & MacOS.

So for OpenHarmony DevEco Studio is not required, the secret is essentially public, and one can trvially generate the signing material as documented in the OpenHarmony docs. (It's not a security issue, since upstream OpenHarmony is essentially a demo platform, and any downstream distribution would change the signing keys (or leave them away in the first place).

For HarmonyOS DevEco is the easiest way. I've seen that there is now documentation how to generate signing configs via commandline and a website for HarmonyOS, but I haven't tried it out. I'd probably

I see. My bad...

[jschwe]

Suggested change

	>For Linux users, DevEco Studio is only available on Windows and MacOS. To proceed, **you will need another Windows / MacOS machine with DevEco Studio IDE installed** to create the signing keys. If you're developing for OpenHarmony boards (such as HopeRun development board), then you can name the `SigningConfigs` `default`. Otherwise, set it to `hos` if you're developing Servo for HarmonyOS devices (such as Huawei Mate series phones).
	>For Linux users, DevEco Studio is only available on Windows and MacOS. To proceed, **you will need another Windows / MacOS machine with DevEco Studio IDE installed** to create the signing keys.
	If you're developing for OpenHarmony boards (such as HopeRun development board), then you can name the `SigningConfigs` `default`.
	Otherwise, set it to `hos` if you're developing Servo for HarmonyOS devices.

[jdm]

Suggested change

	To generate the information needed for password encryption, the required application and profile certificate files, and the keystore itself, you can clone a [sample ArkTS app](https://github.com/jschwe/ServoDemo) and open it on DevEco Studio IDE. Note that since signing information is tied to the bundle name, not all ArkTS app will work, and therefore it is **highly** recommended to use the sample ArkTS app mentioned above.
	To generate the information needed for password encryption, the required application and profile certificate files, and the keystore itself, you can clone a [sample ArkTS app](https://github.com/jschwe/ServoDemo) and open it on DevEco Studio IDE.
	Note that since signing information is tied to the bundle name, not all ArkTS app will work, and therefore it is **highly** recommended to use the sample ArkTS app mentioned above.