Viktor Svub viktor-svub

Migration to ASP.NET Core in .NET 6

WebApplication and WebApplicationBuilder
Differences in the hosting model
Building libraries for ASP.NET Core
FAQ
Cheatsheet

WebApplication and WebApplicationBuilder

Jailbreak-Firefox

This script allows you to install unsigned extensions (ones that aren't approved by Mozilla) on normal Firefox builds and the official Snap! That's right, no "Firefox Developer Edition" nonsense required!

⚠️ Disclaimer ⚠️

This script is not well tested, like at all. This script might break things, possibly important things. You should probably take a backup of your Firefox profile before using it. You have been warned.

Dependencies

sudo apt install -y curl unzip zip
# Only needed when jailbreaking the Snap

preface: Posting these online since it sounds like these notes are somewhat interesting based on a few folks I've shared with. These are semi-rough notes that I basically wrote for myself in case I ever needed to revisit this fix, so keep that in mind.

I recently bought an LG ULTRAGEAR monitor secondhand off of a coworker. I really love it and it's been great so far, but I ran into some minor issues with it in Linux. It works great on both Mac and Windows, but on Linux it displays just a black panel until I use the second monitor to go in and reduce the refresh rate down to 60 Hz.

This has worked decent so far but there's some issues:

It doesn't work while linux is booting up. The motherboards boot sequence is visible just fine, but as soon as control is handed over to Linux and I'd normally see a splash screen while I'm waiting for my login window, I see nothing.
It doesn't work on the login screen. This would be fine if login consistently worked on my second screen, but I need to manually switch

Compiling a standalone executable using modern JavaScript/TypeScript runtimes

We have the same code working using node, deno, and bun.

E.g.,

bun run index.js

A Short IPv6 Guide for Home IPv4 Admins

This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.

Let’s begin.

First of all, there are some concepts that one must unlearn from ipv4:

Concept 1

	BS-SPEKE (defined on multiplicative groups)

	BS-SPEKE is a modified B-SPEKE with blind salt (OPRF). Modified B-SPEKE is a
	similar change from SPEKE as from SPAKE2 to SPAKE2+ to make it augmented. Doing
	this saves a scalar point multiply vs original B-SPEKE with blind salt. BS-SPEKE
	is the best augmented PAKE that I know of. Only problem is there are no proofs,
	but it's not hard to take the SPEKE proof, add the OPAQUE proof for OPRF, and
	it's obvious that the augmented change makes it augmented. So if anyone knows
	how to formally state that in a proof, that would be awesome to have. BS-SPEKE
	defined on ECC can be found here:

	import network
	import socket
	import time
	import struct

	from machine import Pin

	NTP_DELTA = 2208988800
	host = "pool.ntp.org"

	Double BS-SPEKE

	Double BS-SPEKE is BS-SPEKE but with 3DH vs Noise-KN to make it a doubly
	augmented PAKE. Double BS-SPEKE is the best doubly augmented PAKE that I know
	of. Only problem is there are no proofs, but it's not hard to take the SPEKE
	proof, add the OPAQUE proof for OPRF, and it's obvious that the doubly augmented
	change makes it doubly augmented. So if anyone knows how to formally state that
	in a proof, that would be awesome to have. BS-SPEKE defined on multiplicative
	groups can be found here:
	https://gist.github.com/Sc00bz/ec1f5fcfd18533bf0d6bf31d1211d4b4

	// TcbElevation - Authors: @splinter_code and @decoder_it

	#define SECURITY_WIN32
	#include <windows.h>
	#include <sspi.h>
	#include <stdio.h>

	#pragma comment(lib, "Secur32.lib")

	void EnableTcbPrivilege(BOOL enforceCheck);

	/* Gist: Win32 Message Loop with `node-addon-api`
	* Author: Gage Sorrell <[email protected]>
	* Copyright: (c) 2023 Gage Sorrell
	* License: MIT
	*/

	/* This file demonstrates how to get access to the Windows API (Win32)
	* message loop in your NodeJS application via node-addon-api.
	* This code goes into your node-addon-api package, with no additional
	* build tools necessary.