Discussion: Launch wsltty as a signed Appx Package or unsigned ZIP file

Question

Discussion: Launch wsltty as a signed Appx Package or unsigned ZIP file

Biswa96 opened this issue 6 years ago · comments

Continuing discussion from mintty/wsltty #63.

As a signed Appx: Extract wsltty.zip in the cloned wsltty.appx folder. Then run the build.cmd script which make appx and signed it with users own signed certificate. The folder structure of wsltty.zip will be like following:

Folder structure (click to open)

+---bin
|       cygwin-console-helper.exe
|       cygwin1.dll
|       mintty.exe
|       wslbridge-backend
|       wslbridge.exe
|       
+---usr
    +---share
        +---mintty
            +---lang
            +---themes

But user does need the Windows SDK tools to sign (and may be Build tools). This procedure secures the package installation and user doesn't need to enable Developer mode.

As a unsigned ZIP: User can download it from release page directly (will be added). Then extract ZIP file and run the command from powershell: Add-AppxPackage -Path <Path_To_AppxManifest.xml> -Register. The folder structure of build folder like following:

Folder structure (click to open)

+build
|
|   AppxManifest.xml
|   resources.pri
|   
+---Assets
|       
+---bin
|       cygwin-console-helper.exe
|       cygwin1.dll
|       Launcher.exe
|       Launcher.exe.config
|       mintty.exe
|       wslbridge-backend
|       wslbridge.exe
|       wsltty.ico
|       
+---usr
    +---share
        +---mintty
            +---lang
            +---themes

With this procedure user does not need any developer tools but needs to enable Developer mode in Settings. This also is not certified.
Further Details will be added later.

mintty · Answer 1 · Sat Mar 31 2018 06:29:07 GMT+0800 (China Standard Time)

