6 ms·
Not Apple related, but you could log into any linux box using a specific few versions of grub2 by hitting backspace 28 times: https://motherboard.vice.com/en_us
by judge2020 8y ago
Not Apple related, but you could log into any linux box using a specific few versions of grub2 by hitting backspace 28 times: https://motherboard.vice.com/en_us/article/ezpdqz/hack-into-a-linux-computer-by-hitting-the-backspace-28-timestimes/ https://motherboard.vice.com/en_us/article/ezpdqz/hack-into-...
- codedokode 8y agoAlso, you can bypass screen lock in Ubuntu by removing the HDD [1]. The bug still is not fixed. [1] https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1777415 https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1777415
- laumars 8y agoHonestly, I wouldn’t but that in the same class if bugs as those that preceded it because if the attacker he removed the HDD he will have access to your contents anyway (unless the HDD is encrypted) and it’s not a quick and convenient process either (unlike tapping backspace multiple times). That said, I also don’t agree that this bug should never get fixed either.
- nurettin 8y agoThis is a very naive estimation of what might happen when someone has access to all your running software. Since it is linux, it loads executables into memory and is able to run them even when they are deleted along with runtime dependencies. Anything that caches anything to anywhere other than disk will be accessible. Your memcache, your redis, some databases, keychains, your non-userdata browser sessions.
- laumars 8y agoI'm aware of that but it's a moot point because you'd be popping the storage device back in anyway. Which is why I didn't address that in my previous comment. In any case, half the examples you've provided there are server specific and you really shouldn't be allowing untrusted physical access to your servers (nor running Xorg to be honest).
- nurettin 8y agoWhile I do agree, a lot of ideas here are still laden with hindsight.
- Jonnax 8y agoThat's a bug in Unity. They dropped their own desktop environment in 18.04 for GNOME. So it's likely it won't ever be fixed.
- morganvachon 8y agoSometimes I feel like a relic using Slackware with lilo and SysV init, then I read about exploits like that and I smile.
- omeid2 8y agoI am afraid your system is _probably_ just bug ridden as any other, it is simply not popular enough to for people to find bugs.
- morganvachon 8y agoIt's actually the opposite situation. Slackware's policy is to stick to the original software as distributed by the author with only minimal patching where necessary, so if a particular program (say, KDE) has a big support community, Slackware benefits from all those eyes on the code. This leads to a very mature and stable system at the expense of running older versions of software (though there's always the -current branch for those wishing to live on the edge). Beyond this, the small but dedicated Slackware team is working daily to find and patch bugs when they do appear. You can look at the changelogs for examples of that workflow[1]. There's no such thing as a software project without bugs, but Slackware is consistently one of the most stable and robust OSes out there. [1] http://www.slackware.com/changelog/ http://www.slackware.com/changelog/
- biggestdecision 8y agoThis bug only applied to grub authentication, which isn't a widely used feature. And you could achieve the same result with boot from disk/USB if that is enabled. The vuln doesn't give you access to the actual accounts on the computer.
- seanp2k2 8y agoLet's not forget https://www.cvedetails.com/cve/CVE-2013-1050/ https://www.cvedetails.com/cve/CVE-2013-1050/ and https://www.cvedetails.com/cve/CVE-2015-7496/ https://www.cvedetails.com/cve/CVE-2015-7496/ and https://www.cvedetails.com/cve/CVE-2017-8900/ https://www.cvedetails.com/cve/CVE-2017-8900/ (to a lesser extent). Check out https://www.cvedetails.com/vulnerability-list.php?vendor_id=0&product_id=0&version_id=0&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=1&opfileinc=0&opginf=0&cvssscoremin=7&cvssscoremax=0&year=2018&month=0&cweid=0&order=3&trc=194&sha=05aa8f8c1263cd6dfb415503c9c247a410d9fb3a https://www.cvedetails.com/vulnerability-list.php?vendor_id=... for more fun.
- samstave 8y agohttp://i.imgur.com/rG0p0b2.gif http://i.imgur.com/rG0p0b2.gif
- stiGGG 8y agoOh dear, I remember something similar was possible on iOS lockscreen multiple times. What version of Windows was that?
- samstave 8y ago95. 98 had an even better one... just hitting cancel on some login boxes would let you in.
- cheerlessbog 8y agoI believe that was by design: the dialog was an opportunity to authenticate with the domain. If you just wanted local access you could hit cancel. Remember Win9x was not a secure OS itself.