panda3d.core.Multifile

class Multifile

Bases: ReferenceCount

A file that contains a set of files.

Inheritance diagram

Inheritance diagram of Multifile

__init__() → None
openRead(multifile_name: Filename, offset: streamoff) → bool

Opens the named Multifile on disk for reading. The Multifile index is read in, and the list of subfiles becomes available; individual subfiles may then be extracted or read, but the list of subfiles may not be modified.

Also see the version of openRead() which accepts an istream. Returns true on success, false on failure.

openRead(multifile_stream: IStreamWrapper, owns_pointer: bool, offset: streamoff) → bool

Opens an anonymous Multifile for reading using an istream. There must be seek functionality via seekg() and tellg() on the istream.

If owns_pointer is true, then the Multifile assumes ownership of the stream pointer and will delete it when the multifile is closed, including if this function returns false.

openWrite(multifile_name: Filename) → bool

Opens the named Multifile on disk for writing. If there already exists a file by that name, it is truncated. The Multifile is then prepared for accepting a brand new set of subfiles, which will be written to the indicated filename. Individual subfiles may not be extracted or read.

Also see the version of openWrite() which accepts an ostream. Returns true on success, false on failure.

openWrite(multifile_stream: ostream, owns_pointer: bool) → bool

Opens an anonymous Multifile for writing using an ostream. There must be seek functionality via seekp() and tellp() on the pstream.

If owns_pointer is true, then the Multifile assumes ownership of the stream pointer and will delete it when the multifile is closed, including if this function returns false.

openReadWrite(multifile_name: Filename) → bool

Opens the named Multifile on disk for reading and writing. If there already exists a file by that name, its index is read. Subfiles may be added or removed, and the resulting changes will be written to the named file.

Also see the version of openReadWrite() which accepts an iostream. Returns true on success, false on failure.

openReadWrite(multifile_stream: iostream, owns_pointer: bool) → bool

Opens an anonymous Multifile for reading and writing using an iostream. There must be seek functionality via seekg()/seekp() and tellg()/tellp() on the iostream.

If owns_pointer is true, then the Multifile assumes ownership of the stream pointer and will delete it when the multifile is closed, including if this function returns false.

close() → None

Closes the Multifile if it is open. All changes are flushed to disk, and the file becomes invalid for further operations until the next call to open().

getMultifileName() → Filename

Returns the filename of the Multifile, if it is available.

Return type

Filename

setMultifileName(multifile_name: Filename) → None

Replaces the filename of the Multifile. This is primarily used for documentation purposes only; changing this name does not open the indicated file. See openRead() or openWrite() for that.

isReadValid() → bool

Returns true if the Multifile has been opened for read mode and there have been no errors, and individual Subfile contents may be extracted.

isWriteValid() → bool

Returns true if the Multifile has been opened for write mode and there have been no errors, and Subfiles may be added or removed from the Multifile.

needsRepack() → bool

Returns true if the Multifile index is suboptimal and should be repacked. Call repack() to achieve this.

getTimestamp() → time_t

Returns the modification timestamp of the overall Multifile. This indicates the most recent date at which subfiles were added or removed from the Multifile. Note that it is logically possible for an individual subfile to have a more recent timestamp than the overall timestamp.

Return type

time_t

setRecordTimestamp(record_timestamp: bool) → None

Sets the flag indicating whether timestamps should be recorded within the Multifile or not. The default is true, indicating the Multifile will record timestamps for the overall file and also for each subfile.

If this is false, the Multifile will not record timestamps internally. In this case, the return value from getTimestamp() or getSubfileTimestamp() will be estimations.

You may want to set this false to minimize the bitwise difference between independently-generated Multifiles.

getRecordTimestamp() → bool

Returns the flag indicating whether timestamps should be recorded within the Multifile or not. See setRecordTimestamp().

setScaleFactor(scale_factor: size_t) → None

Changes the internal scale factor for this Multifile.

