You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a living document. Everything in this document is made in good
faith of being accurate, but like I just said; we don't yet know everything
about what's going on.
Background
On March 29th, 2024, a backdoor was discovered in
xz-utils, a suite of software that
Setting up GH-pages with custom domain, strict (end-to-end) SSL with CloudFlare DNS & CDN
Custom domains, GH-pages, Cloudflare and strict SSL end-to-end encryption
Why I wrote this
Before Github supported SSL encryption for github pages sites, many people were using CloudFlare (CF) as their DNS provider
and CDN proxy. CF allowed users to enable SSL encryption from the CDN end points/proxies to the end user. This was great and
it allowed visitors to your website to connect with a secure connection between their browser and the cloudflare CDN box
that was serving your content. However, with this setup one (significant) link in the chain remained unencrypted and
This gist, based in part on a gist by Brian Hartvigsen, allows you to export from Authy your TOTP tokens you have stored there.
Those can be "standard" 6-digits / 30 secs tokens, or Authy's own version, the 7-digits / 10 secs tokens.
#Fixing “WARNING: UNPROTECTED PRIVATE KEY FILE!” on Linux
If you are getting this error then you probably reset the permissions on your hidden .ssh directory in your user folder, and your keys aren’t going to work anymore. It’s very important that these files not be writable by just anybody with a login to the box, so openssh will give you an error if you try to use them.
This is a more serious version of Contract Killer 3. Some language and provisions were taken from a lawyer-speak contract and injected here.
date
Identification of parties
This agreement is made between customer name ("you") of company name located at customer address and developer name ("us") of developer's company located at company address.
Purpose of agreement
You desire to retain us as an independent contractor to develop the name of application (the "application") described in the section, Technical specifications.
We are ready, willing and able to undertake the development of the application and agree to do so under the terms and conditions set forth in this agreement.