Understanding just what user profiles are, and how they interact with the Windows registry system is key to keeping a secure system. Making sure that your programs store settings in the user-specific settings trees, rather than the program directory, will help keep passwords and other vital information secure.
.NET Windows Security: Understanding User Profiles
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Which is exactly what Unix systems have been doing better and more simply for years.
User profiles get more fun when you’re part of a domain.
Just because many Windows developers didn’t take care of user profiles – it doesn’t mean that they’re not there.
In fact Windows profiles are much more sophisticated in a domain environment – because you can exactly define which subdirectories of the user home directory are going to be server-located or not. Under Unix, every subfolder HAS in fact to be mounted via NFS or SAMBA or it is local – there’s nothing in between …
Unix user administration is extremely flexible and capable. I’m not exactly sure what it is you think can be done under windows that is impossible under Unix w.r.t. users home directories.
Ever deal with roaming profiles in a Windows environment? I didn’t think so…it sucks ass big time.
Unix user administration is extremely flexible and capable. I’m not exactly sure what it is you think can be done under windows that is impossible under Unix w.r.t. users home directories.
Folder Redirection is one thing that springs instantly to mind (no, NFS mounting home directories is not the same thing).