This is normally 1, but it may be set to any arbitrary value (greater than zero) to support Multifile archives that exceed 4GB, if necessary. (Individual subfiles may still not exceed 4GB.)

All addresses within the file are rounded up to the next multiple of _scale_factor, and zeros are written to the file to fill the resulting gaps. Then the address is divided by _scale_factor and written out as a 32-bit integer. Thus, setting a scale factor of 2 supports up to 8GB files, 3 supports 12GB files, etc.

Calling this function on an already-existing Multifile will have no immediate effect until a future call to repack() or close() (or until the Multifile is destructed).

getScaleFactor() → size_t

Returns the internal scale factor for this Multifile. See setScaleFactor().

Return type

size_t

setEncryptionFlag(flag: bool) → None

Sets the flag indicating whether subsequently-added subfiles should be encrypted before writing them to the multifile. If true, subfiles will be encrypted; if false (the default), they will be written without encryption.

When true, subfiles will be encrypted with the password specified by setEncryptionPassword(). It is possible to apply a different password to different files, but the resulting file can’t be mounted via VFS.

getEncryptionFlag() → bool

Returns the flag indicating whether subsequently-added subfiles should be encrypted before writing them to the multifile. See setEncryptionFlag().

setEncryptionPassword(encryption_password: str) → None

Specifies the password that will be used to encrypt subfiles subsequently added to the multifile, if the encryption flag is also set true (see setEncryptionFlag()).

It is possible to apply a different password to different files, but the resulting file can’t be mounted via VFS. Changing this value may cause an implicit call to flush().

getEncryptionPassword() → str

Returns the password that will be used to encrypt subfiles subsequently added to the multifile. See setEncryptionPassword().

setEncryptionAlgorithm(encryption_algorithm: str) → None

Specifies the encryption algorithm that should be used for future calls to addSubfile(). The default is whatever is specified by the encryption- algorithm config variable. The complete set of available algorithms is defined by the current version of OpenSSL.

If an invalid algorithm is specified, there is no immediate error return code, but flush() will fail and the file will be invalid.

It is possible to apply a different encryption algorithm to different files, and unlike the password, this does not interfere with mounting the multifile via VFS. Changing this value may cause an implicit call to flush().

getEncryptionAlgorithm() → str

Returns the encryption algorithm that was specified by setEncryptionAlgorithm().

setEncryptionKeyLength(encryption_key_length: int) → None

Specifies the length of the key, in bits, that should be used to encrypt the stream in future calls to addSubfile(). The default is whatever is specified by the encryption-key-length config variable.

If an invalid key_length for the chosen algorithm is specified, there is no immediate error return code, but flush() will fail and the file will be invalid.

It is possible to apply a different key length to different files, and unlike the password, this does not interfere with mounting the multifile via VFS. Changing this value may cause an implicit call to flush().

getEncryptionKeyLength() → int

Returns the encryption key length, in bits, that was specified by setEncryptionKeyLength().

setEncryptionIterationCount(encryption_iteration_count: int) → None

Specifies the number of times to repeatedly hash the key before writing it to the stream in future calls to addSubfile(). Its purpose is to make it computationally more expensive for an attacker to search the key space exhaustively. This should be a multiple of 1,000 and should not exceed about 65 million; the value 0 indicates just one application of the hashing algorithm.

The default is whatever is specified by the multifile-encryption-iteration- count config variable.

It is possible to apply a different iteration count to different files, and unlike the password, this does not interfere with mounting the multifile via VFS. Changing this value causes an implicit call to flush().

getEncryptionIterationCount() → int

Returns the value that was specified by setEncryptionIterationCount().

addSubfile(subfile_name: str, filename: Filename, compression_level: int) → str

Adds a file on disk as a subfile to the Multifile. The file named by filename will be read and added to the Multifile at the next call to flush(). If there already exists a subfile with the indicated name, it is replaced without examining its contents (but see also update_subfile).

