Security

Cybersecurity (security) includes controlling physical access to hardware as well as protection from attacks that come via network access, data injection, and code injection.

It seems Caddy does not support wildcards/ expression matching in the reverse proxy's header_up.

For example this does not remove any headers:

header_up -X-SHIBBOLETH-*

This works as expected, but is limited in its use:

header_up -X-SHIBBOLETH-LOGIN

It'd be great if Caddy would support wildcards/ expression matching in the reverse proxy's header_up/ header_down.

OS/Environment

None yet, but I'm working on OS X v10.11.6 'El Capitan' client-side. (See 'The way of deployment (cloud or local)' below for details on considered server infrastructure.)

Ansible version

None yet, as I haven't yet gotten that far into setting up Algo.

Version of components from `requirements.txt`

Not applicable (see above.)

Summary of the pro

Environment

Sat Dec 11 06:20:24 AM UTC 2021
rasm2 5.5.2 27280 @ linux-x86-64 git.5.5.2
commit: e65e385e5308293c23611e16e531df8c52a9ff18 build: 2021-12-11__06:31:42
Linux x86_64

Description

The opcodes jecxz and jrcxz cannot assemble.

Test

$ rasm2 -a x86 -b 64 'jecxz 0x1'
Cannot assemble 'jecxz 0x1' at line 3
invalid
$ rasm2 -a x86 -b 64 'jrcxz 0x1

Sorry for not following the template. It's a straightforward question.

By enabling "WordPress-specific rules", the following codes will be added to the wordpress.conf:

# WordPress: deny general stuff
location ~* ^/(?:xmlrpc\.php|wp-links-opml\.php|wp-config\.php|wp-config-sample\.php|readme\.html|license\.txt)$ {
    deny all;
}

However, this disables xmlrpc feature, which disa

Asking about this since the NSA recently published guidance advising the public and private sectors to transition to cryptographic algorithms that are no less than sha384 & ec384 (elliptic curves).

While Edwards' Curves are different, its worth noting that prior to this update sha256 & secp256k1 were both on the list of acceptable cryptographic algorithms. My deduction was that 128-bit securit

You might have a compose file that doesn't reference the exact version of the container image you want to minified (e.g., the target service might reference the latest tag and you want to minify v1.2.3 for your target image).

The --target-compose-svc-image command parameter (for build and profile commands) should provide a way to use the desired image version without having to rewrite

Dec	JAN	Feb
	07
2021	2022	2023

Security

Here are 15,115 public repositories matching this topic...

trimstray / the-book-of-secret-knowledge

Hack-with-Github / Awesome-Hacking

x64dbg / x64dbg

caddyserver / caddy

swisskyrepo / PayloadsAllTheThings

mitmproxy / mitmproxy

Developer-Y / cs-video-courses

trailofbits / algo

OS/Environment

Ansible version

Version of components from requirements.txt

Summary of the pro

FallibleInc / security-guide-for-developers

StevenBlack / hosts

OWASP / CheatSheetSeries

drduh / macOS-Security-and-Privacy-Guide

osquery / osquery

hwdsl2 / setup-ipsec-vpn

shieldfy / API-Security-Checklist

matomo-org / matomo

radareorg / radare2

Environment

Description

Test

digitalocean / nginxconfig.io

OpenZeppelin / openzeppelin-contracts

trimstray / nginx-admins-handbook

Hacker0x01 / hacker101

imthenachoman / How-To-Secure-A-Linux-Server

ory / hydra

google / tink

docker-slim / docker-slim

keepassxreboot / keepassxc

authelia / authelia

bettercap / bettercap

gravitational / teleport

keeweb / keeweb

Community Powered Security

Security apps

Version of components from `requirements.txt`