I see that azurerm provider has azurerm_monitor_metric_alert but does not appear to support azure quota alerts. Various AI think I can use azurerm_monitor_metric_alert with a scope like `/subscriptions/${data.azurerm_subscription.current.subscription_id}/providers/Microsoft.Compute/locations/${location}/providers/Microsoft.Quota/quotas/standardDPLDSv5Family"
but this doesn't seem to be the case. It seems to be impossible to manage subscription quota alerts via terraform. Is this right?
According to Ubuntu's CVE-2022-0778 this release should address the CVE. However, when I look at the OpenSSL version I can't really tell that it is 1.1.1n. I do see that it was built on Mar 9 prior to:
So, how would I know that this is truly 1.1.1n?
OpenSSL 1.1.1 11 Sep 2018
built on: Wed Mar 9 12:13:40 2022 UTC
platform: debian-amd64
options: bn(64,64) rc4(16x,int) des(int) blowfish(ptr)
compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,
--noexecstack -g -O2 -fdebug-prefix-map=/build/openssl-vxXVMf/openssl-1.1.1=.
-fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_USE_NODELETE
-DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2
-DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM
-DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM
-DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM
-DECP_NISTZ256_ASM -DX25519_ASM -DPADLOCK_ASM -DPOLY1305_ASM
-DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2
OPENSSLDIR: "/usr/lib/ssl"
ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1"
Seeding source: os-specific
Ubuntu Repo: https://git.launchpad.net/ubuntu/+source/openssl
Tags:
* 3b83ed56dea2b735e31731fd042b52ff869f9a97 -
(tag: import/1.1.1n-1, origin/debian/sid) 1.1.1n-1
(patches unapplied) (c: Wed, 16 Mar 2022 04:33:58 +0000)
(a: Tue, 15 Mar 2022 19:46:18 +0100) <Sebastian Andrzej Siewior>%
applied/1.1.1n-1
* d4d5eeef3576b16013c48abc435c5da889cedf1b - (tag: applied/1.1.1n-1,
origin/applied/debian/sid) 1.1.1n-1 (patches applied)
(c: Wed, 16 Mar 2022 04:33:58 +0000)
(a: Tue, 15 Mar 2022 19:46:18 +0100) <Sebastian Andrzej Si
I've got two windows systems tied to the AWS CloudHSM v2 (the cavium HSM). On one, I generated the CSR, and accepts/added the cert purchased with that CSR. I can sign and the private key is pulled properly from the HSM via the Key Container.
The other signing is my production signing system and it is working properly with the existing cert but when I try to add the new cert, no Key Container is setup. I'm used to needing to run the repair process but in this case I have no ID to provide the file.
"\Program Files\Amazon\CloudHSM\tools\set_cloudhsm_credentials.exe" --user REDACTED --password "..."certutil -addstore my my-new-cert.crtcertutil -store my > cert_store_details.txt Serial Number: REDACTED
Issuer: CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1, O=DigiCert, Inc., C=US
NotBefore: 1/25/2022 12:00 AM
NotAfter: 1/25/2023 11:59 PM
Subject: CN=REDACTED, C=US, SERIALNUMBER=REDACTED, OID.1.3.6.1.4.1.311.60.2.1.2=Delaware, OID.1.3.6.1.4.1.311.60.2.1.3=US, OID.2.5.4.15=Private Organization
Non-root Certificate
Cert Hash(sha1): REDACTED
No key provider information
Cannot find the certificate and private key for decryption.
Normally, I'd create a repair.txt like so with Key Container id between the = and & on the Container however, I don't got one of those so I'm out of luck
[Properties]
11 = "" ; Add friendly name property
2 = "{text}" ; Add Key Provider Information property
_continue_="Container=&"
_continue_="Provider=Cavium Key Storage Provider&"
_continue_="Flags=0&"
_continue_="KeySpec=2"
If I just run a repair certutil -repairstore my "REDACTED" then I get asked for a smart card. Oh and this machine is a Windows Core 2016 (so there's NO UI or limited UI).
I see that elrepo only provides nosrc and not src packages for their kernel-lt but I don't understand their rational and nor have I been able to find it by searching.
Does anyone know the reason and where to look for documentation about it?
How can I find the updated necessary to enable SHA-2 support on Windows 2012 RTM.
Going to 2012R2 is a larger jump than we'd like to take at this moment, so we are looking for the SHA-2 enabling update as a standalone.
When trying to build a centos rootfs tarball the hard way (see centos docs) my livemedia-creator run hangs with:
livemedia-creator --make-tar --iso=/root/boot8.iso \
--ks=/root/centos-8.ks --image-name=centos8-docker.tar.xz
Domain installation still in progress. You can reconnect to
the console to complete the installation process.
So, I can't make a rootfs tarball which I'd use to make a base docker image. I let it run for a few hours, nothing of use in the logs and I gather something interactive is going on but I can't reach the console
Is there a way to get ansible-playbook execution to provide the entire winrm error? I am running with -vvvv and still see a cut off like below:
WINRM RESULT u'<Response code 1, out
"{"changed":false,"ms", err "powershell : Excepti">'
Adding more '-v' doesn't seem to do much to improve clarity of error.
Environment
Has anyone ever seen retries work on an ansible win_chocolatey task?
The follow seems to fail on the first attempt with no retries and I'm getting timeouts at the ansible level while choco attempts to install a package.
- name: Install Chocolatey
win_chocolatey:
name: a_package
env: choco
retries: 3
Have you successfully used retries with win_chocolatey tasks?
Possible Solution Using Henrik's suggestion and a block, I have retries plus a rescue/catch operation to fetch the choco log in case of errors after retries
- name: install applications
block:
- win_chocolatey:
name: "{{ item }}"
source: "{{ choco_artifactory_source }}"
register: result
until: result.rc == 0
retries: 3
with_items:
- wget
- curl
rescue:
- fetch:
src: "{{ choco_log }}"
dest: "{{ agent_log_dir }}"
flat: yes
what's the recommended approach for setting up remote rpm repositories to proxy Amazon Linux?
The yum repo files on Amazon linux show a mirror list and then base URLs with UIDs. I don't know if I can count on the Repo-baseurl or if there's a way to feed the mirror list into artifactory.
Do, I need to replicate the entire mirror list and then pull them together in a virtual repository?
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
Repo-id : amzn2-core/2/x86_64
Repo-name : Amazon Linux 2 core repository
Repo-revision: 1532545700
Repo-updated : Wed Jul 25 19:08:20 2018
Repo-pkgs : 9,137
Repo-size : 8.1 G
Repo-mirrors : http://amazonlinux.us-east-1.amazonaws.com/2/core/latest/x86_64/mirror.list
Repo-baseurl : http://amazonlinux.us-east-1.amazonaws.com/2/core/2.0/x86_64/ecb7f3179dc53ca05863f9df12535c3a24d03bb87b8f3816aaa632d02ff53f2c/
Repo-expire : 300 second(s) (last: Tue Jul 31 11:46:36 2018)
Filter : read-only:present
Repo-filename: /etc/yum.repos.d/amzn2-core.repo
After creating a remote rpm repo called rpm-amzn-remote linked to http://amazonlinux.us-east-1.amazonaws.com/2/core/2.0/x86_64/ecb7f3179dc53ca05863f9df12535c3a24d03bb87b8f3816aaa632d02ff53f2c/ I see the following relative paths when I run repoquery
repoquery --tempcache \
--repofrompath=repo,http://artifactory/rpm-amzn-remote/ --repoid=repo\
--qf="%{version}-%{release}.%{arch} %{location}" --show-duplicates kernel-devel
# result
4.9.62-10.57.amzn2.x86_64 \
http://artifactory/../../../../blobstore/18381632cff65dcf8dd4b7fe67bb45f58dc85720816c78d03ffa6677cab4b9e1/kernel-devel-4.9.62-10.57.amzn2.x86_64.rpm
and of course, the link cannot be downloaded
Does anyone know where I can find the i386 centos 4.7 repos files that would normally sit in /etc/yum.repos.d. Alas, it looks like someone copied the 5.5 edition over to a 4.7 system.
I can setup a new VM, install 4.7 and extract the files from that system (but I was hoping for a faster approach.
Please let me know if you know where these files live on the net. I'm off to RPMfind to see what I can locate.
Thanks
Peter