beneroth changed the topic of #picolisp to: PicoLisp language | The scalpel of software development | Channel Log: https://libera.irclog.whitequark.org/picolisp | Check www.picolisp.com for more information
rob_w has joined #picolisp
razzy has joined #picolisp
Guest28 has joined #picolisp
Guest28 has quit [Client Quit]
cranium has joined #picolisp
prestidigitator has joined #picolisp
NobleNibble has quit [Ping timeout: 252 seconds]
escew has quit [Ping timeout: 252 seconds]
escew has joined #picolisp
<tankf33der> Fixedpoint mayh tutorial
<Regenaxer> Very good
rob_w has quit [Quit: Leaving]
hunar has joined #picolisp
hunar has quit [Ping timeout: 240 seconds]
razzy has quit [Ping timeout: 248 seconds]
peterhil has quit [Ping timeout: 240 seconds]
cranium has quit [Quit: Leaving]
razzy has joined #picolisp
<razzy> anyone uses 2-factor autentication keychain?
<cess11> in what context?
<razzy> either in work or at home. cess11 how problematic it is to use. how it increase safety.
<cess11> depends entirely on the implementation
<cess11> at work we have it on one support ticket service, it's with email so the weak point is probably with social engineering of either my employer or the account retrieval process with microsoft
<razzy> cess11: well, do you have recomendation for product?
<cess11> use a hardware key
<cess11> if the organisation isn't already on password managers and long random passwords, start there
<cess11> it's the weakest link that will break, if some doofus has summer2020 as email password it doesn't matter that the email is used for 2fa
<cess11> if the organisation switches some important password for everyone every six weeks that's what will break, because it takes a fake package delivery and a recording device to catch some post-it
razzy has quit [Ping timeout: 250 seconds]
razzy has joined #picolisp
razzy has quit [Ping timeout: 240 seconds]
razzy has joined #picolisp
clacke has joined #picolisp
beneroth has joined #picolisp