Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

If you join a Homegroup from a Windows 8 machine, you are prompted for a password. This password is subsequently visible whenever you enter the homegroup settings:

enter image description here This is silly. Is there a way to obscure it?

share|improve this question

1 Answer 1

up vote 6 down vote accepted

At current, No.

The prevailing logic for Homegroups is that it's a Leaderless system, meaning that all members have all applicable rights over shared resources (unless specifically defined by the file/directory's original owner).

Since the Homegroup password is considered owned by no one (there is no Homegroup Administrators group like there is on a Domain) then all members of the Homegroup have full access to that information and the password is reference-able at any time un-obscured.

Maybe in the future, as Homegroups become more and more adopted in the general public, more robust securities will be implemented. But as it stands now, that password is considered public knowledge for all members of a Homegroup.

share|improve this answer
    
+1 Good summary/insight of the reasoning. –  George Duckett Oct 23 '12 at 12:43
3  
It was visible in Win7 as well. –  Karan Oct 23 '12 at 12:43
    
Thank you Karan, Yes, this is a limitation in the way Homegroups are designed and its not OS specific.. –  Jared Tritsch Oct 23 '12 at 12:44
    
I didn't notice in W7, but the reasoning is flawed in my opinion. Just because all members are equal doesn't mean that the password should not be protected from onlookers who are not members - the password is public to members and everyone else in the vicinity as it stands. This isn't the place for this discussion however. –  Paul Oct 23 '12 at 12:50
    
This is a problem. For just that reason, Paul. But this is the logic as to why things are the way they are. They could easily put a "show me the password" button but they didn't, and likely because it simply didn't occur to the developers who were not thinking along those lines. THey were coming from a "sharing is caring" paradigm and not thinking in terms of security. This will probably be fixed eventually as I have seen this issue floating around the MSDN forum the last couple years. –  Jared Tritsch Oct 23 '12 at 12:54

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.