Either Filename:::set_binary() or set_text() must have been called previously to specify the nature of the source file. If set_text() was called, the text flag will be set on the subfile.

Returns the subfile name on success (it might have been modified slightly), or empty string on failure.

addSubfile(subfile_name: str, subfile_data: istream, compression_level: int) → str

Adds a file from a stream as a subfile to the Multifile. The indicated istream will be read and its contents added to the Multifile at the next call to flush(). The file will be added as a binary subfile.

Note that the istream must remain untouched and unused by any other code until flush() is called. At that time, the Multifile will read the entire contents of the istream from the current file position to the end of the file. Subsequently, the Multifile will not close or delete the istream. It is the caller’s responsibility to ensure that the istream pointer does not destruct during the lifetime of the Multifile.

Returns the subfile name on success (it might have been modified slightly), or empty string on failure.

updateSubfile(subfile_name: str, filename: Filename, compression_level: int) → str

Adds a file on disk to the subfile. If a subfile already exists with the same name, its contents are compared byte-for-byte to the disk file, and it is replaced only if it is different; otherwise, the multifile is left unchanged.

Either Filename:::set_binary() or set_text() must have been called previously to specify the nature of the source file. If set_text() was called, the text flag will be set on the subfile.

addSignature(certificate: Filename, chain: Filename, pkey: Filename, password: str) → bool

Adds a new signature to the Multifile. This signature associates the indicated certificate with the current contents of the Multifile. When the Multifile is read later, the signature will still be present only if the Multifile is unchanged; any subsequent changes to the Multifile will automatically invalidate and remove the signature.

The chain filename may be empty if the certificate does not require an authenticating certificate chain (e.g. because it is self-signed).

The specified private key must match the certificate, and the Multifile must be open in read-write mode. The private key is only used for generating the signature; it is not written to the Multifile and cannot be retrieved from the Multifile later. (However, the certificate can be retrieved from the Multifile later, to identify the entity that created the signature.)

This implicitly causes a repack() operation if one is needed. Returns true on success, false on failure.

This flavor of addSignature() reads the certificate and private key from a PEM-formatted file, for instance as generated by the openssl command. If the private key file is password-encrypted, the third parameter will be used as the password to decrypt it.

addSignature(composite: Filename, password: str) → bool

Adds a new signature to the Multifile. This signature associates the indicated certificate with the current contents of the Multifile. When the Multifile is read later, the signature will still be present only if the Multifile is unchanged; any subsequent changes to the Multifile will automatically invalidate and remove the signature.

This flavor of addSignature() reads the certificate, private key, and certificate chain from the same PEM-formatted file. It takes the first private key found as the intended key, and then uses the first certificate found that matches that key as the signing certificate. Any other certificates in the file are taken to be part of the chain.

getNumSignatures() → int

Returns the number of matching signatures found on the Multifile. These signatures may be iterated via get_signature() and related methods.

A signature on this list is guaranteed to match the Multifile contents, proving that the Multifile has been unmodified since the signature was applied. However, this does not guarantee that the certificate itself is actually from who it says it is from; only that it matches the Multifile contents. See validateSignatureCertificate() to authenticate a particular certificate.

getSignatureSubjectName(n: int) → str

Returns the “subject name” for the nth signature found on the Multifile. This is a string formatted according to RFC2253 that should more-or-less identify a particular certificate; when paired with the public key (see getSignaturePublicKey()), it can uniquely identify a certificate. See the comments in getNumSignatures().

getSignatureFriendlyName(n: int) → str

Returns a “friendly name” for the nth signature found on the Multifile. This attempts to extract out the most meaningful part of the subject name. It returns the emailAddress, if it is defined; otherwise, it returns the commonName.

See the comments in getNumSignatures().

getSignaturePublicKey(n: int) → str

Returns the public key used for the nth signature found on the Multifile. This is encoded in DER form and returned as a string of hex digits.

