Set Launch Option:
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json %command%
""" | |
from: | |
1 OVERVIEW AND GENERAL CONCEPTS - 0:00 | |
2 ENTRIES - 12:12 | |
STANDING OPPONENT - 13:33 | |
KNEELING OPPONENT - 20:31 | |
BRINGING IT TOGETHER - 28:12 | |
to: | |
CHAPTER01=00:00:00.000 |
Set Launch Option:
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json %command%
Start RabbitMQ with Docker:
$ docker run --rm -d -p 5672:5672 rabbitmq:3
Then, in 3 different shells, run:
$ celery -A receiver worker -Q in -n receiver -l INFO
Running Steam on ubuntu 20.04 64-bit | |
STEAM_RUNTIME is enabled automatically | |
Pins up-to-date! | |
Steam client's requirements are satisfied | |
WARNING: Using default/fallback debugger launch | |
/home/adrian/.local/share/Steam/ubuntu12_32/steam | |
[2021-05-01 16:43:52] Startup - updater built Apr 12 2021 18:51:36 | |
Installing breakpad exception handler for appid(steam)/version(1618256785) | |
Looks like steam didn't shutdown cleanly, scheduling immediate update check | |
[2021-05-01 16:43:52] Loading cached metrics from disk (/home/adrian/.local/share/Steam/package/steam_client_metrics.bin) |
# Enable Powerlevel10k instant prompt. Should stay close to the top of ~/.zshrc. | |
# Initialization code that may require console input (password prompts, [y/n] | |
# confirmations, etc.) must go above this block; everything else may go below. | |
if [[ -r "${XDG_CACHE_HOME:-$HOME/.cache}/p10k-instant-prompt-${(%):-%n}.zsh" ]]; then | |
source "${XDG_CACHE_HOME:-$HOME/.cache}/p10k-instant-prompt-${(%):-%n}.zsh" | |
fi | |
# If you come from bash you might have to change your $PATH. | |
# export PATH=$HOME/bin:/usr/local/bin:$PATH |
.gitattributes text eol=lf | |
.gitignore text eol=lf | |
*.build text eol=lf | |
*.c text eol=lf | |
*.cmake text eol=lf | |
*.cpp text eol=lf | |
*.csv text eol=lf | |
*.f text eol=lf | |
*.f90 text eol=lf | |
*.for text eol=lf |
[user] | |
email = td.anh0812@gmail.com | |
name = anhtd | |
[alias] | |
b = branch | |
co = checkout | |
d = diff | |
lg = log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit | |
p = pull | |
pu = push |
Kong, Traefik, Caddy, Linkerd, Fabio, Vulcand, and Netflix Zuul seem to be the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to separate the popularity from other things.
This is just a picture of this link from Feb
GitHub repositories can disclose all sorts of potentially valuable information for bug bounty hunters. The targets do not always have to be open source for there to be issues. Organization members and their open source projects can sometimes accidentally expose information that could be used against the target company. in this article I will give you a brief overview that should help you get started targeting GitHub repositories for vulnerabilities and for general recon.
You can just do your research on github.com, but I would suggest cloning all the target's repositories so that you can run your tests locally. I would highly recommend @mazen160's GitHubCloner. Just run the script and you should be good to go.
$ python githubcloner.py --org organization -o /tmp/output