Skip to content

Instantly share code, notes, and snippets.

@ralfbergs
ralfbergs / gist:d69197cf15ab431f3ca229a1800ee1bd
Created October 28, 2016 22:04
"elasticache" return value
"mgmt_ec_redis": {
"changed": true,
"elasticache": {
"data": {
"AutoMinorVersionUpgrade": true,
"CacheClusterCreateTime": 1477691226.244,
"CacheClusterId": "ciot-ec-mgmt-db-red",
"CacheClusterStatus": "available",
"CacheNodeType": "cache.m4.large",
"CacheNodes": [
---
- hosts: localhost
vars:
env: "{{ env_devmgmt_name }}"
roles:
- aws/create
---
- hosts: localhost
vars:
env: "{{ env_devmgmt_name }}"
roles:
- aws/create
@ralfbergs
ralfbergs / 1-download-repos.log
Last active August 23, 2018 22:02
Huawei Grace: Build TWRP
rabe@inspiron3847:~/devel/android$ mkdir twrp-8.1
rabe@inspiron3847:~/devel/android$ cd twrp-8.1
rabe@inspiron3847:~/devel/android/twrp-8.1$ repo init --depth=1 -u git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git -b twrp-8.1
Get https://gerrit.googlesource.com/git-repo/clone.bundle
Get https://gerrit.googlesource.com/git-repo
Get git://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni.git
remote: Counting objects: 2240, done.
remote: Total 2240 (delta 0), reused 0 (delta 0), pack-reused 2240
Receiving objects: 100% (2240/2240), 713.42 KiB | 1.41 MiB/s, done.
Resolving deltas: 100% (953/953), done.
@ralfbergs
ralfbergs / gist:f42d49fbc5ebb46b95fe3e24bf67b516
Created January 28, 2024 18:36
Professional Cloud DevOps Engineer Certification Learning Path > Cloud Operations and Service Mesh with Anthos > Securing Network Traffic with Anthos Service Mesh: statements correcting the video
There is several SERIOUS errors in the short video that show a severe lack of understanding of how TLS works (I'm sorry for the harsh words).
Let me elaborate:
The lecturer says: "This process is called 'asymmetric encryption' since we're only encrypting the sent message."
This is absolutely wrong. A TLS channel is always "fully encrypted," i.e. encryption happens in both directions. "Asymmetric encryption" is called "asymmetric," because encryption and decryption happens with different keys (public key for encryption, and private key for decryption,) and not with the same key (THIS is why it's called "symmetric encryption", because the encryption and decryption happens using the same key.)
Moreover, the lecturer says: "However, in a microservice architecture, we are going to have services communicating both ways, so traffic must also be encrypted from Service B to Service A. Therefore, when Service A establishes the connection with Service B, it will share a symmetric key, which both services can use to