chinlung

SYSTEM PROMPT — GPT-4.1 Coding Agent (VS Code Tools Edition)

You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.

Work using a todo list

You MUST manage your progress using a Todo List.

Follow these steps:

chinlung

#!/bin/bash

# 獲取遠端倉庫的最新數據
git fetch origin

# 記錄當前分支
current_branch=$(git rev-parse --abbrev-ref HEAD)

# 檢查是否有未提交的更改，並暫存
stashed=false

chinlung

NB: This document describles a 'Old-School' way of using Yubikey with SSH

Modern OpenSSH has native support for FIDO Authentication. Its much simpler and should also be more stable with less moving parts. OpenSSH also now has support for signing arbitary files witch can be used as replacement of gnupg. Git also supports signing commits/tags with ssh keys.

Pros of FIDO

• Simpler stack / less moving parts
• Works directly with ssh, ssh-add and ssh-keygen on most computers
• Simpler
• Private key can never leave the FIDO device

Cons of FIDO

chinlung

Generating Authy passwords on other authenticators

---

*update: TBC, but this new might affect how easy it is to use this technique past August 2024: Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August

---

This gist, based in part on a gist by Brian Hartvigsen, allows you to export from Authy your TOTP tokens you have stored there.
Those can be "standard" 6-digits / 30 secs tokens, or Authy's own version, the 7-digits / 10 secs tokens.

chinlung

README

Create a template service file at /etc/systemd/system/[email protected]. The template parameter will correspond to the name of target host:

[Unit]
Description=Setup a secure tunnel to %I
After=network.target

chinlung

Install Samba 3 on OS X 10.7 Lion

Run the two commands below one at a time to get Samba 3 installed and to have it run on boot.

Install Samba with Homebrew

brew install samba

Set Samba up to launch on boot

chinlung

Portable Version KEYS:
P6Z3T-UYJC9-YAK3F-APN9M-6ZDSD
FGZPK-93CWX-Q33Y6-D5URV-YXC3X
9CZQX-9YAQA-PF33L-XVUQH-NSD48
8RZ3L-H3Y5L-W2RY5-Z5M8N-C7Z2U
CCZNU-LW3LF-K9V2T-MYZFF-94667
EWZM6-3W4UX-KH922-C96GK-VGBH2
 
Standard Version KEYS:
4AZNW-S2YHE-LLMWM-J6EL8-7QKDL

chinlung

{{-- You do not need to add this component if you are using the permanent option in the head component --}}
<script>
    if (!window.sessionTimerPermanent && window.Livewire) {
        window.livewire.hook('afterDomUpdate', startSessionTimer)
    }
    // if you are on livewire > 1.3.1 and want to avoid the default error alert
    // https://github.com/livewire/livewire/pull/1146

    window.livewire.onError(statusCode => {
        if (statusCode === 419) {

chinlung

Setting up proper permissions to a laravel directory

There are basically two ways to setup your ownership and permissions. Either you give yourself ownership or you make the webserver the owner of all files.

Webserver as owner (the way most people do it):

Assuming www-data is your webserver user.

chinlung

# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

# Add the following to your shell init to set up gpg-agent automatically for every shell
if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
    source ~/.gnupg/.gpg-agent-info
    export GPG_AGENT_INFO
else