Munawwar Firoz Munawwar

HTTP Streaming (or Chunked vs Store & Forward)

The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.

However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on

It "types" the contents of the clipboard.

Why can't you just paste the contents you ask? Sometimes pasting just doesn't work.

One example is in system password fields on OSX.
Sometimes you're working in a VM and the clipboard isn't shared.
Other times you're working via Remote Desktop and again, the clipboard doesn't work in password boxes such as the system login prompts.
Connected via RDP and clipboard sharing is disabled and so is mounting of local drives. If the system doesn't have internet access there's no easy way to get things like payloads or Powershell scripts onto it... until now.

Windows

The Windows version is written in AutoHotKey and easily compiles to an executable. It's a single line script that maps Ctrl-Shift-V to type the clipboard.

Setup SSH Authentication for Git Bash on Windows

Prepararation

Create a folder at the root of your user home folder (Example: C:/Users/uname/) called .ssh.
Create the following files if they do not already exist (paths begin from the root of your user home folder):

.ssh/config

Preact: Progressive Hydration

Preact now supports seamless progressive hydration.

Any component can throw during hydration (or new tree creation like a route change!), and if a component somewhere higher in the tree catches that via componentDidCatch, hydration gets paused.

Re-rendering the tree (via setState, etc) simply resumes hydration where it left off.

0u+_W!+h_+h3_01d & InWithTheNew!

Modern Password Theory in a Nutshell

By Andrew Somers

In the Beginning, there was the "hard to read" paradigm

So... We've been taught now for years to make our passwords more secure by D0!n97h!n95L!k37h!5 ("doing things like this", i.e. substituting characters with numbers and so forth).

The theory was that by increasing the character set size, password entropy would improve — at the expense of being much harder to read, harder to remember, and harder to type into the hidden void that is the password field. This has long been accepted as "the way".

But does this actually improve password safety? The short answer is "not really".

	'use strict'

	// see: https://github.com/nodejs/node/pull/6157

	var startTime = process.hrtime()
	var startUsage = process.cpuUsage()

	// spin the CPU for 500 milliseconds
	var now = Date.now()
	while (Date.now() - now < 500)

	const buffer = require('buffer');
	const crypto = require('crypto');

	// Demo implementation of using `aes-256-gcm` with node.js's `crypto` lib.
	const aes256gcm = (key) => {
	const ALGO = 'aes-256-gcm';

	// encrypt returns base64-encoded ciphertext
	const encrypt = (str) => {
	// The `iv` for a given key must be globally unique to prevent

	/**
	This is in a Nodejs environment
	*/

	const crypto = require('crypto');

	module.exports = (
	email = '',
	name = 'Anonymous',
	initialsAvatarBackground = '000000',

	function chain(value) {
	return {
	/**
	* @param {function\|string} func function or function name (in chained value)
	* @param {...any} args
	*/
	fn(func, ...args) {
	if (typeof func === 'string') {
	return chain(value[func](...args));
	}

	/*
	Made by Elly Loel - https://ellyloel.com/
	With inspiration from:
	- Josh W Comeau - https://courses.joshwcomeau.com/css-for-js/treasure-trove/010-global-styles/
	- Andy Bell - https://piccalil.li/blog/a-modern-css-reset/
	- Adam Argyle - https://unpkg.com/open-props@1.3.16/normalize.min.css / https://codepen.io/argyleink/pen/KKvRORE

	Notes:
	- `:where()` is used to lower specificity for easy overriding.
	*/