Security Advisories / Bulletins / vendors Responses linked to Log4Shell (CVE-2021-44228)
| ip | tag_name | |
|---|---|---|
| 162.155.56.106 | Apache Log4j RCE Attempt | |
| 223.111.180.119 | Apache Log4j RCE Attempt | |
| 213.142.150.93 | Apache Log4j RCE Attempt | |
| 211.154.194.21 | Apache Log4j RCE Attempt | |
| 210.6.176.90 | Apache Log4j RCE Attempt | |
| 199.244.51.112 | Apache Log4j RCE Attempt | |
| 199.101.171.39 | Apache Log4j RCE Attempt | |
| 197.246.175.186 | Apache Log4j RCE Attempt | |
| 196.196.150.38 | Apache Log4j RCE Attempt |
| #!/bin/zsh | |
| :<<'ABOUT_THIS_SCRIPT' | |
| ----------------------------------------------------------------------- | |
| Written by:William Smith | |
| Partner Program Manager | |
| Jamf | |
| bill@talkingmoose.net | |
| https://gist.github.com/b6637160b65b751824943ede022daa17 |
Similar to my advice regarding OCSP Stapling for servers/server developers, based on questions I've received about "CT best practices," I wanted to write something similar for those writing server software. That is, this isn't targeted at server operators, but for those writing software like Apache, nginx, Caddy, etc.
At the most basic level, the deployment of Certificate Transparency to date has largely tried to focus the burden on CAs, rather than on server developers. If the CA is doing everything right,
| # tasks/main.yml | |
| - name: install certbot dependencies | |
| apt: name={{ item }} state=present | |
| with_items: | |
| - build-essential | |
| - libssl-dev | |
| - libffi-dev | |
| - python-dev | |
| - git |
On Twitter the other day, I was lamenting the state of OCSP stapling support on Linux servers, and got asked by several people to write-up what I think the requirements are for OCSP stapling support.
Support for keeping a long-lived (disk) cache of OCSP responses.
This should be fairly simple. Any restarting of the service shouldn't blow away previous responses that were obtained. This doesn't need to be disk, just stable - and disk is an easy stable storage for most server
| #!/bin/bash | |
| # Bash script for setting or clearing touch requirements for | |
| # cryptographic operations the OpenPGP application on a YubiKey 4. | |
| # | |
| # Author: Alessio Di Mauro <alessio@yubico.com> | |
| GCA=$(which gpg-connect-agent) | |
| DO=0 | |
| UIF=0 |
| language: objective-c | |
| before_script: | |
| - chmod +x scripts/travis/add-key.sh | |
| - chmod +x scripts/travis/remove-key.sh | |
| - chmod +x scripts/travis/testflight.sh | |
| - ./scripts/travis/add-key.sh | |
| script: xctool -workspace [Workspace name].xcworkspace -scheme '[Scheme to use]' -configuration [Build configuration name] -sdk iphoneos7.1 CONFIGURATION_BUILD_DIR='~/build/' build | |
| after_success: | |
| - ./scripts/travis/testflight.sh | |
| after_script: |
| language: objective-c | |
| xcode_workspace: "<WorkspaceName.xcworkspace>" | |
| xcode_scheme: "<SchemaName>" | |
| script: xctool -workspace <WorkspaceName.xcworkspace> -scheme <SchemeName> -configuration Release build archive | |
| before_script: | |
| - ./scripts/travis/add-key.sh | |
| after_script: | |
| - ./scripts/travis/remove-key.sh | |
| after_success: | |
| - ./scripts/travis/testflight.sh |
