Bumps [jsrsasign](https://github.com/kjur/jsrsasign) from 11.1.0 to 11.1.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/kjur/jsrsasign/blob/master/ChangeLog.txt">jsrsasign's changelog</a>.</em></p> <blockquote> <p>ChangeLog for jsrsasign</p> <ul> <li>Changes from 11.1.0 to 11.1.1 (2026-Feb-20) <ul> <li>security fix for DSA and BigInteger <ul> <li>PR <a href="https://redirect.github.com/kjur/jsrsasign/issues/651">#651</a>, <a href="https://redirect.github.com/kjur/jsrsasign/issues/650">#650</a>, <a href="https://redirect.github.com/kjur/jsrsasign/issues/649">#649</a>, <a href="https://redirect.github.com/kjur/jsrsasign/issues/648">#648</a>, <a href="https://redirect.github.com/kjur/jsrsasign/issues/647">#647</a>, <a href="https://redirect.github.com/kjur/jsrsasign/issues/646">#646</a>, <a href="https://redirect.github.com/kjur/jsrsasign/issues/645">#645</a>. Thank you <a href="https://github.com/Kr0remer"><code>@Kr0remer</code></a></li> <li>After assigned CVE number reports will be added.</li> </ul> </li> <li>SECURITY.md added. Thank you <a href="https://github.com/njg7194"><code>@njg7194</code></a></li> </ul> </li> </ul> <p>restore KJUR.crypto.Cipher class without RSA/RSAOAEP support</p> <ul> <li>Changes from 11.0.0 to 11.1.0 (2024-Feb-01) <ul> <li>src/crypto.js <ul> <li>restore KJUR.crypto.Cipher class without RSA and RSAOAEP encryption/decryption support</li> </ul> </li> </ul> </li> </ul> <p>remove RSA and RSAOAEP encryption for Marvin attack</p> <ul> <li>Changes from 10.9.0 to 11.0.0 (2024-Jan-16) <ul> <li>remove RSA PKCS#1.5 end OAEP encryption/decryption for Marvin attack (<a href="https://redirect.github.com/kjur/jsrsasign/issues/598">#598</a>)</li> <li>src/crypto.js <ul> <li>remove KJUR.crypto.Cipher class for RSA and RSAOAEP encryption/decryption</li> </ul> </li> <li>ext/{rsa,rsa2}.js remove encrypt/decrypt/encryptOAEP/decryptOAEP for RSAKey class</li> </ul> </li> </ul> <p>enhanced support for encrypted PKCS8</p> <ul> <li>Changes from 10.8.6 to 10.9.0 (2023-Nov-27) <ul> <li>KEYUTIL.getPEM is updated not to use weak ciphers (<a href="https://redirect.github.com/kjur/jsrsasign/issues/599">#599</a>) <ul> <li>default encryptionScheme is changed from des-EDE3-CBC to aes256-CBC</li> <li>default prf is changed from hmacWithSHA1 to hmacWithSHA256</li> </ul> </li> <li>src/keyutil.js <ul> <li>more encrypted PKCS#8 private key support <ul> <li>KEYUTIL.getKey now supports encrypted PKCS#8 private key with aes128-CBC, aes256-CBC encrypted and using hmacWithSHA224/256/384/512 as psudorandom function.</li> <li>KEYUTIL.getPEM now supports such as above encrypted PKCS#8 PEM priavte key.</li> </ul> </li> </ul> </li> <li>src/crypto.js <ul> <li>Cipher.decrypt/encrypt now supports symmetric ciphers (des-EDE3-CBC,aes128-CBC,aes256-CBC)</li> </ul> </li> <li>src/base64x.js <ul> <li>function inttohex and twoscompl are added</li> </ul> </li> <li>src/asn1.js <ul> <li>ASN1Util.bigIntToMinTwosComplementsHex is now DEPRECATED. use twoscompl.</li> </ul> </li> <li>src/asn1x509.js <ul> <li>aes*-CBC and hmacWithSHA* OIDs are added</li> </ul> </li> <li>test/qunit-do-{base64x,crypto-cipher,keyutil-eprv,keyutil,keyutil-p8egen}.html <ul> <li>update and add some test cases for above</li> </ul> </li> <li>stop bower support (bower.json removed)</li> </ul> </li> </ul> <p>X509.getExtSubjectDirectoryAttributes another bugfix</p> <ul> <li>Changes from 10.8.5 to 10.8.6 (2023-Apr-26) <ul> <li>src/x509.js <ul> <li>another bugfix X509.getExtSubjectDirectoryAttributes method</li> </ul> </li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|---|---|---|
| .. | ||
| api | ||
| assets | ||
| config | ||
| generators/landing-page | ||
| scripts | ||
| tasks | ||
| views | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .htmlhintrc | ||
| .lesshintrc | ||
| .npmrc | ||
| .sailsrc | ||
| app.js | ||
| Gruntfile.js | ||
| package.json | ||
| Procfile | ||
| README.md | ||
fleetdm.com
This is where the code for the public https://fleetdm.com website lives.
Bugs
To report a bug or make a suggestion for the website, create an issue in the fleet GitHub repository.
Testing locally
See https://fleetdm.com/handbook/engineering#test-fleetdm-com-locally
Deploying the website
To deploy changes to the website to production, merge changes to the main branch. If the changes affect the website's code, or touch any files that the website relies on to build content, such as the query library, osquery schema, docs, handbook, articles, etc., then the website will be redeployed.
Wondering how this works? This is implemented in a GitHub action in this repo. Check out the code there to see how it works! For help understanding what
sails runandnpm runcommands in there do, check the scripts inwebsite/package.jsonand inwebsite/scripts/.
Changing the database schema
To deploy new code to production that relies on changes to the database schema or other external systems (e.g. Stripe), first put the website in "maintenance mode" in Heroku. Then, make your changes in the database schema. Next, if you have a script to fix/migrate existing data, go ahead and run it now. (e.g. sails run fix-or-migrate-existing-data). Then, merge your changes and wait for the deploy to finish. Finally, switch off "maintenance mode" in Heroku.
Note that entering maintenance mode prevents visitors from using the website, so it should be used sparingly, and ideally at low-traffic times of day.
Warning: Doing an especially sensitive schema migration? There is a potential timing issue to consider, thanks to an infrastructure change that eliminated downtime during deploys by using Heroku's built-in support for hot-swapping. Read more in https://github.com/fleetdm/fleet/issues/6568#issuecomment-1211503881
Wiping the production database
I hope you know what you're doing. The "easiest" kind of database schema migration:
sails_datastores__default__url='REAL_DB_URI_HERE' sails run wipe
Then when you see the sailboat, hit CTRL+C to exit. All done!