Hacker Newsnew | past | comments | ask | show | jobs | submit | RGS1811's commentslogin

I got a lot of questions about the names of root level linux directories, which while good knowledge doesn't seem to fit under the title description.


There's a download button at the bottom of the player.



True, and penalizing misbehavior is a big part of the solution here, but it's also true that there are practical social limits on behavior (including competitive behavior), and these can wax and wane culturally, giving rise to greater or lesser degrees of trust and good faith in commerce. ("What can I count on from people in general?")


The standard scored against was mostly good, although his preferred column width was pretty arbitrary, and the best line-height can depend on the context of a piece of text and its use.


Plato's procedural/dialogical approach to learning is also vastly superior to the Kantian/illuminist 'one and done' understanding of proof and discovery. Kant was a funny sort of progressive, who also believed that his work in metaphysics and epistemology laid the absolute foundation for the field.

It's odd but only enlightenment and post-enlightenment thinkers seem to approach their work this way, as if it were an absolute step forward which will never need to be revisited. You don't generally find it in ancient or medieval philosophers, who are much more interested in eking out nuance and exposing difficulties than in laying absolute groundworks and so on. In the enlightenment (at least in philosophy), progressivism and delusional absolutism always go hand in hand.


His Master's Voice is the most philosophically rigorous and profound piece of Sci-Fi I've read. Yes, it's hard to get through. It doesn't really have a plot. But wow, Lem really thought through the difficulties and implications of the scenario, and the science in the fiction is either intelligent and plausible or simply correct. And to top it all off, he appreciates how much the socio-political dimension of science impact the trajectory of the project, and explains the dynamics of that side of it really well.


The most disturbing thing about iCloud Keychain is that you can get access to all of your stored passwords just by unlocking a device linked to your Apple ID. Not just the ability to log in with them, the actual plaintext.


Urm, if you have the ability to log in with a password to a website, you require the plain text password. Keychain also prompts for your user password before allowing plaintext access, not just the fact you're logged in.

Not sure what else is expected in this case, you'd get the same behavior from most other password managers.


Keychain doesn't prompt for your user password on iOS. Just your unlock code. That's what bothers me.


But iOS won’t reveal the plaintext password from the keychain to the user (it will only autocomplete forms).


It will if you go to settings->accounts and passwords.


you still get a password or touch if prompt before showing the passwords.


I assume RGS1811 was worried about someone using your finger for TouchID or face for FaceID, involuntarily. I also worry about that, especially if you get knocked out or black out or something, but I think the solution is to not have important login info in the keychain at all, such as access to money (bank apps), email, or other uses that can be used to verify your identity or steal from you.


If that is a legitimate concern, then don't use Touch ID or Face ID. By using those a person is intentionally choosing convenience over security. By even saving passwords in an account-shared fashion (be it Keychain, LastPass, or 1Password), you're giving up some security for convenience.

The latest iOS versions have also included a "five clicks on the power button" emergency option, which disables both TouchID and FaceID. It's not perfect, but if you're going into a questionable situation, it's a good way to avoid being coerced into using those to unlock your phone.


What made me concerned was the discovery that, on an old iPad mini I rarely use (without touch id / face id), entering the standard four digit unlock code is enough to get access to the full list of logins/passwords stored by iCloud Keychain. I would like to have to at least re-enter my apple ID to get at this full list.


Don’t use a basic unlock code then. I use an XKCD style passcode to unlock mine.


This isn't unique to Apple: Google has adopted the same policy.

It's not clear what the best solution is here, or if the best way to have the conversation about it follows hyperbole like "the most disturbing thing".

I think password managers are on the whole a good thing because people are using more (stronger) passwords.

I also think the password manager could (at least on trusted hardware like an iPhone) provide some protection from the attacks you're alluding to, such as a tarpit that slows access to the password database, but they certainly won't offer any protection on a desktop machine without specialised hardware and it might be difficult to get right -- difficult enough that new security vulnerabilities are introduced instead.

What exactly do you propose?


I think Firefox's solution is a little better. You can set a master password which is used to encrypt the password database. To unlock you have to enter the password. You can browse without unlocking.


