140 karma · joined October 11, 2015
https://blog.ctis.me
Here’s one such example, which is also an interesting technical deep dive: https://signal.org/blog/building-faster-oram/
The gold standard for this would be a Hardware Security Module (HSM), which is essentially a device that stores private keys with certain guarantees of physical security (e.g, that private key material cannot be extracted from the device once it has been generated or placed there, and the device performs operations using the key material on behalf of some client).
HSMs in various forms underpin all sorts of cryptosystems that society depends on, because securing private key material at rest is essential. You'll find them everywhere from your debit/credit card, to certificate authorities, financial institutions, defense, and your smartphone.
For your use case, I'd recommend taking a look at Yubikeys. I did a writeup a while back on how to use them to store different types of private keys for various purposes:
[1] https://bundler.io/guides/bundler_in_a_single_file_ruby_scri...
>This means that the slowest computers hold back the fastest computers […]
It works so well because you’ve optimized the system’s design with respect to its bottleneck. Check out the theory of constraints :)
It's designed to military standards and to be as individually transportable as other military communications equipment:
> Department of Defense (DoD) Impact Level 5 (IL5) accreditation
> rugged and portable design that meets stringent accreditation requirements like MIL-STD-810H
> The appliance can be conveniently transported in a rugged case
> Weighing approximately 100lbs, it's human-portable, making it easy to transport and deploy in various locations.
> disaster zones, remote research stations, or long-haul trucking operations
Military operations are all three of these.
Its design enables the offline self-hosting of cloud surveillance tools:
> Google Distributed Cloud air-gapped appliance is designed to operate without any connectivity to Google Cloud or the public internet. The appliance remains fully functional in disconnected environments
> built-in AI solutions from the Google Distributed Cloud air-gapped appliance like translation, speech, and optical character recognition
What about facial recognition?
I run a large Meetup group for software developers in the Tampa Bay Area [0]
We’re multi-platform, and essentially a technology vendor for other Meetup groups in Tampa ([1]). While our overall community spans ~4,000 distinct people, only ~2,300 of those are Meetup members [1],[2]
I’ve built a ton of unique integrations around Meetup, and have built a ton of custom integrations with Meetup’s API (such as [3],[4])
If you’d like to get in touch, please do send an email to the address on our GitHub org [5]. Would love to see more competition in this space!
[2] https://go.tampa.dev/meetup
[3] https://github.com/tampadevs/events.api.tampa.dev
I've been working on Tampa Devs with the other co-founder since September of 2021, along with a group of really excellent volunteers.
We're a nonprofit that's loosely inspired by nyc's Recurse Center (https://www.recurse.com/). We host events, a mentorship program, and career development resources. All of which are free or very low cost.
Our community has grown to include thousands of local developers. It feels good to be part of something that drives a widely positive impact, especially on a local level. Anyone can do something similar no matter where they are, and I would highly recommend it.
For a cool technical angle, here's a talk I gave at a local conference on the tools we use to run our community at scale: https://go.tampa.dev/unityops.
Like the author, as well as many who have commented, I've long been disappointed in the gap between macOS' support for advanced use cases (which I need), and the iPad's portability (which I like).
I picked up a Surface Go 3. Having an actual desktop OS on a well-built, decently powerful (albeit hot at times) tablet struck the perfect balance for me. Wish I had done it years ago.
My organization is itself a 501c3, and our charitable mission is to provide developers with opportunities to learn and network. We do this by organizing monthly technical meetings, networking events, career panels, and hackathons. All at no cost to our members (no fees, tickets, or dues).
We also provide support to a larger network of meetup groups in the Tampa Bay area [2]. These groups are more specialized into specific disciplines/areas of interest. Many of these died out during the pandemic so rehabilitating that scene is an important mission for us as well.
After sorting out a couple minor snags in the build process (particularly around getting cross-compilation to work on Linux in GitHub Actions, and library validation entitlements for code signing), the finished builds work wonderfully on the M1 machines we've tested with.
I’ve just released sssecrets. Sssecrets is a Ruby gem for generating secrets (like API tokens, etc) in line with best practices.
Sssecrets is a reusable implementation of GitHub's API token format (which is also used by NPM), and it's designed to make it simple for developers to issue secure secret tokens that are easy to detect when leaked. Structured Secrets are a compact format with properties that are optimized for detection with static analysis tools. This makes it possible to automatically detect when secrets are leaked in a codebase using features like GitHub Secret Scanning or GitLab Secret Detection.
From Engineering Security, Peter Gutmann:
A European government CA marked its signing certificates as being valid for encryption only, but no-one noticed.
Another European CA marked its signature keys as not being valid for signatures.
A different CA marked its own trusted root certificate as being invalid for certificate signing.
Another national CA distributed a certificate to be used to encrypt data for the country’s tax authority that was marked as only being usable for digital signatures but not for encryption.
Yet another CA reversed the order of the bit flags in the keyUsage due to confusion over encoding endianness, essentially setting a random keyUsage in certificates that it issued.
Another CA created a self-invalidating certificate by adding a certificate policy statement stipulating that the certificate had to be used strictly as specified in the keyUsage, and a keyUsage containing a flag indicating that the RSA encryption key could only be used for Diffie-Hellman key agreement.
Most SMB leaders have enough trouble as it is keeping up with their day to day IT operations. The section at the start of the document is intended for “CEOs”, yet it’s likely impenetrable to that audience on account of the jargon while simultaneously giving advice that’s too high-level/broad to be useful.
Later parts of the document intended for technical leads are too focused on minutiae rather than outlining the overarching goals of their implementation, which loses the intended spirit of the document IMO.
For example, it’s more useful to start by outlining what these controls are trying to achieve. For example, “Ensuring business continuity after a ransomware attack” or “Protecting business assets with strong multi-factor authentication”, as opposed to throwing out specific individual technical controls without a high-level narrative to describe what you’re actually aiming for.
U2FsdGVkX1/FFKGwfCgflTAvl5rr2RP+WSQ4n/tGHuMcFnD8JFfXJfoAzIHAVakHSOiiM7MnOsAZGT2jyh/+Sgs6mgN4wea6RnMx8dIXCItuu5g462RG9un8fHivYtqdTNBa3XLp8HDWsPXMHoEoiP4M1F9nrQhMREYFp2Q6fpiEpZY4q1a+VtGpLIjdVk2k788eMQjvYZh/vruzvx751HCzz/D+lsVSFJsOaoZQpqOTj4iD/kSludUkKY7v/vk8fcew4i88RtEc63oRgarLiBEu5rB1PGxCf32/8tVVjy4/B2QmQ8nYdL50SR4oeU52lb3pyciOweuJOiE88U+WdmQ4IJ+LNozGYE514vta5Qy2ZCHgHhHNTrs32X6n9+1w0Mv0Y8z/Cxf28Rm356pIPw==
https://en.wikipedia.org/w/index.php?title=Hobby_tunneling&s...
When a new version is released, the Signal app notifies you.
This blog is statically generated by Hugo. It’s compiled and hosted by Cloudflare Pages, using GitHub for version control. Image files and other large assets are stored in BackBlaze B2 and served via Cloudflare.
I originally built it atop a functional Werc installation, but ultimately decided I would prefer static sites to running a server. Luckily, I stumbled across a port of the base Werc template and styles into Hugo’s templating system. From this I was able to port my own revisions and achieve a pleasing result, combining Werc’s aesthetic simplicity with my desire for a static site.
Avoid hostile/nonfree licensing provisions that restrict commercial use or "require corporations to pay up". Instead, create real value in diversified offerings built upon the OSS project (which is in no way artificially limited). Sidekiq is a gift, Sidekiq Pro & Enterprise are products.
Offer paid features, support, SLAs, etc that really appeal to "enterprise" use-cases. Trust that users will convert as their need for such functionality is justified by their businesses' growth and scale.
[0] https://github.com/tholman/elevator.js/pull/64
[1] https://github.com/tholman/elevator.js/issues/113
private static char encipherCharacter(char message_char, char key_char){
return (char)(((int)(message_char) + (int)(key_char) - 194)%26 + 97);
}
public static String encipher(String plaintext, String key){
String ciphertext = "";
for(int i = 0; i < plaintext.length(); i++)
ciphertext += encipherCharacter(plaintext.charAt(i), key.charAt((i % key.length())));
return ciphertext;
}
https://gist.github.com/ctrezevant/8ca9e163d702af245ded35d97...
The only feature I miss from Radicale is the built-in support for versioning in Git. It's definitely handy to keep track of/roll back changes to my calendars, contacts, todos, etc on the server.
I wrote a small script [1] that periodically syncs changes from my Nextcloud cal/cardDAV feeds into a Git repository. Sharing it here as a bonus in case it's useful to others.
The content that we create does not exist in a vacuum- humans create for the overall good of society. Everything you see and use day-to-day is an incredible amalgamation of thoughts and ideas woven together from centuries of our past and present collective knowledge.
The notion that an individual or organization can maintain exclusive control of "intellectual property" in perpetuity stands at odds with thousands of years of human history. Modern patent and copyright law seems to have forgotten this.