See the new site: https://postgresisenough.dev
TLDR: JWTs should not be used for keeping your user logged in. They are not designed for this purpose, they are not secure, and there is a much better tool which is designed for it: regular cookie sessions.
If you've got a bit of time to watch a presentation on it, I highly recommend this talk: https://www.youtube.com/watch?v=pYeekwv3vC4 (Note that other topics are largely skimmed over, such as CSRF protection. You should learn about other topics from other sources. Also note that "valid" usecases for JWTs at the end of the video can also be easily handled by other, better, and more secure tools. Specifically, PASETO.)
A related topic: Don't use localStorage (or sessionStorage) for authentication credentials, including JWT tokens: https://www.rdegges.com/2018/please-stop-using-local-storage/
The reason to avoid JWTs comes down to a couple different points:
- The JWT specification is specifically designed only for very short-live tokens (~5 minute or less). Sessions
The easiest way to get the ClamAV package is using Homebrew
$ brew install clamav
Before trying to start the clamd daemon, you'll need a copy of the ClamAV databases.
Inside /your/location/to/brew/etc/clamav, you'll see 2 files:
Picking the right architecture = Picking the right battles + Managing trade-offs
- Clarify and agree on the scope of the system
- User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?
| /** | |
| * ================== angular-ios9-uiwebview.patch.js v1.1.1 ================== | |
| * | |
| * This patch works around iOS9 UIWebView regression that causes infinite digest | |
| * errors in Angular. | |
| * | |
| * The patch can be applied to Angular 1.2.0 – 1.4.5. Newer versions of Angular | |
| * have the workaround baked in. | |
| * | |
| * To apply this patch load/bundle this file with your application and add a |
| #!/usr/bin/env node | |
| // Based on the 'replace text' hook found here: http://devgirl.org/2013/11/12/three-hooks-your-cordovaphonegap-project-needs/ | |
| // This hook should be placed in the 'after_prepare' hook folder. | |
| // The hook relies on a JSON file located at '<project_root>/resources/.build.json' to track the build number. | |
| // build.json content: | |
| // {"build: 1} | |
| // Add 'BUILDNR' to the version number in the '<project_root>/config.xml' file. |
Revised date: 07/11/2012
Between us [company name] and you [customer name]
We’ll always do our best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract you won’t find any complicated legal terms or long passages of unreadable text. We’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.
| // WebKit font-smoothing | |
| //------------------------------------------------ | |
| // References: | |
| // | |
| // 1. http://maxvoltar.com/sandbox/fontsmoothing/ | |
| // 2. http://maxvoltar.com/archive/-webkit-font-smoothing | |
| // | |
| // Values: none, antialiased (default), subpixel-antialiased | |
| // |