Skip to content

Instantly share code, notes, and snippets.

Avatar
📖
Building @honkit

azu azu

📖
Building @honkit
View GitHub Profile
@azu
azu / Google: remove hidden text.user.js
Last active Jul 29, 2020
検索結果でテキストをコピーすると入る"ウェブ検索結果" and "検索結果"を削除する
View Google: remove hidden text.user.js
// ==UserScript==
// @name Google: remove hidden text
// @description 検索結果でテキストをコピーすると入る"ウェブ検索結果"と"検索結果"を削除する
// @namespace info.efcl.google
// @match https://www.google.*/search*
// @grant none
// @version 1.0
// @author azu
// ==/UserScript==
@azu
azu / delete-book.js
Last active May 30, 2020
Inkdrop: delete by book ids
View delete-book.js
const deleted = [
"book:xxx"
]
const db = inkdrop.main.dataStore.getLocalDB()
const notes = db.notes;
for (const id of deleted) {
const results = await notes.findInBook(id, { limit: 1 });
console.log(`id ${id}, size: ${results.docs.length}`)
for (const doc of results.docs) {
const deletedId = doc._id;
@azu
azu / git-2.26.1-README.md
Last active May 1, 2020
Gitの認証情報を奪い取れるGit 2.26.0以下にある脆弱性について
View git-2.26.1-README.md

Git 2.26.0以下にある脆弱性

Git 2.26.0以下*1には、細工したリポジトリをgit cloneしたときに、 そのユーザーのCredential(たとえばGitHub.comをcloneするときに使う認証情報)を奪い取れる脆弱性があります。

📝 取得できる認証情報は credential.helper の設定に依存する

既にPoC(検証するためのコード)もあり、結構簡単なので是非Gitを2.26.1以上にアップデートしましょう。 git submoduleを使うと見た目ではわかりにくい攻撃もできるので、「気をつける」では回避は難しいです。

@azu
azu / .phoenix.js
Last active Apr 19, 2020
SplitView on ~/.phoenix.js
View .phoenix.js
const appNames = {
left: "Tweeten",
right: "MyDiscord"
}
const windowRatio = {
left: 0.75,
right: 0.25
};
/**
* SplitView
@azu
azu / browser-resources.md
Last active Jun 25, 2020
ブラウザ/セキュリティ/プライバシー周りの一次情報に近い二次情報の情報源をまとめたもの
View browser-resources.md

一次情報に近い二次情報の情報源をまとめたもの。

ここでの一次情報はコミットとかコードのこと。

Browser

@azu
azu / readme.md
Created Mar 7, 2020
Support custom "getNextVersion" in configuration proposal for ship.js
View readme.md
@azu
azu / release-flow.md
Last active Mar 7, 2020
Release Flow
View release-flow.md

My workflow is 4 steps:

  1. Developing (Person)
  2. Create Release Pull Request (CI or Person)
  3. Review Release Pull Request (Person)
  4. Publish (CI)

Developing

  1. Develop it
View schema.tss
type SecretLintConfigDescriptorRule = {
id: string,
options?: {},
disabled?: boolean,
};
type SecretLintConfigDescriptorRulePreset = {
id: string,
options?: {},
disabled?: boolean,
};
@azu
azu / README.md
Last active Jul 15, 2020
GitHub Package Registry and Npm Registry for same scoped does not work @ 2020-01-10
View README.md

📝 I submit the same text to GitHub Support.


I want to use same scope for npm package and GitHub Package Registry.

For example, @org scope exist in npm and GitHub.

  • @org/foo-public package is public on npm registry
  • @org/bar-private package is private on GitHub Package Registry
@azu
azu / aws-lambda-node-8.10-is-eol.md
Last active Jan 9, 2020
Node.js 8.10 is EOL, please migrate your functions to a newer runtime version (copy from email)
View aws-lambda-node-8.10-is-eol.md

We are contacting you as we have identified that your AWS Account currently has one or more Lambda functions using Node.js 8.10, which will reach its EOL at the end of 2019.

What’s happening?

The Node community has decided to end support for Node.js 8.x on December 31, 2019 [1]. From this date forward, Node.js 8.x will stop receiving bug fixes, security updates, and/or performance improvements. To ensure that your new and existing functions run on a supported and secure runtime, language runtimes that have reached their EOL are deprecated in AWS [2].

You can’t perform that action at this time.