Getting "replacing registered class" warning from bindata

[md5]

I'm looking at possibly using ruby_smb for a project and after adding it to my Gemfile and loading it up, I'm seeing a bunch of warnings like the following:

warning: replacing registered class RubySMB::SMB2::BitField::DirectoryAccessMask with RubySMB::SMB1::BitField::DirectoryAccessMask
warning: replacing registered class RubySMB::SMB2::BitField::FileAccessMask with RubySMB::SMB1::BitField::FileAccessMask
warning: replacing registered class RubySMB::SMB2::Packet::NegotiateRequest with RubySMB::SMB1::Packet::NegotiateRequest
warning: replacing registered class RubySMB::SMB1::DataBlock with RubySMB::SMB1::Packet::NegotiateRequest::DataBlock
warning: replacing registered class RubySMB::SMB2::Packet::NegotiateResponse with RubySMB::SMB1::Packet::NegotiateResponse

It repeats like that for 111 colliding class names.

Based on the discussion in dmendel/bindata#157, it seems like perhaps using their namespacing feature would remove these warnings. They even point to another rapid7 repo as an example of using the feature:

• https://github.com/rapid7/metasploit-framework/blob/master/lib/rex/proto/amqp/version_0_9_1/types.rb
• https://github.com/rapid7/metasploit-framework/blob/master/lib/rex/proto/amqp/version_0_9_1/frames/method_arguments.rb

I do see one use of search_prefix in this project, but it also seems that these class names are basically part of the public API since some of them are mentioned in README.md, so maybe they can't be namespaced to avoid these warnings without being a breaking change for users.

If the warnings can be safely ignored, it would be ideal if they were not shown every time I load up this gem (e.g. by ruby_smb wrapping the part of the code that triggers the warnings with Kernel.silence_warnings).

[md5]

Looks like I was somehow using ruby_smb version 3.3.2 instead of the latest 3.3.16. When I updated to the current version I no longer saw the warnings. I see that you pinned the version of bindata to 2.4.15 in 487977c, which may be why I no longer see the warnings that I saw when bindata-2.5.1 was in use, but I suspect they will crop up when/if you remove that version pinning.

Leaving the issue open since I think it's only not happening because of that version pin, but go ahead and close if that's better for y'all. At least now somebody searching for the error message I came across should find this issue.