Research Triangle PowerShell Users Group Tools for Automation, 9 Sep 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: PowerShell Lightning Talk: Convert Scoop and Winget Packages to Chocolatey with Stephen Valdinger

Description

Stephen Valdinger discusses some scripts he created to convert / import Scoop and WinGet packages into Chocolatey. Stephen is a support engineer for Chocolatey and active PowerShell community member.

Research Triangle PowerShell Users Group (RTPSUG) is the largest PowerShell group in the world! We meet twice a month to discuss all topics related to PowerShell and automation. Our topics cover beginner to advanced concepts and offer people a chance to learn new skills and ask questions. One of the foundations that we live by is to create a space to for all to attendees to feel welcome, have a chance to ask questions and be part of a community. For more information on our group, please visit any of following links:

WEB: www.rtpsug.com
MEETUP: https://www.meetup.com/Research-Triangle-PowerShell-Users-Group
LINKEDIN: https://www.linkedin.com/company/rtpsug/
TWITTER: https://twitter.com/rtpsug
GITHUB: https://github.com/rtpsug

A

Probably heard of a couple of these things out here, let me just make this a little bigger. So by now everybody's probably heard of scoop scoop is a package manager for Windows, and also when get is the new Microsoft package, manager' windows.

A

We also have a package manager I work for chocolaty, so we thought it would be really cool if in the off-chance I there's not something in our community or depository, that either scoop or wink it has or you're coming from the scoop and Wingate ecosystem and you're used to using their manifests is what they call their in their package: definitions to quickly generate chocolaty packages. Out of that, so I've got a little PowerShell function that I've written. That does just that.

A

So, for example, if we take this 7-zip package out here on the Windgate repository and we look at the yamo file, this is the definition for a winget package and if we click this raw link and grab it- and we come back here to our powerful window and then I'll just copy in this URL and I'm, going to push it directly to convert to chocolate package and I'm going to tell it where to store it and I've got a packages. Folder created right here from this repository.

A

What this is going to do is it's going to invoke chocolaty on the back end of things, and it's going to read that manifest file and it's going to generate a chocolaty package for you and just a couple of seconds and if we look inside of here, we've got our tools directory, there's the sevens at the MSI from the manifest it went ahead and downloaded that put it into the package, and if we look at the chocolaty installed on ps1, this is the powershell script that actually installs the package.

A

You can see I'm using the business version version of chocolaty here, so we were able to automatically detect these silent arguments for that binary and write the packaging so that this is completely offline and ready to go. And similarly, if you are ready to deploy this in your environment like do, I don't think I have the extension on here. So if I were to do something like c packages and then do.

A

Chucko push.

A

That and my source.

A

Why did I call it I, think I call it greased lightning and once it force.

A

And that's up there ready to go so now. If I wanted to do, Chaco install 7-zip from and I think I called the friendly name of this package.

A

See I've already got it installed, so it's not going to yeah I can divorce if I want to. Maybe oh, if I would actually learn how to type this would go easier right. Cursive doing it live.

A

So that's how you can convert a scoop package or a wing it packaged into a chocolaty package. This is eventually going to make it into chocolate a proper as just a command. You can run and we're looking at putting it into the open source version, as well as the business version. Obviously the business version here it lights it up a little better and that you get a completely offline package out of it.

A

The open-source version doesn't have the functionality to automatically detect those silent, install switches and things like that, but will get you 80% of the way there on the open source side. So that's that one and then real, quick I've got this other function that is broken on the this machine for reasons that are unbeknownst to me, I think it's because I'm run server 2019, but I haven't really diagnose it.

A

Yet I copied this from somewhere else, but just to show that off and show this off and I'll throw this up on github somewhere so that we can link it later. But I wrote this quick function called disable TLS protocol err choco.

A

We have some requirements where we have to test some of our our central management stuff against hardened environments, where folks that are in air gap networks it things like that have very stringent TLS requirements, so this function allows me to disable TLS one zero one, one one, two SSL three kind of on the fly I can pick one or many of these and it'll go down through. Basically, it just creates some registry keys and turns the client server things disabled by default. To one then turns those particular cyphers off the I'm touching the registry.

A

In this way it does require reboot, so I throw a prompt at the end of it. Asking him probably want to restart the computer and if I answer yes or why it'll restart the computer so relatively straightforward, it doesn't do anything terribly complex or crazy, but if you do need to disable TLS in a hurry in the most dirty way possible, this script will do it. There is a built-in powershell, commandlets called disable TLS cipher suite.

A

That does a slightly different thing in that the actual individual cipher suites can be removed with that command lit, and we use that in conjunction with this to kind of disable TLS environments, while we're testing things just to make sure when we do encounter a situation where a customer has a really lockdown environment or something like that did we have an answer that we can give them saying: oh yeah, it's because this cipher suites not there. You need to do this, another great tool that you can use actually to audit and change a system.

A

There's the IAS crypto tool. It has a command line version and a GUI version that enables you to really quickly back up your registry and then make configuration, changes and reboot a server to manage your TLS stuff. But that's this in a nutshell: that's all I've got all right.