1. 1
    akama avatar akama 1 year ago | link | on: Security Design: Stop Trying to Fix the User

    I’m going to only focus on one point here which is the aspect of passwords/logins. One of the wonderful things about corporate environments is there desire to focus on single sign on solutions. It would be wonderful if someone was working to take that to the internet as a whole. This is actually one of the reasons I was so excited for Mozilla’s Persona which seems like an ideal solution in a number of ways but with some obvious downsides as well. One of the most important issues facing the internet is decentralized identity. Large technology companies are already trying to own this space. This identity should carry between websites and a user should be able to have multiple ones for privacy and security reasons. Security would be far better off if we made users only remember a couple passwords for an identity and then used those identities to login into services rather than insisting that we create an account for every service.

    1. 2
      akama avatar akama 3 years ago | link | on: Clicking "About This Mac" in Yosemite sends identifying information to Apple

      I don’t really get the usage for sending back this event to Apple. What could they possibly be learning from this?

      1. 2
        akama avatar akama 3 years ago | link | on: Is Docker ready for production? Feedbacks of a 2 weeks hands on

        One of the biggest limitations of Docker that I haven’t seen solved yet is how to run databases. Do you mount a file system folder and store the database there? Then you have issues with multiple databases hosts and persistence. Does this mean that you are supposed to put the database on an ordinary host and just connect to it from the webapp containers? Now you have two different types of things to manage.

        Mind you, I don’t have a ton of experience with Docker. I’ve just used it for some personal projects, but this seems like something that should be solved.

        1. 3
          silky avatar silky 3 years ago | link

          infact the normal way to manage databases is locating them on a different server from your app servers, and then connecting to them in that fashion.

          it works out nicely, often, because they are in the same network as you; so access is fast, and they don’t need to be accessible externally (aside from management). so if you simply using docker for app deployment, it shouldn’t affect how you manage your dbs.

          1. 2
            mattgreenrocks avatar mattgreenrocks 3 years ago | link

            For small apps, you can mount a local filesystem within a container running, say, Postgres. You’re encouraged to do this because storing things in a container is a bad idea. See the guide for more details.

            Docker also has mechanisms to provide DNS-like names to other containers in an easy fashion.

          1. 1
            akama avatar akama 4 years ago | link | on: Top 7 Alternatives for Ubuntu One Cloud Storage

            BitSync is the most promising of these, but I am still very disappointed that the code is not open source. This was a huge mistake and has stunted the growth by a considerable amount. An open source code base could have seen a huge amount of adoption in the form of standalone apps and platforms/apps that were built on top of it.