cosign
speedtest
cosign | speedtest | |
---|---|---|
30 | 125 | |
4,068 | 11,124 | |
1.7% | 1.0% | |
9.6 | 7.2 | |
9 days ago | 14 days ago | |
Go | PHP | |
Apache License 2.0 | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cosign
-
Securing CI/CD Images with Cosign and OPA
Cosign: In this context, Cosign from the Sigstore project offers a compelling solution. Its simplicity, registry compatibility, and effective link between images and their signatures provide a user-friendly and versatile approach. The integration of Fulcio for certificate management and Rekor for secure logging enhances Cosign's appeal, making it particularly suitable for modern development environments that prioritize security and agility.
-
An Overview of Kubernetes Security Projects at KubeCon Europe 2023
sigstore is another suite of tools that focuses on attestation and provenance. Within the suite are two tools I heard mentioned a few times at KubeCon: Cosign and Rekor.
-
Spin 1.0 — The Developer Tool for Serverless WebAssembly
Since we can distribute Spin applications using popular registry services, we can also take advantage of ecosystem tools such as Sigstore and Cosign, which address the software supply chain issue by signing and verifying applications using Sigstore's new keyless signatures (using OIDC identity tokens from providers such as GitHub).
-
Iron Bank: Secure Registries, Secure Containers
Use distroless images (which contain only application and its runtime dependencies, and don't include package managers/shells or any other programs you would expect to find in a standard Linux distribution). All distroless images are signed by cosign.
-
Getting hands on with Sigstore Cosign on AWS
$ COSIGN_EXPERIMENTAL=1 cosign verify-blob --cert https://github.com/sigstore/cosign/releases/download/v1.13.1/cosign-linux-amd64-keyless.pem --signature https://github.com/sigstore/cosign/releases/download/v1.13.1/cosign-linux-amd64-keyless.sig https://github.com/sigstore/cosign/releases/download/v1.13.1/cosign-linux-amd64
-
How much are you 'trusting' a docker image from hub.docker.com?
Another thing to look for is, whether the image is signed using something like cosign (https://github.com/sigstore/cosign). This lets the publisher digitally sign the image, so you at least know that what's on the registry is what they intended to put there. Handy to avoid the risks of attackers squatting similar names and catching typos.
-
What security controls to prevent someone from pushing arbitrary code into production?
i’m late but surprised no one has mentioned cosign
-
Docker build fails on GitHub Action after net7 update
name: Docker # This workflow uses actions that are not certified by GitHub. # They are provided by a third-party and are governed by # separate terms of service, privacy policy, and support # documentation. on: push: branches: [ "main" ] # Publish semver tags as releases. tags: [ 'v*.*.*' ] pull_request: branches: [ "main" ] paths: - src/MamisSolidarias.WebAPI.Campaigns/Dockerfile - .github/workflows/docker-publish.yml workflow_dispatch: env: # Use docker.io for Docker Hub if empty REGISTRY: ghcr.io IMAGE_NAME: mamis-solidarias/campaigns jobs: build: runs-on: ubuntu-latest permissions: contents: read packages: write # This is used to complete the identity challenge # with sigstore/fulcio when running outside of PRs. id-token: write steps: - name: Checkout repository uses: actions/checkout@v3 # Install the cosign tool except on PR # https://github.com/sigstore/cosign-installer - name: Install cosign if: github.event_name != 'pull_request' uses: sigstore/cosign-installer@main with: cosign-release: 'v1.13.1' - name: Set up QEMU uses: docker/setup-qemu-action@v2 with: platforms: 'arm64' # Workaround: https://github.com/docker/build-push-action/issues/461 - name: Setup Docker buildx uses: docker/setup-buildx-action@v2 # Login against a Docker registry except on PR # https://github.com/docker/login-action - name: Log into registry ${{ env.REGISTRY }} if: github.event_name != 'pull_request' uses: docker/login-action@v2 with: registry: ${{ env.REGISTRY }} username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} # Extract metadata (tags, labels) for Docker # https://github.com/docker/metadata-action - name: Extract Docker metadata id: meta uses: docker/metadata-action@v4 with: images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} tags: | type=schedule type=ref,event=branch type=ref,event=pr type=semver,pattern={{version}} type=semver,pattern={{major}}.{{minor}} type=semver,pattern={{major}} type=sha # Build and push Docker image with Buildx (don't push on PR) # https://github.com/docker/build-push-action - name: Build and push Docker image id: build-and-push uses: docker/build-push-action@v3 with: context: . platforms: linux/amd64, linux/arm64 file: src/MamisSolidarias.WebAPI.Campaigns/Dockerfile push: ${{ github.event_name != 'pull_request' }} tags: ${{ steps.meta.outputs.tags }} labels: ${{ steps.meta.outputs.labels }} # Sign the resulting Docker image digest except on PRs. # This will only write to the public Rekor transparency log when the Docker # repository is public to avoid leaking data. If you would like to publish # transparency data even for private images, pass --force to cosign below. # https://github.com/sigstore/cosign - name: Sign the published Docker image if: ${{ github.event_name != 'pull_request' }} env: COSIGN_EXPERIMENTAL: "true" # This step uses the identity token to provision an ephemeral certificate # against the sigstore community Fulcio instance. run: echo "${{ steps.meta.outputs.tags }}" | xargs -I {} cosign sign {}@${{ steps.build-and-push.outputs.digest }}
-
How to tag base image so images built from it can be tracked
After inspecting the layers i think you should start thinking about signing your images: https://github.com/sigstore/cosign/
-
Understanding Kubernetes Limits and Requests
cosign
speedtest
-
Slower speeds after installing OpenWRT
I recently installed OpenWRT on a TP-Link TL-WDR4300, and put the router of my ISP in bridge mode. Now I noticed that the wireless speeds are significantly slower (40mbps vs 3mbps via librespeed.org), after using OpenWRT.
-
List of your reverse proxied services
LebreSpeed
-
Ask HN: Is Comcast ripping me off and how can I prove it?
Try hosting a DIY speed test on a cloud server (like Google colab or the free oracle instances or whatever):
https://github.com/librespeed/speedtest
- Do you use any specific tools to verify connection health of remote workers?
-
How to host HTTP without SSL enryption on Cloudflare domain?
here's the top two results if you search for "open speed test nginx reverse proxy": https://github.com/librespeed/speedtest/wiki/Reverse-proxy-with-Nginx https://github.com/henrywhitaker3/Speedtest-Tracker/issues/924
-
5G on the 4G plan
Or https://librespeed.org/
-
Gig1 none of my devices are getting close to max speed
Fast.com is giving me ~ 250Mbps https://librespeed.org is giving me ~ 112Mbps the one constant between all the tests seems to be the 52Mb upload
-
SSLVPN - Fluctuating bandwith
It should be DIA. They provide the internet connection to the company since 2 decades and it's a very small ISP, so it's very vague in terms of contract. Iperf was giving me very terrible results with TCP, UDP was giving me a couple of Gbit/s throughput, definitely a wrong result. We are using this self hosted speedtest. All my results above are based on this software: https://github.com/librespeed/speedtest
-
Speedtests
Put a copy of Librespeed on a web server that's accessible through the VPN and told them to use that. For (our) convenience, it's logged into a database that's correlated with the VPN login/logout times so the users don't even need to log in to use it, but we still know whose test result it is.
- 40 Containers & Counting...
What are some alternatives?
notation - A CLI tool to sign and verify artifacts
awesome-selfhosted - A list of Free Software network services and web applications which can be hosted on your own servers
in-toto-golang - A Go implementation of in-toto. in-toto is a framework to protect software supply chain integrity.
speedtest-cli - Command line interface for testing internet bandwidth using speedtest.net
connaisseur - An admission controller that integrates Container Image Signature Verification into a Kubernetes cluster
reverse-proxy-confs - These confs are pulled into our SWAG image: https://github.com/linuxserver/docker-swag
spire - The SPIFFE Runtime Environment
aria2 - aria2 is a lightweight multi-protocol & multi-source, cross platform download utility operated in command-line. It supports HTTP/HTTPS, FTP, SFTP, BitTorrent and Metalink.
spiffe-vault - Integrates Spiffe and Vault to have secretless authentication
Organizr - HTPC/Homelab Services Organizer - Written in PHP
rekor - Software Supply Chain Transparency Log
MagicMirror - MagicMirror² is an open source modular smart mirror platform. With a growing list of installable modules, the MagicMirror² allows you to convert your hallway or bathroom mirror into your personal assistant.