Add option to disallow symlinks about archive_tar

[mrook]

Good idea, I'll add that.

[mrook]

Yeah that sounds good to me, a PR is appreciated!

[mortenson]

@mrook Thanks! Just filed #27

[mrook]

Merged the PR - I'll make sure to tag a new release later this week.

[mortenson]

@mrook Thank you!

[mrook]

https://github.com/pear/Archive_Tar/releases/tag/1.4.9

[klausi]

The Drupal security advisory is saying that Archive_Tar had a security release: https://www.drupal.org/sa-core-2019-012

But that is not the case I think? Symbolic links are still processed by default, so users are still in danger if they use this library the same way. Should the release notes warn users to change their library usage?

[mortenson]

@klausi I'm not sure if you mean the Drupal release notes or the Archive_Tar release notes - but for Drupal, core code that wraps Archive_Tar was updated to disallow symlinks. Drupal is not responsible for how users use third party dependencies directly.

I think it was incorrect for the SA to say that the Archive_Tar release was "security update" - allowing symlinks is a feature of Archive_Tar and not a security flaw, so the update really added an optional security enhancement for applications that do not want to support symlinks.

[klausi]

I mean the Drupal release notes which say "The Drupal project uses the third-party library Archive_Tar, which has released a security update that impacts some Drupal configurations."

But Archive_Tar did not mention that this is a security update in the release notes at https://pear.php.net/package/Archive_Tar/download/1.4.9

Allowing symlinks is a very dangerous feature for anybody that uses Archive_Tar on attacker supplied archive files.

[mortenson]

@klausi It was not a security update of Archive_Tar, it was an optional security feature addition. I agree that the release notes could have told people who untar untrusted data to use the new flag, however. Not sure if that's possible retroactively.

[greggles]

I've updated the Drupal security advisory page to try to clarify what happened.

I think it could be a good idea for the Archive_Tar library to add some help text about being cautious in enabling symlinks for user-generated content.