Languages

Menu
Sites
Language
Is it normal that .wgt files Tizen Studio builds via 'Build Signed Package' aren't encrypted?

Is it normal that .wgt files Tizen Studio builds via 'Build Signed Package' aren't encrypted?

The built packages can be easily opened to get .js files which aren't encrypted. Should I have done something before building the package?

I found someone's .wgt file in the Internet once and when I opened it all the files were encrypted, so I couldn't see code.

Edited by: Anonymous on 03 May, 2019
List

Responses

1 Replies
Armaan-Ul- Islam

Encrypt HTML/js/CSS Code:

In your config.xml file Tizen tab > Setting > Encryption > enable

or if you love to code:

<tizen:setting background-support="disable" encryption="enable" hwkey-event="enable"/>

 

How this encryption is handled behind the scene is shared in TizenWiki. Check this link for details:

https://wiki.tizen.org/wiki/Security/Tizen_3.X_Key_Manager_Web_App_Encryption_Support

Though it shares some stuff about Tizen 3.0, but the idea is similar.

 

Point to be Noted:

This Encryption is handled while installation. Packaging with encryption feature is handled by Tizen store. When you would submit your file & they would find encryption="enable" , The Store would take care the of the package distributed being encrypted. The general '.wgt' file on your local machine would still be unzipable, But the downloadable package from Tizen store would be encrypted.