paul-snively

import { Stream } from 'xstream';
import { run } from "@cycle/run";
import { ReactElement } from 'react';
import { h, ReactSource } from "@cycle/react";
import { makeDOMDriver, p } from "@cycle/react-dom";
import { PrimaryButton, IStackTokens, Stack } from '@fluentui/react';

export type Sources = {
  readonly react: ReactSource;
};

paul-snively

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns='http://www.w3.org/2000/svg'
    xmlns:svg='http://www.w3.org/2000/svg'
    exclude-result-prefixes="xs"
    version="1.1">
  <xsl:template match="svg:svg[@viewBox]">
    <xsl:copy>
      <xsl:copy-of select="@*[name(.)!='height' and name(.) != 'width']" />

paul-snively

Notes on IAM (Identity and Access Management) and Zero-Trust Architecture

Overall ideas

• Pervasive X.509 authentication with SPIFFE standards using the SPIRE reference implementation
• Frequent (e.g. hourly) rotation of dynamically-generated certificates for mTLS between nodes/workloads in the usual SPIFFE way
• In Kubernetes:
  • cert-manager with csi-driver-spiffe
  • k8s Workload Registrar — deprecated in favor of the spire-controller-manager
• Most workloads will use csi-driver-spiffe as described here to provide the SPIFFE_ENDPOINT_SOCKET evironment variable and the [Java SPIFFE Provider](https://github.com/spiffe/java-spiffe/blob/main/java-spiffe-provider/R