this module may violate the Drupal license

hmmm interesting. Drupal vB rides a very fine line there and it *might* pass as legal. But my module Drupaltin on the other hand won't for sure. Kinda sucks but what can you do....

Thanks for the post.

DrupalVB only includes config.php from Vbulletin which simply contains a set of arrays (data). Vbulletin could simply solve this by declaring that file to be public domain, and not proprietary. Thus Vbulletin, Drupal, and anyone else can access and run against the code contained in that file.

In any case, I think that since config.php is pure data, and is user supplied data (your own database password, setup, memcached info, etc.) that it cannot be covered under copywrite.
The only thing copywrite protected would be the commented *shrug*.

This issue will be fixed in 5.x-2.x, which only accesses vBulletin's data in the database, but does not include code. Thanks, Peter, without this notice I would not have recognized and solved this problem during the 2.x re-write.