It's fairly common to say whitelisting and blacklisting to describe
desirable and undesirable things in cyber security. However just because
it is common doesn't mean it's right.
However, there's an issue with the terminology. It only makes sense if
you equate white with 'good, permitted, safe' and black with 'bad,
dangerous, forbidden'. There are some obvious problems with this.
You may not see why this matters. If you're not adversely affected by
racial stereotyping yourself, then please count yourself lucky. For some
of your friends and colleagues (and potential future colleagues), this
really is a change worth making.
From now on, we will use 'allow list' and 'deny list' in place of
'whitelist' and 'blacklist' wherever possible. Which, in fact, is
clearer and less ambiguous. So as well as being more inclusive of all,
this is a net benefit to our understandability.
(Words mostly borrowed from
<https://www.ncsc.gov.uk/blog-post/terminology-its-not-black-and-white>)
Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Change missing columns to datetime2. All columns of datetime are
now changed to datetime2.
Co-authored-by: mattinbits <3765307+mattinbits@users.noreply.github.com>
Co-authored-by: sirVir <sirVir@users.noreply.github.com>
pylint has poor support for alembic so alembic.op module will
fail ci if not ignored.
Fix code formatting.
Kaxil Naik
Ash Berlin-Taylor
Jiajie Zhong
Tomek Urbaszek
Jarek Potiuk
Tomek
Kamil Breguła
Kevin Yang
Morten Post