This can be used, in conjunction with the subject name (see getSignatureSubjectName()), to uniquely identify a particular certificate and its subsequent reissues. See the comments in getNumSignatures().

printSignatureCertificate(n: int, out: ostream) → None

Writes the certificate for the nth signature, in user-readable verbose form, to the indicated stream. See the comments in getNumSignatures().

writeSignatureCertificate(n: int, out: ostream) → None

Writes the certificate for the nth signature, in PEM form, to the indicated stream. See the comments in getNumSignatures().

validateSignatureCertificate(n: int) → int

Checks that the certificate used for the nth signature is a valid, authorized certificate with some known certificate authority. Returns 0 if it is valid, -1 if there is some error, or the corresponding OpenSSL error code if it is invalid, out-of-date, or self-signed.

flush() → bool

Writes all contents of the Multifile to disk. Until flush() is called, addSubfile() and removeSubfile() do not actually do anything to disk. At this point, all of the recently-added subfiles are read and their contents are added to the end of the Multifile, and the recently-removed subfiles are marked gone from the Multifile.

This may result in a suboptimal index. To guarantee that the index is written at the beginning of the file, call repack() instead of flush().

It is not necessary to call flush() explicitly unless you are concerned about reading the recently-added subfiles immediately.

Returns true on success, false on failure.

repack() → bool

Forces a complete rewrite of the Multifile and all of its contents, so that its index will appear at the beginning of the file with all of the subfiles listed in alphabetical order. This is considered optimal for reading, and is the standard configuration; but it is not essential to do this.

It is only valid to call this if the Multifile was opened using openReadWrite() and an explicit filename, rather than an iostream. Also, we must have write permission to the directory containing the Multifile.

Returns true on success, false on failure.

getNumSubfiles() → int

Returns the number of subfiles within the Multifile. The subfiles may be accessed in alphabetical order by iterating through [0 .. getNumSubfiles()).

findSubfile(subfile_name: str) → int

Returns the index of the subfile with the indicated name, or -1 if the named subfile is not within the Multifile.

hasDirectory(subfile_name: str) → bool

Returns true if the indicated subfile name is the directory prefix to one or more files within the Multifile. That is, the Multifile contains at least one file named “subfile_name/…”.

scanDirectory(contents: vector_string, subfile_name: str) → bool

Considers subfile_name to be the name of a subdirectory within the Multifile, but not a file itself; fills the given vector up with the sorted list of subdirectories or files within the named directory.

Note that directories do not exist explicitly within a Multifile; this just checks for the existence of files with the given initial prefix.

Returns true if successful, false otherwise.

removeSubfile(index: int) → None

Removes the nth subfile from the Multifile. This will cause all subsequent index numbers to decrease by one. The file will not actually be removed from the disk until the next call to flush().

Note that this does not actually remove the data from the indicated subfile; it simply removes it from the index. The Multifile will not be reduced in size after this operation, until the next call to repack().

removeSubfile(subfile_name: str) → bool

Removes the named subfile from the Multifile, if it exists; returns true if successfully removed, or false if it did not exist in the first place. The file will not actually be removed from the disk until the next call to flush().

Note that this does not actually remove the data from the indicated subfile; it simply removes it from the index. The Multifile will not be reduced in size after this operation, until the next call to repack().

getSubfileName(index: int) → str

Returns the name of the nth subfile.

getSubfileLength(index: int) → size_t

Returns the uncompressed data length of the nth subfile. This might return 0 if the subfile has recently been added and flush() has not yet been called.

Return type

size_t

getSubfileTimestamp(index: int) → time_t

Returns the modification time of the nth subfile. If this is called on an older .mf file, which did not store individual timestamps in the file (or if getRecordTimestamp() is false), this will return the modification time of the overall multifile.

Return type

time_t

isSubfileCompressed(index: int) → bool

Returns true if the indicated subfile has been compressed when stored within the archive, false otherwise.

