This is a Windows 2003 server. On Fri, Mar 2, 2012 at 5:43 PM, Axel Luttgens <[email protected]> wrote:
> Le 2 mars 2012 à 20:07, Chris Murphy a écrit : > > > > > On Mar 2, 2012, at 12:04 PM, Markus Hitter wrote: > > > >> > >> Am 01.03.2012 um 01:25 schrieb Chris Murphy: > >> > >>> And while I'm no fan of Microsoft, this seems like it constitutes a > major exploit. Like a design level flaw that isn't easy to fix server side > or they probably would have done it by now. > >> > >> Before doing such claims you should perhaps ask how the server is > configured, first. Every server can be set up in a wide open way, allowing > everything for everybody. > > > > It is not a claim. It is called a supposition, and my word selection > "seems like" does establish such. > > > > And this has been a supposition of mine throughout, if you've kept track > of the whole thread. But Susan has since said she called Apple support, > described the problem, and they appear to be asserting this as a known > problem. > > > > And also the previous behavior indicates the server was setup expressly > in a way contrary to how you describe, and past versions of OS X honored > this configuration. But now by merely changing clients, this information is > being exposed. > > Well, having read the whole thread, I noticed Susan has spoken about a > "general Windows server volume" and a "Windows volume", but never specified > whether the share is provided by a Mac OS X server or a Windows server. > > Perhaps would it be nice to have some additional info before going further? > > Axel > > > _______________________________________________ > MacOSX-admin mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/macosx-admin > -- Susan Alston Internet Developer/Blackboard Administrator 110 McSweeney Chowan University 252-398-6263 _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