Both the iPhone and Google Chrome ask for authentication before showing the passwords.

Firefox works similarly: Once you unlock it, you see all the passwords. On an iPhone or Google Chrome, you have to click each password you want to see.


Fortunately, Chrome for Linux and Chrome OS don't ask. Both OSes trust users to control access at the session level.


You need a second factor (physical access to a device already in the circle) to add a device to the iCloud Keychain.

Edit: I see you are worried about devices already linked


I don't believe this is entirely accurate – a further auth prompt is always required before revealing plain-text passwords.


I've often enjoyed smalin's visualizations, which I find a little easier to follow visually than andy filebrown's. E.g. https://www.youtube.com/watch?v=LlvUepMa31o


Seconded! I remember being wowed by his Debussy Arabesque visualization many years ago. Still worth a watch/listen! https://youtu.be/A6s49OKp6aE


I came for the filesystem bugs, I stayed for the absurd root exploit, but its the little crashes, rendering glitches, and feeling of general instability that made me fall in love with High Sierra...


APFS has been nothing but pain for me. File system changes show up in Finder minutes later! I should have stayed in Sierra.


Unfortunately, it seems Apple has forced us to choose between Meltdown mitigation and a somewhat working OS. The recent Sierra security updates didn’t include the Meltdown patch.

https://twitter.com/theregister/status/949358083431546880


Apple has actually backported the fix to Sierra and even El Capitan. https://support.apple.com/en-us/HT208331


The tweet in the post you replied to points out that the page that you linked to was altered today to no longer say the fixes extended to those two.


My educated guess, based on 14-years working for MIT’s IT department: the fixes for Sierra and El Capitan broke something important, so they got pulled.

When they get fixed, they’ll be re-released…


My MacMini6,2 (2012 Server) has two SSDs RAIDed together. High Sierra beta worked fine and upgraded fine to golden master and subsequent. When I decided to reinstall my OS from scratch and reload from backups I discovered to my horror that mine was not a supported configuration and there was no way in hell I would be getting back to where I started from. This happened on the 20th November. I finally managed to boot my system again on the 20th December. After failing to re-enable RAID I broke my system into individual root and /User partitions on separate drives (or tried to) and discovered that APFS (Encrypted) and /etc/fstab don’t get along. I re-defined my home folder to be on the second drive but cannot log in until I’ve logged into a utility account and mounted the encrypted partition separately. Currently permissions are so fucked up I can’t even stream music from iTunes. On Monday I’m gonna nuke it again and try another route from scratch.

Throughout this Apple Support has been anything but (aborting when for some reason my Mini’s S/N failed to match their records for Server machines, and thus bailing on me on the premise that I shouldn’t have RAID anyway so basically screw me.)


I've felt for a long time that Apple have lost interest in their end-user computers. MacOS Server has long seemed like 'if you REALLY want it, here, have fun'. But the tools tended to work. SoftRAID somehow works fine on Windows, why not on Mac.

Can't imagine how much pain you've been through with this. Got enough backups to revert back to Sierra?


And to think that ZFS for FreeBSD had already been up and running for years...


Not on 1B devices.


Maybe not on 1 billion devices, but ZFS was running on mission-critical Sun/Oracle hardware with expensive support contracts for many years. ZFS is currently probably the most reliable modern filesystem.

Still, rolling out APFS on such a large number of iDevices/Macs is a very impressive feat (although APFS is, of course, a simpler filesystem). The problems are with many of the 'edge cases' (RAID, etc.). This is not really surprising, btrfs has been in development since 2007 and still has problems with more complex setups.


Secret hint: if it's an older mac, try the NVIDIA Web Driver for the video driver.


It's a 2017 MBP with touchbar (and a Radeon GPU).


Rendering glitches when in Chrome are awful indeed and happen way too often


APFS. That's the big addition. I've had a few horrific problems with High Sierra, two of them leading me to do full disk wipes. My current problem is this odd occasional screen scrambling bug, that happens for a split second a couple times a day. Could it be related to the random colors that show up sometimes when I wake my MBP from sleep? I have no idea.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: