Re: Symlinks for the Freelance root.afs volume
Jeffrey Altman <[email protected]>
| Newsgroups | gmane.comp.file-systems.openafs.devel.win32 |
|---|---|
| Organization | Mass |
| Message-ID | <[email protected]> |
Rodney M Dyer wrote: > At 11:36 AM 10/28/04, Jeffrey Altman wrote: > Strange, the filter isn't working too well. I have a desktop.ini file > in my home user volume root and Explorer picks it up just fine. I will > try it though. We filter it out at some levels. I am not sure exactly where. It might only affect top level cell volumes. I'm not sure. It might also only be a filter on the stat() calls. Again, I'm not sure. I don't care about it so I haven't looked at the code. You are welcome to do so. Search for desktop.ini. > Btw, I can't say I'm too happy about the certificates. This blows my > AFSLogonShell hack out of the water. Time to create my own provider > dll. Except with my own, there's no way for me to get a hold of the > SMBName if in high security mode. Ah well, win some, lose some. Back > to the drawing board. The point of the certificates is to enable those providing support to the AFS community knowledge of whether or not the code that is being used by an end user is in fact the code that was shipped from OpenAFS.org or whether it was a local and perhaps customized build. This is going to be especially important if/when I am able to gain access to the Microsoft Crash Report Database for the OpenAFS executables. I don't want to waste my time searching for the cause of crashes in binaries which I did not build. There is nothing in the use of certificates which prevents you from replacing a DLL with one of your own. It just means that when your DLL crashes I will ignore it. Jeffrey Altman
smime.p7s
(application/x-pkcs7-signature, 3.2 KB) - not displayed