See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
| Filter | Description | Example |
|---|---|---|
| allintext | Searches for occurrences of all the keywords given. | allintext:"keyword" |
| intext | Searches for the occurrences of keywords all at once or one at a time. | intext:"keyword" |
| inurl | Searches for a URL matching one of the keywords. | inurl:"keyword" |
| allinurl | Searches for a URL matching all the keywords in the query. | allinurl:"keyword" |
| intitle | Searches for occurrences of keywords in title all or one. | intitle:"keyword" |
This is a cheat sheet for how to perform various actions to ZSH, which can be tricky to find on the web as the syntax is not intuitive and it is generally not very well-documented.
| Description | Syntax |
|---|---|
| Get the length of a string | ${#VARNAME} |
| Get a single character | ${VARNAME[index]} |
| # Created by @PhilippIRL | |
| # This script patches Spotify's offline.bnk file (this file caches the remote config) to trick Spotify into thinking that your account is enabled for dev tools. | |
| # Spotify will automatically revert this local change after some time when it next fetches the remote config. | |
| # Of course you will have to completely close Spotify before running this script. | |
| import os, sys, platform | |
| systemPlatform = platform.system() | |
| if systemPlatform == 'Windows': |
| #!/usr/bin/env bash | |
| # Temporarily enable developer mode for the Spotify desktop client on Linux and macOS. | |
| showHelp () { | |
| echo -e \ | |
| "Usage: ./tmpdevmodify.sh [option]\n | |
| Options: | |
| -c, --clearcache Clear Spotify app cache | |
| -d, --debug Add Debug Tools to user dropdown menu |
| // Copyright (C) 2022 Evan McBroom | |
| // | |
| // Permission is hereby granted, free of charge, to any person obtaining a copy | |
| // of this software and associated documentation files (the "Software"), to deal | |
| // in the Software without restriction, including without limitation the rights | |
| // to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| // copies of the Software, and to permit persons to whom the Software is | |
| // furnished to do so, subject to the following conditions: | |
| // | |
| // The above copyright notice and this permission notice shall be included in |
Thank you to SpecterOps for supporting this research and to Duane and Matt for proofreading and editing! Crossposted on the SpecterOps Blog.
TLDR: You may use this header file for reliable compile time string encryption without needing any additional dependencies.
Programmers of DRM software, security products, or other sensitive code bases are commonly required to minimize the amount of human readable strings in binary output files. The goal of the minimization is to hinder others from reverse engineering their proprietary technology.
Common approaches that are taken to meet this requirement often add an additional maintenance burden to the developer and are prone to error. These approaches will be presented along with t
| # Syntactic Grammar for ECMAScript | |
| ecma-script-module ::= { top-level | ignorable } | |
| top-level ::= statement | |
| | function-declaration | |
| | class-declaration | |
| function-declaration ::= [ "async" ] "function" identifier function-params-postfix compound-statement |
| // ==UserScript== | |
| // @name DarkReader | |
| // @match *://*/* | |
| // @grant none | |
| // @run-at document-start | |
| // ==/UserScript== | |
| // MIT License | |
| // Copyright (c) 2019 Alexander Shutau |