We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://github.com/rapid7/ruby_smb/blob/master/lib/ruby_smb/fscc/file_information/file_name_information.rb#L5 contains a link to https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/cb30e415-54c5-4483-a346-822ea90e1e89 however it seems like MS removed the definition of the fields here so the only way to review this information now is to download the specs file from https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/efbfe127-73ad-4140-9967-ec6500e66d5e.
It may be worthwhile considering if we want to update the link accordingly.
The text was updated successfully, but these errors were encountered:
Actually this should link to https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/20406fb1-605f-4629-ba9a-c67ee25f23d2 I stand corrected, which defines this structure. It appears the link was to the wrong definition and someone searched for FILENAMEINFORMATION vs FILE_NAME_INFORMATION and therefore got the wrong definition.
Sorry, something went wrong.
No branches or pull requests
https://github.com/rapid7/ruby_smb/blob/master/lib/ruby_smb/fscc/file_information/file_name_information.rb#L5 contains a link to https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/cb30e415-54c5-4483-a346-822ea90e1e89 however it seems like MS removed the definition of the fields here so the only way to review this information now is to download the specs file from https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/efbfe127-73ad-4140-9967-ec6500e66d5e.
It may be worthwhile considering if we want to update the link accordingly.
The text was updated successfully, but these errors were encountered: