HiddenLayer555@lemmy.ml to Programmer Humor@programming.devEnglish · edit-21 month agoSQL Injectionlemmy.mlimagemessage-square10fedilinkarrow-up113arrow-down10file-textcross-posted to: programmerhumor@lemmy.ml
arrow-up113arrow-down1imageSQL Injectionlemmy.mlHiddenLayer555@lemmy.ml to Programmer Humor@programming.devEnglish · edit-21 month agomessage-square10fedilinkfile-textcross-posted to: programmerhumor@lemmy.ml
minus-squareCanadaPlus@lemmy.sdf.orglinkfedilinkarrow-up1·1 month agoSo does that imply they already knew the candidate they were hiring, and were just checking if this is the guy?
minus-squareMadhuGururajan@programming.devlinkfedilinkEnglisharrow-up1·25 days agoNo the interviewer is personification of the naive backend that checks only that a specific row is present in the DB, or that’s how I read it.
minus-squareCanadaPlus@lemmy.sdf.orglinkfedilinkarrow-up1·25 days agoSo I guess the interview is handled by a non-vulnerable intermediate process, which adds the hire to the the main table of employees when at some point in a successful interview, and then calls a notification process that just searches it?
minus-squareMadhuGururajan@programming.devlinkfedilinkEnglisharrow-up2·25 days agoyeah something like “if new candidate in employee DB == hired”
So does that imply they already knew the candidate they were hiring, and were just checking if this is the guy?
No the interviewer is personification of the naive backend that checks only that a specific row is present in the DB, or that’s how I read it.
So I guess the interview is handled by a non-vulnerable intermediate process, which adds the hire to the the main table of employees when at some point in a successful interview, and then calls a notification process that just searches it?
yeah something like “if new candidate in employee DB == hired”