Interviews are supposed to evaluate whether a candidate can do the job. All too often, though, they become tests of endurance, performance, or obedience. And some of the most common interview questions aren’t just unhelpful, rather lazy, intrusive, and manipulative, reflecting a deeper problem in how companies approach hiring. If we want real insight, we have to ask insightful questions. That sounds obvious, but it’s staggering how many interviews still fall back on shallow or shady lines of questioning. You’ve invested hours wading through half-baked applications, irrelevant referrals, and now AI slop. After all that effort, why would you waste the actual interview, the most valuable moment, with questions that produce rehearsed answers and zero useful insight? Let’s look at four of the worst interview questions to ask, not just to call them out, but to push for a smarter, more respectful way of interviewing that both values people and leads to better hiring decisions. 1. Can you ...
The most difficult part of setting up a chroot environment is identifying dependencies for the programs you want to copy to the jail. For example, to make cp available, not only do you need to copy its binary from /bin and any shared libraries it depends on, but the dependencies can have their own dependencies too that need to be copied. The internet suggests using ldd to list a binary’s dependencies, but that has its own problems. The man page for ldd warns not to use the script for untrusted programs because it works by setting a special environment variable and then executes the program. What’s a security-conscious systems administrator to do? The ldd man page recommends objdump as a safe alternative. objdump outputs information about an object file, including what shared libraries it links against. It doesn’t identify the dependencies’ dependencies, but it’s still a good start because it doesn’t try to execute the target file. We can overcome the dependencies of depende...