505 reputation
1311
bio website dyfis.net
location Chicago, IL
age
visits member for 4 years, 9 months
seen Dec 17 at 17:34

Just this guy, see?


Dec
8
comment What is the value of MD5 checksums if the MD5 hash itself could potentially also have been manipulated?
I'm not questioning whether a targeted MITM is likely. I'm questioning whether being careless enough to use a readily traced and attributed CA key to perform it is likely. Particularly for a sufficiently high-value target, outbound 'net traffic is liable to be recorded in enough detail to include metadata up to and including the public part of the SSL handshake, so even if the user doesn't look, their security staff or automated infrastructure might do so in retrospective analysis.
Dec
8
comment What is the value of MD5 checksums if the MD5 hash itself could potentially also have been manipulated?
It only takes one person who checks the certificate chain to cause a scandal. If you think the NSA would use a government CA key for MITM rather than using one stolen from a privately held or -- even better -- foreign certificate authority (thus providing plausible deniability), I have a bridge to sell you.
Oct
29
comment Warning for rm -r command
@ErlVolton, ...I missed your edit; re: getting a question moved, voting to close with a reason from the migration category will have that effect.
Oct
28
comment Warning for rm -r command
On a different part, by the way -- rm is provided by your operating system, not by bash. This means that this probably shouldn't be tagged bash (whether you're using bash or some other shell has no bearing on your rm command's available options or flags), but should be tagged with the specific operating system you're using.
Oct
28
comment Warning for rm -r command
Which platform is this valid on? (It's not in the POSIX spec for rm; is it GNU? Mac? ...?)
Oct
28
comment Warning for rm -r command
@ErlVolton, questions about available arguments for rm belong on SuperUser, or unix.stackexchange.com, not StackOverflow.
Oct
28
comment Warning for rm -r command
In general, "please write this thing for me" questions aren't welcome on StackOverflow -- and neither are "how do I configure this non-programming-related tool that comes with my operating system?"
Sep
30
awarded  Explainer
Sep
24
awarded  Autobiographer
Sep
20
comment Sudo vs root; any actual differences?
@EliahKagan, (...the bug in question relating to a case in which it was necessary to call setuid(geteuid()) for systemd's authentication of processes communicating with it over IPC to function properly).
Sep
20
comment Sudo vs root; any actual differences?
@EliahKagan, I thought I recalled a firsthand contrary observation -- looking up the associated bug and patch, however, it turns out to be resulted to the use of the setuid bit alone, rather that sudo.
Jun
21
comment Sudo vs root; any actual differences?
This distinction can in fact be discerned by comparing the result of geteuid() with the result of getuid(). If you happen on a program not working correctly under sudo, this is almost certainly the cause.
Jun
17
awarded  Famous Question
May
6
comment How to `rm` files in current directory and directories inside current directory
...see pubs.opengroup.org/onlinepubs/009695399/utilities/xargs.html if you have questions on that count.
May
6
comment How to `rm` files in current directory and directories inside current directory
Funny that you'd have someone with the xargs -0 GNUism, but not find -exec {} + (which GNU added long before the standard required it).
May
6
comment How to `rm` files in current directory and directories inside current directory
This works fine, but has no advantages over the -exec rm {} + approach other than compatibility with older find implementations.
May
5
comment How to `rm` files in current directory and directories inside current directory
...as another aside, options (like -r) should go before positional arguments (like the filenames given here). Some tools support doing it the other way around, and others don't; assuming that no more option parsing is done after the first positional argument is the safe and compatible approach.
May
5
comment How to `rm` files in current directory and directories inside current directory
@staticx, ...which is true because Apple picked up the feature in recent releases. Still, they aren't using GNU's find but their own, so it's not safe to assume feature parity without checking on a feature-by-feature basis.
May
5
comment How to `rm` files in current directory and directories inside current directory
@staticx, indeed, that's not a fair assumption. Lots of folks on MacOS or a BSD, and the commercial UNIX implementations do still exist.
May
5
comment How to `rm` files in current directory and directories inside current directory
@staticx, -execdir is a GNU extension, not a POSIX-standardized option.