...

...

@@ -114,7 +114,7 @@ __HALT_COMPILER();

114

114

<entry>Whole-archive signature validation</entry>

115

115

<entry>Yes</entry>

116

116

<entry>Yes</entry>

117

-

<entry>Yes (PHP 5.3.1+)</entry>

117

+

<entry>Yes</entry>

118

118

</row>

119

119

<row>

120

120

<entry>Web-specific application support</entry>

...

...

@@ -202,6 +202,13 @@ __HALT_COMPILER();

202

202

gzip or bzip2 format and still be executed by the Phar extension.

203

203

</para>

204

204

<para>

205

+

There is limited support for reading tarballs in pax interchange format,

206

+

but all recognized pax headers (currently, typeflag <literal>x</literal> and

207

+

<literal>g</literal>) are silently ignored.

208

+

There is also limited support for GNU Tar Archives;

209

+

currently, <literal>././@LongLink</literal> headers are resolved.

210

+

</para>

211

+

<para>

205

212

To compress an entire archive, use <function>Phar::compress</function>.

206

213

To decompress an entire archive, use <function>Phar::decompress</function>.

207

214

</para>

...

...

@@ -213,7 +220,7 @@ __HALT_COMPILER();

213

220

the zip file format. Per-file and whole-archive metadata is stored in

214

221

the zip file comment and zip archive comment as a serialized string. Pre-existing

215

222

zip comments will be successfully read as a string. Per-file compression

216

-

read/write is supported with zlib compression, and read access is supported

223

+

read/write is supported with zlib DEFLATE compression, and read access is supported

217

224

with bzip2 compression. There is no limit on the number of files

218

225

within a zip-based phar archive. Empty directories are stored in the zip archive

219

226

as files with a trailing slash like <literal>my/directory/</literal>

...

...

@@ -318,14 +325,14 @@ __HALT_COMPILER();

318

325

<entry><literal>0x00001000</literal></entry>

319

326

<entry>

320

327

If set, this Phar contains at least 1 file that

321

-

is compressed with zlib compression

328

+

is compressed with zlib DEFLATE compression

322

329

</entry>

323

330

</row>

324

331

<row>

325

332

<entry><literal>0x00002000</literal></entry>

326

333

<entry>

327

334

If set, this Phar contains at least 1 file that

328

-

is compressed with bzip compression

335

+

is compressed with bzip2 compression

329

336

</entry>

330

337

</row>

331

338

</tbody>

...

...

@@ -418,13 +425,13 @@ __HALT_COMPILER();

418

425

<row>

419

426

<entry><literal>0x00001000</literal></entry>

420

427

<entry>

421

-

If set, this file is compressed with zlib compression

428

+

If set, this file is compressed with zlib DEFLATE compression

422

429

</entry>

423

430

</row>

424

431

<row>

425

432

<entry><literal>0x00002000</literal></entry>

426

433

<entry>

427

-

If set, this file is compressed with bzip compression

434

+

If set, this file is compressed with bzip2 compression

428

435

</entry>

429

436

</row>

430

437

</tbody>

...

...

@@ -437,7 +444,8 @@ __HALT_COMPILER();

437

444

<para>

438

445

Phars containing a signature always have the signature appended to the

439

446

end of the Phar archive after the loader, manifest, and file contents.

440

-

The two signature formats supported at this time are MD5 and SHA1.

447

+

The signature formats supported at this time are MD5, SHA1, SHA256, SHA512,

448

+

and OPENSSL.

441

449

</para>

442

450

<para>

443

451

<table>

...

...

@@ -451,11 +459,12 @@ __HALT_COMPILER();

451

459

</thead>

452

460

<tbody>

453

461

<row>

454

-

<entry>16 or 20 bytes</entry>

462

+

<entry>varying</entry>

455

463

<entry>

456

464

The actual signature, 20 bytes for an SHA1 signature,

457

465

16 bytes for an MD5 signature, 32 bytes for an SHA256 signature,

458

-

and 64 bytes for an SHA512 signature.

466

+

and 64 bytes for an SHA512 signature. The length of an OPENSSL

467

+

signature depends on the size of the private key.

459

468

</entry>

460

469

</row>

461

470

<row>

...

...

@@ -463,10 +472,12 @@ __HALT_COMPILER();

463

472

<entry>

464

473

Signature flags. <literal>0x0001</literal> is used to

465

474

define an MD5 signature, <literal>0x0002</literal> is used

466

-

to define an SHA1 signature, <literal>0x0004</literal> is used

467

-

to define an SHA256 signature, and <literal>0x0008</literal> is

475

+

to define an SHA1 signature, <literal>0x0003</literal> is used

476

+

to define an SHA256 signature, and <literal>0x0004</literal> is

468

477

used to define an SHA512 signature. The SHA256 and SHA512 signature

469

-

support was introduced with API version 1.1.0.

478

+

support is available as of API version 1.1.0.

479

+

<literal>0x0010</literal> is used to define an OPENSSL signature, what

480

+

is available as of API version 1.1.1, if OpenSSL is available.

470

481

</entry>

471

482

</row>

472

483

<row>

473

484