updating public copies of the sdk

I've been examining the sdk and the eula is more detail and am wondering if it's possible for there to be a public update of the sdk with this method.

- ContributorA goes to blackmagicdesign.com, clicks on the SDK, submits their name and contact info as required, reviews and agrees to the EULA, and then selects `Register & Download`.

- ContributorA then gets to the download page which contains a temporary download link (this contains a Key-Pair-Id and a long base64 Signature value and an Expiration timestamp). Here ContributorA does not download the SDK but only copies the URL and shares the URL with ContributorB.

- ContributorB accesses the URL to download the SDK. ContributorB has not reviewed nor agreed to the EULA and is thus not agreeing to
> The Licensee must not lease, rent, distribute or sub-license the Software, or use the Software in a time-sharing arrangement, or in any other manner that is not the Permitted Use.

- ContributorB unpacks the SDK and reviews the header license of the SDK files which permit distribution and has a common open source boilerplate in the header.

I am not well versed in associated law/ethics with such EULA, but in the above scenario ContributorA is agreeing to a EULA that applies to the SDK itself and not a temporary URL of the SDK, while the scenario of ContributorB accessing is in a scenario that doesn't include the EULA but they are subject to respect the license within the SDK which unlike the EULA permits sharing.

???