Page History

...

I can see anyone’s files within our file share, such all directories here:

\\files.cornell.edu\as\chm\Users

I’m using my basic <oh10> account to log in (the only one I’m paying for within CIT’s VDI service); nothing special.

We have verified that permissions on those the above directories are correct.. Indeed, on any other Windows computer, permissions are respected. Thus I suspect the CIT VDI instance is giving me elevated privileges to my account in an unintended way.

More details: I just tested more directories and I can seem to see into any directory below <\as\chm\> AND everywhere below <\as\PHY\>. However, one level above those <\as\>, I was not able to get to other directories I tested at that level, FWIW.

To clarify: My basic <oh10> AD account should not get broad access to either of the Chm or Phy levels, even though my IT group supports both Chemistry and Physics. And I confirmed I cannot get access to them when using my <oh10> account from within other Windows systems, other than CIT’s VDI.

In this case, my directories are on a file server provisioned by A&S IT, a service used to support A&S staff and admin-related services.

Why I think this is critical: We need to trust file shares will This is "not good". We want to trust file shares to respect the permissions set on directories and files and thus are capable of holding data which is designated NOT to be shared. When that trust is compromised the value of the file share service is severely compromised. This can lead staff to find alternative locations for data (such as performance reviews and salaries), perhaps using places not very "good" from an institutional perspective, even as they may nominally seem to meet the a staff member's own needs. Please fix!
In this case, my directories are on a file server provisioned by A&S IT, a service used to support A&S staff and admin-related services.

CU View blocked (

...

Java plug-in)

Pertains to all of the campus's views:

...