| // Add ChatGPT Menu | |
| const onOpen = () => { | |
| const ui = SpreadsheetApp.getUi(); | |
| ui.createMenu("ChatGPT") | |
| .addItem("💾 Save Responses as Text", "saveAsText") | |
| .addItem("ChatGPT API Sheet by Sarah Tamsin 💜", "openUrl") | |
| .addToUi(); | |
| }; |
Imagine that you cloned an open source project to contribute something. You implemented a bugfix through a series of atomic commits on a private branch. Just when you’re about to create a Pull Request to submit your changes, you discover in the contributor’s guide that you’re supposed to prefix each commit with the bug tracking number.
Rewriting the commit message of the last commit is easy:
git commit --amend
| ;;; Startup | |
| ;;; PACKAGE LIST | |
| (setq package-archives | |
| '(("melpa" . "https://melpa.org/packages/") | |
| ("elpa" . "https://elpa.gnu.org/packages/"))) | |
| ;;; BOOTSTRAP USE-PACKAGE | |
| (package-initialize) | |
| (setq use-package-always-ensure t) | |
| (unless (package-installed-p 'use-package) |
It happens that there are many standards for storing cryptography materials (key, certificate, ...) and it isn't always obvious to know which standard is used by just looking at file name extension or file content. There are bunch of questions on stackoverflow asking about how to convert from PEM to PKCS#8 or PKCS#12, while many tried to answer the questions, those answers may not help because the correct answer depends on the content inside the PEM file. That is, a PEM file can contain many different things, such as an X509 certificate, a PKCS#1 or PKCS#8 private key. The worst-case scenario is that someone just store a non-PEM content in "something.pem" file.
| public interface Debuggable { | |
| default String debug() { | |
| StringBuilder sb = new StringBuilder(this.getClass().getName()); | |
| sb.append(" [ "); | |
| Field[] fields = this.getClass().getDeclaredFields(); | |
| for(Field f: fields) { | |
| f.setAccessible(true); | |
| try { | |
| sb.append(f.getName() + " = " + f.get(this)); | |
| sb.append(", "); |
Security Advisories / Bulletins / vendors Responses linked to Log4Shell (CVE-2021-44228)
| ;;; Startup | |
| ;;; PACKAGE LIST | |
| (setq package-archives | |
| '(("melpa" . "https://melpa.org/packages/") | |
| ("elpa" . "https://elpa.gnu.org/packages/"))) | |
| ;;; BOOTSTRAP USE-PACKAGE | |
| (package-initialize) | |
| (setq use-package-always-ensure t) | |
| (unless (package-installed-p 'use-package) |
| ############################## | |
| ## Java | |
| ############################## | |
| .mtj.tmp/ | |
| *.class | |
| *.jar | |
| *.war | |
| *.ear | |
| *.nar | |
| hs_err_pid* |
This is a small tool using Tinyscript and pypdf or pikepdf to bruteforce the password of a PDF given an alphabet (defaults to printables) and a length (default is 8).
$ pip install pypdf tinyscript
$ tsm pdf-password-bruteforcer
| package main | |
| import ( | |
| "bytes" | |
| "crypto/tls" | |
| "encoding/xml" | |
| "fmt" | |
| "io/ioutil" | |
| "net/http" | |
| "strings" |
