@rysiek what's the issue with doing that? if you expect that command to run an exploit, malware, whateveryouwannacallit, and you are fine with what that may imply, then i don't quite see the issue; i more see an issue with literally any other curl | bash oneliner from random websites
@star@rysiek Given the "detecting curl", I believe a good part of the issue is you should not trust the script you inspected to be the one you will be delivered, and should capture the script in an inspectable context (or curl >> file, inspect file, bash file)
if you expect that command to run an exploit, malware, whateveryouwannacallit, and you are fine with what that may imply
But folks are clearly not fine with what that might imply. If this is exploit/malware, by definition it cannot be trusted. Running it directly on one's workstation means that if it is malicious, it can access all user-accessible files at the very least.
I don't believe folks running this on their workstations consider this an option, and they really should.
1