slimsag

Mar 11: In Effort to Bolster Government Cybersecurity, Biden Administration Takes Step to Ensure Secure Dev

• Article link
• The actual software security attestation form which outlines minimum requirements

Today’s release of the secure software development attestation form reinforces secure-by-design principles advanced by CISA, Federal government partners, and international allies:

The referenced secure-by-design principles published by CISA

Note: the above includes 9 references to memory safe, which it regards as:

slimsag

sourcegraph % bazel test //cmd/frontend/internal/context/...
INFO: Analyzed 3 targets (0 packages loaded, 0 targets configured).
ERROR: /Users/stephen@sourcegraph.com/work/sourcegraph/cmd/frontend/internal/context/resolvers/BUILD.bazel:21:8: GoCompilePkg cmd/frontend/internal/context/resolvers/resolvers_test.internal.a failed: (Exit 1): builder failed: error executing GoCompilePkg command (from target //cmd/frontend/internal/context/resolvers:resolvers_test) bazel-out/darwin_arm64-opt-exec-ST-13d3ddad9198/bin/external/go_sdk/builder_reset/builder compilepkg -sdk external/go_sdk -installsuffix darwin_arm64_race -tags race -src ... (remaining 73 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
cmd/frontend/internal/context/resolvers/context_test.go:105:6: no new variables on left side of :=
compilepkg: error running subcommand GOROOT_FINAL=GOROOT \
GOEXPERIMENT=nocoverageredesign \
GOOS=darwin \
ZERO_AR_DATE=1 \

slimsag

PS C:\dev\shuttle-projects\shuttle> cargo tree
    Updating crates.io index
    Updating git repository `https://github.com/shuttle-hq/tokiotest-httpserver`
    Updating git repository `https://github.com/chesedo/hyper-reverse-proxy`
  Downloaded outref v0.5.1
  Downloaded predicates-tree v1.0.9
  Downloaded dirs-sys v0.3.7
  Downloaded crc-catalog v2.4.0
  Downloaded diff v0.1.13

slimsag

RG353P:/data/anr # cat anr_2023-09-06-16-33-55-478

----- pid 6743 at 2023-09-06 16:33:55 -----
Cmd line: net.random_projects.zig_android_template
Build fingerprint: 'RG353P/RG353P/RG353P:11/RD2A.211001.002/eng.dell.20230306.183900:userdebug/release-keys'
ABI: 'arm64'
Build type: optimized
Zygote loaded classes=15739 post zygote classes=43
Dumping registered class loaders
#0 dalvik.system.PathClassLoader: [], parent #1

slimsag

macOS frame rate of a simple triangle example
starts with vsync enabled and then disabled vsync (printed).
The FPS is printed once every 0.25s


FPS: 60
FPS: 60
FPS: 59
FPS: 61
FPS: 60

slimsag

diff --git a/CMakeLists.txt b/CMakeLists.txt
index ed4948f..5b4e112 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -2,10 +3,15 @@
 # Originally created for "roxlu build system" to compile libyuv on windows
 # Run with -DTEST=ON to build unit tests
 
-PROJECT ( YUV C CXX )	# "C" is required even for C++ projects
 CMAKE_MINIMUM_REQUIRED( VERSION 2.8 )

slimsag

If existing already, delete the default k3d cluster:

k3d cluster delete

Start a k3d cluster and port forward the loadbalancer:

k3d cluster create -p "30080:80@loadbalancer"

slimsag

If existing already, delete the default k3d cluster:

k3d cluster delete

Start a k3d cluster and port forward the loadbalancer:

k3d cluster create -p "30080:80@loadbalancer"

slimsag

OS	Arch	Model	CPU	RAM	Storage
macOS	arm64	2020 Mac Mini	Apple Silicon M1 8 core 3.2ghz	8GB	512G SSD
macOS	x86	Late 2014 Mac Mini	Intel i7 8 core 3ghz	16GB	256G SSD
linux	x86	Beelink GTR5 5900HX	Ryzen 9 5900HX 8 core 4.6ghz	32GB	512G SSD
windows	x86	Beelink GTR5 5900HX	Ryzen 9 5900HX 8 core 4.6ghz	32GB	512G SSD
windows	arm64	Windows Dev Kit 2023	Snapdragon 8cx Gen 3, 8 core ~3ghz	32GB	512G SSD
linux	arm64	Radxa ROCK pi 5B	RK3588 8 core ~2.4ghz	16G	512G SSD

• Case: KENUCO SOHO Mini 10" Rack

slimsag

Proprietary mesh triangulation in open source software?

Recently I was looking for a solid, reliable way to do path triangulation. Looking at state-of-the-art research, I came across the UC Berkley researcher Jonathan Shewchuk's outstanding Triangle library.

Jonathan is very clear on the Triangle website, and in source code, about the project not being open-source:

This program may be freely redistributed under the condition that the copyright notices (including this entire header and the copyright notice printed when the `-h' switch is selected) are not removed, and no compensation is received. Private, research, and institutional use is free.