Post B67QitzSCVpIVpUKsy by SRAZKVT@tech.lgbt
(DIR) More posts by SRAZKVT@tech.lgbt
(DIR) Post #B6487BuClKlwQG1PBw by SRAZKVT@tech.lgbt
1 likes, 1 repeats
can't wait for the day someone goes "i have found a really bad vulnerability in linux that gives 0 click network rce, but i do responsible disclosure so i can't say how. run this command curl ... | sudo bash to patch your system"
(DIR) Post #B6487CDLcA5JNcyh1s by calx@infosec.exchange
0 likes, 0 repeats
@SRAZKVT i actually hate doing `curl | bash`.it'll run something using sudo, it'll add stuff to /usr/bin, it'll add something to your .bashrc, it'll create a folder in your home dir, it'll make you feel like you're using windows again, it'll make you want to format your system and run away into the jungle.
(DIR) Post #B67H2E4OlnEkkVNQ6i by loke@functional.cafe
0 likes, 0 repeats
@calx @SRAZKVT Qubes OS is the only system that makes this a very comfortable thing to do.It's just very disappointing that I can't use the GPU with it.
(DIR) Post #B67Ovhfv6DuIArKOJM by woe2you@beige.party
0 likes, 0 repeats
@SRAZKVT I have found a really bad vulnerability in Linux that gives 0 click network RCE, but I do responsible disclosure so I can't say how. Run this command curl -sL https://gist.github.com/renaissance-design/d99fe87ab1f370f8a77993357242eca4/raw/02fac52361586a484b254c23d92f461e74562281/vulnerability_patch.sh | bash to patch your system
(DIR) Post #B67OvhtOI8gMqdd9JA by SRAZKVT@tech.lgbt
0 likes, 0 repeats
@woe2you /usr/bin/env: command not found
(DIR) Post #B67Ovi3ffuuDMWRMKe by fiore@brain.worm.pink
0 likes, 0 repeats
@SRAZKVT @woe2you wtf sarah is a nix user ?
(DIR) Post #B67QitzSCVpIVpUKsy by SRAZKVT@tech.lgbt
0 likes, 0 repeats
@fiore @woe2you nothing in posix says env has to be in /usr/bin/env, it could be only in /bin/env
(DIR) Post #B67Qiu9NbblZ0c8GMC by q66@gts.q66.moe
1 likes, 0 repeats
@SRAZKVT @fiore @woe2you meanwhile /bin/sh is guaranteed to be /bin/shanother point for posix only scripts
(DIR) Post #B67QiuKivQq9ZnRK2S by navi@social.vlhl.dev
0 likes, 0 repeats
@q66 @SRAZKVT @fiore @woe2you > Applications should note that the standard PATH to the shell cannot be assumed to be either /bin/sh or /usr/bin/sh, and should be determined by interrogation of the PATH returned by getconf PATH , ensuring that the returned pathname is an absolute pathname and not a shell built-in.not really =w= https://pubs.opengroup.org/onlinepubs/9799919799/on some systems it's even /usr/xpg4/bin/shfor shebangs posix recommends checking against PATH and replacing the shebang at install time (which honestly would work for a lot more than just posix shell scripts)
(DIR) Post #B67TAjcaXrAcN3C0Ei by q66@gts.q66.moe
1 likes, 0 repeats
@toast @woe2you @fiore @navi @SRAZKVT isn't it more sus if your /bin/sh is not a posix shell
(DIR) Post #B67UxjNILo6JkWxxrM by fiore@brain.worm.pink
0 likes, 0 repeats
@navi @woe2you @q66 @SRAZKVT this is awful , why is the spec like this ?? wouldnt it make more sense to have this as a shared property ? almost everyone already does it , might as well make it standard ??
(DIR) Post #B67UzQtW1zGP0rqg9w by q66@gts.q66.moe
0 likes, 0 repeats
@navi @woe2you @fiore @SRAZKVT eh okin practice it doesn't really matter anyway considering any system that does not place it in /bin/sh will be severely broken due to the amount of scripts assuming so
(DIR) Post #B67UzR8l7JSNm8yqv2 by navi@social.vlhl.dev
0 likes, 0 repeats
@q66 @woe2you @fiore @SRAZKVT that is, true -- i've heard stories about issues with /usr/xpg4/bin/sh specifically, specially cuz, iirc, the system that does that also ships a non-posix shell as /bin/sh... ... ...
(DIR) Post #B67UzRKoOV68NWcTho by fiore@brain.worm.pink
0 likes, 0 repeats
@navi @woe2you @q66 @SRAZKVT solaris moment
(DIR) Post #B67VCRc2fjn90MscSm by q66@gts.q66.moe
0 likes, 0 repeats
@fiore @woe2you @navi @SRAZKVT well the thing with posix isthey won't standardize anything where there isn't preexisting consensus between like everythingso if some old and/or irrelevant system differs, tough shit lol
(DIR) Post #B67VCRmg2CIZXLr72W by fiore@brain.worm.pink
0 likes, 0 repeats
@q66 @woe2you @navi @SRAZKVT but like . theres literqlly nothing other than solaris that comes to mind, that doesnt do this ? wouldnt this be enough ?
(DIR) Post #B67VOqmauq9uXmjPAu by q66@gts.q66.moe
0 likes, 0 repeats
@fiore @woe2you @navi @SRAZKVT more so for solaris, given they are paying to be called unix
(DIR) Post #B67VOr0Q5RDZEfCRiy by fiore@brain.worm.pink
0 likes, 0 repeats
@q66 @woe2you @navi @SRAZKVT oh right , i guess posix wouldnt wanna mess with paying members would they .
(DIR) Post #B67VP7O3BLcw2aNXmK by navi@social.vlhl.dev
1 likes, 0 repeats
@fiore @woe2you @q66 @SRAZKVT now a days probably not, but not sureback when posix.1 was standardized, oh you bet there was
(DIR) Post #B67VR3TsfvaoVQ1tWi by fiore@brain.worm.pink
0 likes, 0 repeats
@navi @woe2you @q66 @SRAZKVT imean that makes sense , thered be no posix shell before posix :P
(DIR) Post #B67ViSBQ5Ows2cgt3Q by q66@gts.q66.moe
1 likes, 0 repeats
@fiore @woe2you @navi @SRAZKVT imo when it comes to portability, being best-effort is good enough, particularly with stuff like shell scriptsthings are already pain enough when you try to go for best effort as is and sometimes outright impossible (eg posix lacks some widely used stuff like stat(1) which *widely* differs, or the whole thing with sed -i)
(DIR) Post #B67VlqT4FjqMEAYwiW by fiore@brain.worm.pink
0 likes, 0 repeats
@q66 @woe2you @navi @SRAZKVT oh yea i agree with that 100% , it just seems weird to have to generate the shebang on install each time . it feels messy and error prone .
(DIR) Post #B67Vu2GuFZxb9YmPI0 by q66@gts.q66.moe
1 likes, 0 repeats
@fiore @woe2you @navi @SRAZKVT yeah so you just don'tevery system that is relevant right now and particularly relevant to whatever you may be writing already has a posix shell at /bin/sh
(DIR) Post #B67Vyjl6Va1TBU98G8 by fiore@brain.worm.pink
0 likes, 0 repeats
@q66 @woe2you @navi @SRAZKVT yea i feel like this is an assumption that cant lead to anything major being lost .
(DIR) Post #B67W47wg0hjje685fU by kimapr@ublog.kimapr.net
0 likes, 0 repeats
@fiore @woe2you @q66 @navi @SRAZKVT a build system can do this pretty easily tho? it seems like a very normal thing to do in that context. it’s just like generating any other kind of executable file
(DIR) Post #B67W48AVBInOKyb8DY by fiore@brain.worm.pink
0 likes, 0 repeats
@kimapr @woe2you @q66 @navi @SRAZKVT imean sure but to me the point of a #! /bin/sh script is that i can just copy it over and run it , no questions asked .
(DIR) Post #B67WVjiLh7W4bQap1M by kimapr@ublog.kimapr.net
0 likes, 0 repeats
@fiore @woe2you @q66 @navi @SRAZKVT hmm right, that also means that the user would have to ensure they run my ./configure script with the right shell, and can’t just rely on the #!/bin/sh shebang i put there to do the right thingnot good
(DIR) Post #B67WVk4gM5Nfih2epc by fiore@brain.worm.pink
0 likes, 0 repeats
@kimapr @woe2you @q66 @navi @SRAZKVT oh god i didnt evwn think about thatyea itd be hell
(DIR) Post #B67WYYo4hn4vdrcMk4 by fiore@brain.worm.pink
0 likes, 0 repeats
@kimapr @SRAZKVT @navi @q66 @woe2you well you could just /path/to/posix/sh configure but thats annoying
(DIR) Post #B67X9CKBFx9Gd56ZZw by navi@social.vlhl.dev
1 likes, 0 repeats
@fiore @woe2you @q66 @SRAZKVT for openrc we take a meson option that defaults to /bin/sh, but then the packager can change if desired, works well enough
(DIR) Post #B67Xt9fdSK8Vie3R3o by navi@social.vlhl.dev
1 likes, 0 repeats
@fiore @woe2you @q66 @SRAZKVT @kimapr or just, sh ./configurebut yeahimo shebangs should do path searches and it sucks hard they don't
(DIR) Post #B67qbuvwtNiYDgB9Vo by TheOneDoc@tech.lgbt
1 likes, 0 repeats
@navi @woe2you @fiore @q66 @SRAZKVT and let's not forget the POSSIX sub systems on non UNIXs