On Tue, 5 May 2020, Martin Gregorie wrote:
On Mon, 2020-05-04 at 16:25 -0600, Grant Taylor wrote:
I think $DatabaseTechnology's main benefit is keeping the password
data outside of the configuration files.
Agreed, in this sort of corner case.
select count(*) where log.key = md5(key);
Neat.
Agreed, but we still have the boundary problem.
In the hopes of leveraging existing facilities: Is there a way to mark
individual bayes tokens as poison pills?
The message is already being tokenized and scanned for Bayes (presuming
you have that enabled). If there's a way to mark a token in Bayes as
causing an automatic 1.000 then that might be a usable approach.
(Granted, it's not encrypted.)
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
I'm seriously considering getting one of those bright-orange prison
overalls and stencilling PASSENGER on the back. Along with the paper
slippers, I ought to be able to walk right through security.
-- Brian Kantor in a.s.r
-----------------------------------------------------------------------
4 days until the 75th anniversary of VE day
