DeckerSU

Про токены, JSON Web Tokens (JWT), аутентификацию и авторизацию. Token-Based Authentication

Last major update: 25.08.2020

• Что такое авторизация/аутентификация
• Где хранить токены
• Как ставить куки ?
• Процесс логина
• Процесс рефреш токенов
• Кража токенов/Механизм контроля токенов

DeckerSU

# Cloudflare Dynamic DNS update script
# Required policy: read, write, test, policy
# Add this script to scheduler
# Install DigiCert root CA or disable check-certificate
# Configuration ---------------------------------------------------------------------

:local TOKEN "__APITOKEN__"
:local ZONEID "__ZONEIDENTIFIER__"
:local RECORDID "__RECORDIDENTIFIER__"
:local RECORDNAME "__DNSRECORD__"

DeckerSU

Multiple SSH Keys settings for different github account

create different public key

create different ssh key according the article Mac Set-Up Git

$ ssh-keygen -t rsa -C "your_email@youremail.com"

DeckerSU

rsync daemon mode over ssh

There are several common ways to do rsync backups of hosts over ssh:

1. As a non-root user. Upsides: very secure. Downside: cannot back up sensitive files.
2. As root, with a public key. Downsides: Whoever has the private key has full root access to the host being backed up.
3. As root, with a public key and a "forced command". Upsides: Restricts access to the server. Downsides: Requires either careful matching of rsync options (which might change over time), or "validator" scripts. Neither idea sounds very appealing to me.
4. Running rsync in daemon mode on the host being backed up. Upsides: Lots of useful options, like read-only mode, running as a different user if required, server-side excludes/includes, etc. Downsides: Opens up a TCP port that has full filesystem read access and is hard to secure (Ideally you could make the rsync daemon use a unix socket instead, that could be secured by filesystem permissions, but I haven't found a way to do that).

Here is another option t

DeckerSU

GITIAN BUILD for BTC v0.16.3

Prepare VM

• Setup Debian virtual machine on VirtualBox
  https://github.com/bitcoin-core/docs/blob/master/gitian-building/gitian-building-create-vm-debian.md

---

DeckerSU

Keybase proof

I hereby claim:

• I am DeckerSU on github.
• I am deckersu (https://keybase.io/deckersu) on keybase.
• I have a public key whose fingerprint is FD9A 772C 7300 F4C8 94D1 A819 FE50 4808 62E6 451C

To claim this, I am signing this object:

DeckerSU

#!/bin/bash

# Build script for KeePassXC for Ubuntu 16.04 (x64) by Decker (q) 2019

# Follow the original instructions, i.e. mkdir build, cd build, place script in created
# build folder and run. You should get your keepassxc binaries in build/release folder.

CURDIR=$(pwd)
PREFIX=${CURDIR}/depends
BUILD=${CURDIR}/release

DeckerSU

# maximum capability of system
user@ubuntu:~$ cat /proc/sys/fs/file-max
708444

# available limit
user@ubuntu:~$ ulimit -n
1024

# To increase the available limit to say 200000
user@ubuntu:~$ sudo vim /etc/sysctl.conf

DeckerSU

some important text

DeckerSU

test1