| #!/bin/bash | |
| set -euo pipefail | |
| CMD=$0 | |
| function usage { | |
| cat <<EOU | |
| Usage: |
[ Update 2025-03-24: Commenting is disabled permanently. Previous comments are archived at web.archive.org. ]
Most of the terminal emulators auto-detect when a URL appears onscreen and allow to conveniently open them (e.g. via Ctrl+click or Cmd+click, or the right click menu).
It was, however, not possible until now for arbitrary text to point to URLs, just as on webpages.
Le planning des confs au format .ics pour l'ajouter à votre 📆 agenda est ici.
Vidéos de jeux (par date) | Vidéos de jeux (par ordre alphabétique) | Liens utiles | Suggestions & remarques
Planning | Vidéos par ordre alphabétique | Liens utiles | Suggestions & remarques
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
| This builds off the excellent work of @lmarkus. | |
| The scripts below can be used in conjunction with the Neutral Face Emoji Tools Google Chrome extension to (bulk!) | |
| export emojis from one Slack team and import into another team: | |
| https://chrome.google.com/webstore/detail/neutral-face-emoji-tools/anchoacphlfbdomdlomnbbfhcmcdmjej | |
| Original work here: https://gist.github.com/lmarkus/8722f56baf8c47045621 | |
| Steps: | |
| 1) Run js in dev tools |
| # I used this shell.nix to build LineageOS 13.0 for my maguro (Samsung Galaxy Nexus GSM) phone | |
| # The build instructions for normal Linuxes are here: https://wiki.lineageos.org/devices/maguro/build | |
| # For NixOS, follow those instructions but skip anything related to installing packages | |
| # Detailed instructions: | |
| # cd into an empty directory of your choice | |
| # copy this file there | |
| # in nix-shell: | |
| # $ repo init -u https://github.com/LineageOS/android.git -b cm-13.0 | |
| # $ repo sync | |
| # $ source build/envsetup.sh |
| WAYLAND_PROTOCOLS=/usr/share/wayland-protocols | |
| # wayland-scanner is a tool which generates C headers and rigging for Wayland | |
| # protocols, which are specified in XML. wlroots requires you to rig these up | |
| # to your build system yourself and provide them in the include path. | |
| xdg-shell-protocol.h: | |
| wayland-scanner server-header \ | |
| $(WAYLAND_PROTOCOLS)/stable/xdg-shell/xdg-shell.xml $@ | |
| xdg-shell-protocol.c: xdg-shell-protocol.h |
Hey everyone - this is not just a one off thing, there are likely to be many other modules in your dependency trees that are now a burden to their authors. I didn't create this code for altruistic motivations, I created it for fun. I was learning, and learning is fun. I gave it away because it was easy to do so, and because sharing helps learning too. I think most of the small modules on npm were created for reasons like this. However, that was a long time ago. I've since moved on from this module and moved on from that thing too and in the process of moving on from that as well. I've written way better modules than this, the internet just hasn't fully caught up.
@broros
otherwise why would he hand over a popular package to a stranger?
If it's not fun anymore, you get literally nothing from maintaining a popular package.
One time, I was working as a dishwasher in a restu