isSubfileEncrypted(index: int) → bool

Returns true if the indicated subfile has been encrypted when stored within the archive, false otherwise.

isSubfileText(index: int) → bool

Returns true if the indicated subfile represents text data, or false if it represents binary data. If the file is text data, it may have been processed by end-of-line conversion when it was added. (But the actual bits in the multifile will represent the standard Unix end-of-line convention, e.g. n instead of rn.)

getIndexEnd() → streamoff

Returns the first byte that is guaranteed to follow any index byte already written to disk in the Multifile.

This number is largely meaningless in many cases, but if needsRepack() is false, and the file is flushed, this will indicate the number of bytes in the header + index. Everything at this byte position and later will be actual data.

Return type

streamoff

getSubfileInternalStart(index: int) → streamoff

Returns the starting byte position within the Multifile at which the indicated subfile begins. This may be used, with getSubfileInternalLength(), for low-level access to the subfile, but usually it is better to use openReadSubfile() instead (which automatically decrypts and/or uncompresses the subfile data).

Return type

streamoff

getSubfileInternalLength(index: int) → size_t

Returns the number of bytes the indicated subfile consumes within the archive. For compressed subfiles, this will generally be smaller than getSubfileLength(); for encrypted (but noncompressed) subfiles, it may be slightly different, for noncompressed and nonencrypted subfiles, it will be equal.

Return type

size_t

readSubfile(index: int) → bytes

Returns a vector_uchar that contains the entire contents of the indicated subfile.

openReadSubfile(index: int) → istream

Returns an istream that may be used to read the indicated subfile. You may seek() within this istream to your heart’s content; even though it will be a reference to the already-opened pfstream of the Multifile itself, byte 0 appears to be the beginning of the subfile and EOF appears to be the end of the subfile.

The returned istream will have been allocated via new; you should pass the pointer to closeReadSubfile() when you are finished with it to delete it and release its resources.

Any future calls to repack() or close() (or the Multifile destructor) will invalidate all currently open subfile pointers.

The return value will be NULL if the stream cannot be opened for some reason.

Return type

istream

static closeReadSubfile(stream: istream) → None

Closes a file opened by a previous call to openReadSubfile(). This really just deletes the istream pointer, but it is recommended to use this interface instead of deleting it explicitly, to help work around compiler issues.

extractSubfile(index: int, filename: Filename) → bool

Extracts the nth subfile into a file with the given name.

extractSubfileTo(index: int, out: ostream) → bool

Extracts the nth subfile to the indicated ostream.

compareSubfile(index: int, filename: Filename) → bool

Performs a byte-for-byte comparison of the indicated file on disk with the nth subfile. Returns true if the files are equivalent, or false if they are different (or the file is missing).

If Filename.setBinary() or set_text() has already been called, it specifies the nature of the source file. If this is different from the text flag of the subfile, the comparison will always return false. If this has not been specified, it will be set from the text flag of the subfile.

output(out: ostream) → None
ls(out: ostream) → None

Shows a list of all subfiles within the Multifile.

static getMagicNumber() → str

Returns a string with the first n bytes written to a Multifile, to identify it as a Multifile.

setHeaderPrefix(header_prefix: str) → None

Sets the string which is written to the Multifile before the Multifile header. This string must begin with a hash mark and end with a newline character; and if it includes embedded newline characters, each one must be followed by a hash mark. If these conditions are not initially true, the string will be modified as necessary to make it so.

This is primarily useful as a simple hack to allow p3d applications to be run directly from the command line on Unix-like systems.

The return value is true if successful, or false on failure (for instance, because the header prefix violates the above rules).

getHeaderPrefix() → str

Returns the string that preceded the Multifile header on the file, if any. See setHeaderPrefix().

getSubfileNames() → list
property magic_number

Returns a string with the first n bytes written to a Multifile, to identify it as a Multifile.

Return type

string