Skip to content

Resolved Issues

  • #34: Normalize resolved Windows path to Unix-style
  • #42: Avoid analysing non-phar files on alias resolving
  • #40: Add Windows tests using AppVeyor
  • #33: Add alternative mime-type resolving (without ext-fileinfo)
Assets 2

Resolved Issues

  • #34: Normalize resolved Windows path to Unix-style
  • #42: Avoid analysing non-phar files on alias resolving
  • #40: Add Windows tests using AppVeyor
  • #33: Add alternative mime-type resolving (without ext-fileinfo)
Assets 2

@ohader ohader released this May 6, 2019 · 14 commits to master since this release

Releases v3.1.1 and v.2.1.1 aim to overcome drawbacks in Phar's alias resolving from Phar stub as well as solving performance aspects.

Resolved Issues

  • alias resolving & handling #21, #24
  • performance #23
Assets 2

@ohader ohader released this May 6, 2019 · 9 commits to v2 since this release

Releases v3.1.1 and v.2.1.1 aim to overcome drawbacks in Phar's alias resolving from Phar stub as well as solving performance aspects.

Resolved Issues

  • alias resolving & handling #21, #24
  • performance #23
Assets 2
Pre-release

@ohader ohader released this Mar 4, 2019 · 22 commits to master since this release

Description

Releases v3.1.0 and v.2.1.0 aim to overcome drawbacks in Phar's alias resolving (either by Phar archives using Phar::setAlias() in meta-data or Phar::mapPhar() in stub code).

Merged pull-requests

Migration

In case custom Assertable interceptors have been used, path resolving has to be adjusted in order to make use of alias resolving features.

before - example in v3.0.1

$baseFile = Helper::determineBaseFile($path);

after - example in v3.1.0

$invocation = Manager::instance()->resolve($path);
$baseName = $invocation->getBaseName(); // previously called $baseFile

Open Issues

There have been reports about flaws using stream_select() and according stream_cast() in PharStreamWrapper. Since it was not possible to reproduce the behavior in an isolated scenario and specific platform requiresments were not clear, these aspects have not been covered by these releses - see #8 and #19 for details.

Features

  • added low-level Phar\Reader for stub & meta-data (incl. alias) and their model representations
  • added Resolver\PharInvocationResolver in order to resolve/handle alias names
  • added Interceptor\ConjunctionInterceptor for combining multiple interceptors
  • added Interceptor\PharMetaDataInterceptor for actually testing against insecure deserialization in meta-data of Phar archives
Assets 2
Pre-release
Pre-release

@ohader ohader released this Mar 4, 2019 · 14 commits to v2 since this release

Description

Releases v3.1.0 and v.2.1.0 aim to overcome drawbacks in Phar's alias resolving (either by Phar archives using Phar::setAlias() in meta-data or Phar::mapPhar() in stub code).

Merged pull-requests

Migration

In case custom Assertable interceptors have been used, path resolving has to be adjusted in order to make use of alias resolving features.

before - example in v3.0.1

$baseFile = Helper::determineBaseFile($path);

after - example in v3.1.0

$invocation = Manager::instance()->resolve($path);
$baseName = $invocation->getBaseName(); // previously called $baseFile

Open Issues

There have been reports about flaws using stream_select() and according stream_cast() in PharStreamWrapper. Since it was not possible to reproduce the behavior in an isolated scenario and specific platform requiresments were not clear, these aspects have not been covered by these releses - see #8 and #19 for details.

Features

  • added low-level Phar\Reader for stub & meta-data (incl. alias) and their model representations
  • added Resolver\PharInvocationResolver in order to resolve/handle alias names
  • added Interceptor\ConjunctionInterceptor for combining multiple interceptors
  • added Interceptor\PharMetaDataInterceptor for actually testing against insecure deserialization in meta-data of Phar archives
Assets 2
Mar 1, 2019
Merge pull request #20 from TYPO3/task/v2-backports
[TASK] Backport Phar alias changes

@ohader ohader released this Sep 7, 2018 · 74 commits to master since this release

Basically no functional differences to v1.0.1 release. Since PHP 5.3 compatibility has been merged into this repository, the new v2 branch will be used for PHP 5.3 related sources and master still requires PHP 7.0. That's why v1.0.1 is re-released now as v3.0.0.

Assets 2
You can’t perform that action at this time.