Announcement

Collapse
No announcement yet.

How to lock/hide a private folder

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    Originally posted by Buddlespit View Post
    Does he really want to sudo that chmod?
    Within his own home directory, no problem. chmod requires sudo IF used on folders/files not owned by the user.

    If one is unsure of this, try it on a selected folder or file only, then log out and log in as another user and see if you can view the folder/files so changed.
    Last edited by Snowhog; Oct 02, 2013, 05:20 PM. Reason: Clarification.
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #32
      or you could just open dolphin and go to / (root) then /home>right click your /home/you(where "you" is your user name) folder>click properties>click the permissions tab and under "others" change to "forbidden" no need for kdesudo YOU own it .

      VINNY
      i7 4core HT 8MB L3 2.9GHz
      16GB RAM
      Nvidia GTX 860M 4GB RAM 1152 cuda cores

      Comment


        #33
        Originally posted by Snowhog View Post
        chmod requires sudo.
        It does when the user running chmod is not the owner of the file(s), otherwise it doesn't

        Originally posted by Snowhog View Post
        Code:
        sudo chmod -R go-rw user:user *
        I'm fairly sure that doesn't work...last I checked chmod can't change ownerships (only permissions), you need 'chown' to change ownerships

        Comment


          #34
          Originally posted by kubicle View Post
          It does when the user running chmod is not the owner of the file(s), otherwise it doesn't


          I'm fairly sure that doesn't work...last I checked chmod can't change ownerships (only permissions), you need 'chown' to change ownerships
          Corrected. Thank you.
          Windows no longer obstructs my view.
          Using Kubuntu Linux since March 23, 2007.
          "It is a capital mistake to theorize before one has data." - Sherlock Holmes

          Comment


            #35
            Originally posted by Buddlespit View Post
            If you install lightdm by itself, it will install a ton of gtk stuff that you'll probably not want or need. So, I would recommend:
            Code:
            sudo apt-get install lightdm-kde-greeter
            which will just install what you need to get lightdm to work on a kde system (ie-Kubuntu). During the install of lightdm, it will ask you if you want to use lightdm as the default dm (or it will ask you to choose between available dm's, you'll want to choose lightdm). Then go back to system settings and configure lightdm to your tastes. Not a whole lot you can do with lightdm and guest account is enabled by default.



            I did it with this command + the reconfigure command and now I have the lightdm as a default display manager.

            One last question on that issue. When I installed the lightdm I got this message on the konsole
            "The following packages cannot be authenticated"
            and then this one
            "install these packages without verification"

            What does it mean ?

            Comment


              #36
              This thread is really helpful. I always want to find a good way to lock a folder. Thanks, really.

              Comment


                #37
                I'm coming in late on this thread, but I use GreyGeeks method of just saving the file to a flash drive, but I don't encrypt it. When not in use, just simply remove the flash drive. You can't get any simpler than that.

                Comment


                  #38
                  Originally posted by Detonate View Post
                  I'm coming in late on this thread, but I use GreyGeeks method of just saving the file to a flash drive, but I don't encrypt it. When not in use, just simply remove the flash drive. You can't get any simpler than that.
                  Seriously, just try my way with the encfs service menu for Dolphin. It's a infinitely more secure, and no risk of losing a flash drive, somebody using it by mistake or dying. Flash drives tend to die a lot more frequently than standard HDDs. Then again, our motto on these forums is, "Use what works for you."

                  Comment


                    #39
                    Originally posted by Teunis
                    I was thinking of an other simple system.
                    You'd need a little script that will split your data in the odd and even bits that will be stored on separate devices.
                    You can access the content only when both devices are present.
                    Not to sound condescending but why the f**k would you do that? It just seems computationally intensive and just perfect for something to go wrong. It's a really cool, and novel idea but it's just a bit weird. Seriously, there are so many easier, faster and more powerful solutions available. Encfs + service menu leaves you with a super easy to use, fast, and ultra secure encryption method to keep your data safe.

                    The only reason I could think to do your method would be split it and then encrypt the data. You could use it as a way for two party authentication i.e. two parties are needed to read the data while not trusting either party individually. Perfect way to stop a rogue employee stealing trade secrets, but you should always default to encryption to keep data safe above all else.

                    Comment


                      #40
                      Originally posted by dmeyer View Post
                      The only reason I could think to do your method would be split it and then encrypt the data. You could use it as a way for two party authentication i.e. two parties are needed to read the data while not trusting either party individually. Perfect way to stop a rogue employee stealing trade secrets, but you should always default to encryption to keep data safe above all else.
                      In a similar yet contrary vein... Why administrative passwords will never be like nuclear missile launchers.

                      Comment


                        #41
                        Originally posted by SteveRiley View Post
                        I most definitely agree but I have l prefer to not leave too much power in the hands of a single person. I think for the example I used the solution is actually very clever. Although a sys admin as stated in your article should be inherently trusted, you can always apply the idea that one sys admin is always untrusted, and two working together is trusted. It's a very good approach for highly sensitive things. I do believe though that it is way overkill for 90% of use cases but it would prevent things like http://www.thewhir.com/web-hosting-n...n-2700-servers to an extent. Division of duties and responsibilities is really important for a reason. I'm not saying the solution is always practical, more often than not, it isn't, but for highly sensitive stuff it should be used. Also, at someplaces I've been they have a sys admin who only really has privileges on the mail side, another only on some of the database backends. For small companies you are left with little flexibility but bigger organizations can most definitely afford the expense in exchange for enhanced security. As a whole though, your analysis of the situation is spot on but I do think that there to ere on the side of caution is always best.

                        Comment

                        Working...
                        X