Releases: SCRT-HQ/PEMEncrypt
Releases · SCRT-HQ/PEMEncrypt
PEMEncrypt v0.2.1
Changelog
0.2.1 - 2019-08-24
- Issue #5
- Added: Missing path creation to
New-RSAKeyPair
if the parent folder does not yet exist.
- Added: Missing path creation to
- Miscellaneous
- Fixed: Error handling while using
New-RSAKeyPair -Interactive
if the specified Path already exists and-Force
was not specified. - Added: Additional status updates within
New-RSAKeyPair
for a better understanding of what step the key generation is at.
- Fixed: Error handling while using
Instructions
- Click here to download the PEMEncrypt.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PEMEncrypt
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PEMEncrypt # Otherwise, provide the path to the manifest: Import-Module -Path C:\MyPSModules\PEMEncrypt\0.2.1\PEMEncrypt.psd1
PEMEncrypt v0.2.0
Changelog
0.2.0 - 2019-08-10
- Added
New-RSAKeyPair
to enable generation of RSA PEM and SSH keys directly from PowerShell- Supports password protection keys
- Defaults to 4096 key length
- Offers an Interactive mode using the
-Interactive
or-i
switch to simulatessh-keygen
experience
- Updated README with command comparisons between
openssl
,ssh-keygen
andNew-RSAKeyPair
Instructions
- Click here to download the PEMEncrypt.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PEMEncrypt
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PEMEncrypt # Otherwise, provide the path to the manifest: Import-Module -Path C:\MyPSModules\PEMEncrypt\0.2.0\PEMEncrypt.psd1
PEMEncrypt v0.1.1
Changelog
0.1.1 - 2019-07-07
- Added CHANGELOG, CODE_OF_CONDUCT, CONTRIBUTING docs
- Updated README with relevant badges and overall info on installing/upgrading/using the module
- Added comment-based help on the included functions
- Removed KeyLength parameter from
Protect-PEMString
(now calculating from the Modulus BitLength, so it's not necessary to specify) - Updated
*Key
parameters on both functions to allow passing the string formatted Key directly instead of the path to it.
Instructions
- Click here to download the PEMEncrypt.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PEMEncrypt
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PEMEncrypt # Otherwise, provide the path to the manifest: Import-Module -Path C:\MyPSModules\PEMEncrypt\0.1.1\PEMEncrypt.psd1
PEMEncrypt v0.1.0
Changelog
0.1.0
- Initial release to the PowerShell Gallery
- Included functions are
Protect-PEMString
andUnprotect-PEMString
- Fixed deployment issue
Instructions
- Click here to download the PEMEncrypt.zip file attached to the release.
- If on Windows: Right-click the downloaded zip, select Properties, then unblock the file.
This is to prevent having to unblock each file individually after unzipping.
- Unzip the archive.
- (Optional) Place the module folder somewhere in your
PSModulePath
.You can view the paths listed by running the environment variable
$env:PSModulePath
- Import the module, using the full path to the PSD1 file in place of
PEMEncrypt
if the unzipped module folder is not in yourPSModulePath
:# In $env:PSModulePath Import-Module PEMEncrypt # Otherwise, provide the path to the manifest: Import-Module -Path C:\MyPSModules\PEMEncrypt\0.1.0\PEMEncrypt.psd1