We can delete a key from a Python dictionary by the some following approaches.
Using the del keyword; it's almost the same approach like you did though -
myDict = {'one': 100, 'two': 200, 'three': 300 }
print(myDict) # {'one': 100, 'two': 200, 'three': 300}
if myDict.get('one') : del myDict['one']
print(myDict) # {'two': 200, 'three': 300}
Here we create the master key. We want only Certify capability: we use the master key only to create the subkeys, Sign - Encrypt - Authenticate capabilities will be assigned to the subkeys.
Run the following command to start the master key generation process. Select the set your own capabilities creation process (type 8)
▶ gpg --full-generate-key --expert
gpg (GnuPG) 2.2.9; Copyright (C) 2018 Free Software Foundation, Inc.
I am working on adding support for building and distributing (via PyPI) Python Wheels with C Extensions to the Python wheel and pip packages. The discussion on Distutils-SIG continues, but I believe it is fairly certain that some effort to correctly identify Linux distributions will need to be made. I've begun efforts to add this support to wheel.
If you have a Linux distribution or version of a listed distribution not in this gist, or one of the ones I have not directly verified, I could use the following:
/etc/os-release, if it exists
| import json | |
| import os | |
| class Settings: | |
| _config_location = 'config.json' | |
| def __init__(self): | |
| if os.path.exists(self._config_location): | |
| self.__dict__ = json.load(open(self._config_location)) |
On systems with UEFI Secure Boot enabled, recent Linux kernels will only load signed modules, so it's about time DKMS grew the capability to sign modules it's building.
These scripts are extended and scriptified variants of https://computerlinguist.org/make-dkms-sign-kernel-modules-for-secure-boot-on-ubuntu-1604.html and https://askubuntu.com/questions/760671/could-not-load-vboxdrv-after-upgrade-to-ubuntu-16-04-and-i-want-to-keep-secur/768310#768310 and add some error checking, a passphrase around your signing key, and support for compressed modules.
dkms-sign-module is a wrapper for the more generic sign-modules which can also be used outside of DKMS.
/root, say /root/module-signing, put the three scripts below in there and make them executable: chmod u+x one-time-setup sign-modules dkms-sign-module
| #!/usr/bin/env bash | |
| # | |
| # Author: Markus (MawKKe) [email protected] | |
| # Date: 2018-03-19 | |
| # | |
| # | |
| # What? | |
| # | |
| # Linux dm-crypt + dm-integrity + dm-raid (RAID1) | |
| # |
Recently, Let's Encrypt launched free wildcard certificates. While this is good news in and of itself, as it removes one of the last remaining reasons for expensive commercial certificates, I've unfortunately seen a lot of people dangerously misunderstand what wildcard certificates are for.
Therefore, in this brief post I'll explain why you probably shouldn't use a wildcard certificate, as it will put your security at risk.
It's generally pretty poorly understood (and documented!) how TLS ("SSL") works, so let's go through a brief explanation of the parts that are important here.
The general (simplified) idea behind how real-world TLS deployments work, is that you:
| # Proof-of-concept of an error- and stop-safe cleanup pattern. | |
| <# | |
| Note that accepting pipeline input for these functions is not supported | |
| because per https://gist.github.com/alx9r/f81cf64f50a016edda4e92968bdb9c3b | |
| * there is no way to ensure cleanup when an upstream command breaks, throws, | |
| continues, or throws a statement-terminating error, and | |
| * there is no way to determine from a mid-pipeline command whether an exception | |
| thrown downstream will cause the end of the invokation or will be swallowed by | |
| an upstream command. |
| [String]$ClusterName = "Compute01" | |
| [String]$LocalPath = "D:\Image\HPE-20180220.zip" | |
| [String]$DepotName = "HPE-20180220.zip" | |
| [String]$TempDatastoreName = "LOCAL*" | |
| $VMhosts = Get-Cluster -Name $ClusterName | Get-VMHost | Where-Object {$_.ConnectionState -eq "Maintenance"} | |
| foreach ($VMhost in $VMhosts) { | |
| #region: Upload Patch | |
| $Datastore = $VMhost | Get-Datastore -Name $TempDatastoreName |
| navigator.serviceWorker.getRegistrations().then(function (registrations) { | |
| if (!registrations.length) { | |
| console.log('No serviceWorker registrations found.') | |
| return | |
| } | |
| for(let registration of registrations) { | |
| registration.unregister().then(function (boolean) { | |
| console.log( | |
| (boolean ? 'Successfully unregistered' : 'Failed to unregister'), 'ServiceWorkerRegistration\n' + | |
| (registration.installing ? ' .installing.scriptURL = ' + registration.installing.scriptURL + '\n' : '') + |