Sounds good... how does it work? Surprised it should be as easy after all the build trouble we've had before. I would be curious about some background.
(Note that I'm offline for a few days now.)

mintty · Answer 2 · Sat Mar 31 2018 17:01:48 GMT+0800 (China Standard Time)

Yes; can you please explain the background, how this is related to Windows Store apps? Thanks.

Biswapriyo Nath · Answer 3 · Sun Apr 01 2018 04:34:36 GMT+0800 (China Standard Time)

You may think it as a offline-portable installer. Here I explain the difference between the Appx installation and Add-AppxPacakge command.

With signed AppX package:
- Pros: Secured with certificate. User can't tamper the package and installed files. Less privileges. Developer mode not required.
- Cons: Developer has to provide AppX and self-signed Certificate both. Users have to install the certificate before installing the AppX. This process may seem to be boring to users.
With unsigned unpackaged files (wsltty.zip):
- Pros: Just run the command Add-AppxPackage -Path <Path_To_AppxManifest.xml> -Register from powershell and installed. Users like this. And also easy to repair, just uninstall and re-install. Developers has not to provide certificates.
- Cons: Unsecured. Users can tamper files. More privileges. Users have to enable developer mode.

See this article: https://www.howtogeek.com/285410/
About Add-AppxPackage command: https://technet.microsoft.com/en-us/library/hh856048.aspx

Click to see the details of command

>Registers an application in development mode. You can use development mode to install applications from a folder of unpackaged files. You can use the –Register parameter to test your Windows® Store apps before you deploy them as app packages (.appx). To register an existing app package (.appx) installation, you must specify the –DisableDevelopmentMode parameter along with -Register.

Biswapriyo Nath · Answer 4 · Sun Apr 01 2018 13:55:24 GMT+0800 (China Standard Time)

I've successfully install wsltty in UWP environment with Add-AppxPackage command without launcher. I'll provide a temporary link to try it. But there are two problems (probably in mintty).

mintty can't find the wsltty.ico which has to be appear in mintty window. Add the default wsltty.ico, like mintty.exe --icon .wsltty.ico.
mintty can't save its configuration. It shows error ./home/<user_name>/.minttyrc could not saved. So mintty (renamed to wsltty) has to create that ./home/.minttyrc file manually.

mintty · Answer 5 · Sun Apr 01 2018 22:49:32 GMT+0800 (China Standard Time)

I'm getting an error 0x80070005 "Permission denied". Started from an admin-shell.

About the two errors:

You could deploy the icon and copy it to usr/share/mintty/icon in the launcher. Or it might be linked in as a resource in the wsltty build, but I'd prefer the lighter option.
Wondering about "Saved Pictures"; how does it get in here? Anyway, after starting from an auxiliary place (where it was copied), the configdir should be $APPDATA/wsltty, and since option --configdir is not an option, I'll add that to the implicit configuration triggered by being wsltty.exe.

Biswapriyo Nath · Answer 6 · Sun Apr 01 2018 22:57:25 GMT+0800 (China Standard Time)

Have you enable developer mode in settings?
As I said before one can install that unpacked installation process from any folder, so I saved in "Pictures" folder.
There should be no option to launch wsltty for this method. It will be better if wsltty automatically create that folder and file. Like (not real functions, just idea):

GetEnvironment(%UserName%);
CreateFolder(%CurrentFolder%\\home\\%UserName%\\.minttyrc)

mintty · Answer 7 · Tue Apr 03 2018 05:52:36 GMT+0800 (China Standard Time)

For the icon, I'd prefer if you deploy it with the package as described. Please also the new charnames.txt file. I've just uploaded patches for both to the wsltty repository.

About implied --configdir "$APPDATA"/wsltty, I plan to take care of that tomorrow. Also about path conversion (mintty/wsltty#91).

mintty · Answer 8 · Tue Apr 03 2018 19:02:54 GMT+0800 (China Standard Time)

I think I found the best way to handle the --configdir issue. Untested, please check.

About the icon, the launcher sets --icon \"{exePath}\\wsltty.ico\". Would exePath here refer to the target location of copied files? Then wsltty.ico needs to be copied too.

mintty · Answer 9 · Tue Apr 03 2018 19:04:22 GMT+0800 (China Standard Time)

For the deployment without launcher, wsltty.ico would have to be deployed as wsl.ico in the location I indicated.

Biswapriyo Nath · Answer 10 · Tue Apr 03 2018 20:57:31 GMT+0800 (China Standard Time)

I said that if you install from install.cmd (i.e. without launcher/appx) you don't need to copy. All happen from execution path as in wsltty.

I've tested latest mintty. But the two errors remains. 1. I've added the wsl.ico in /usr/share/mintty/icon folder but it doesn't appear in mintty window. 2. When I want to save the preferences it shows this error: "Couldn't save options to <box_icon>: No such file or directory". My idea: At first launch, mintty automatically creates the /home/<user_name> folder and .minttyrc file if they are not present.

Biswapriyo Nath · Answer 11 · Mon May 07 2018 22:45:08 GMT+0800 (China Standard Time)

Do you know details about openssl commands? I've seen an article that .pfx file can be created with openssl commands. That may be replaced with Windows SDK tools. Users may sign Appx with openssl in cygwin (or alternatives).
Here is the article: https://www.ssl.com/how-to/create-a-pfx-p12-certificate-file-using-openssl/

mintty · Answer 12 · Tue May 08 2018 02:09:57 GMT+0800 (China Standard Time)

I once created a pgp key with openssl and it was such a nightmare to find out how it works inmidst the vast poorly structured documentation that I do not feel like repeating that experience. I have the impression you are quite good at investigating such procedures. If the whole signing could be done with openssl that would indeed be great; I do not know it.

mintty · Answer 13 · Tue May 08 2018 19:30:31 GMT+0800 (China Standard Time)

Closing this issue after the signed appx package has been launched.
About openssl signing, you may open another issue if you like, or just find out...

mintty · Answer 14 · Tue May 08 2018 19:32:30 GMT+0800 (China Standard Time)

Actually, the page you linked to explains how to create a .pfx, not how to create a .cer which is needed first.