> For the complete documentation index, see [llms.txt](https://sandbox-docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sandbox-docs.verifone.com/s-adk-5.1-programmers-guide/readme/developing_applications/packman_users_guide.md). # Packman Tool #### Tableof Contents * [Packman tool](#packman_page) * [Introduction](#packman_intro) * [Installation](#packman_installation) * [Pre-requisites](#packman_installation_prerequisites) * [Windows](#packman_installation_windows) * [Linux](#packman_installation_linux) * [Reference](#packman_installation_ref) * [Launch](#packman_launch) * [Windows](#packman_launch_windows) * [Linux](#packman_launch_linux) * [Command line interface](#packman_cli) * [Launch](#packman_cli_launch) * [Help](#packman_cli_help) * [Windows force permissions (vos1, vos2, vos3)](#packman_cli_special_flags) * [doc command](#packman_cli_doc) * [config command](#packman_cli_config) * [build command](#packman_cli_build) * [vos2](#vos2) * [vos3](#vos3) * [titus](#titus) * [extract command (all)](#packman_cli_extract) * [db\_add command (vos3)](#packman_cli_db_add) * [gen\_diff command (vos3)](#packman_cli_gen_diff) * [gen\_removal command (vos3)](#packman_cli_gen_removal) * [list command (all)](#packman_cli_list) * [merge command (vos1, vos2, vos3)](#packman_cli_merge) * [sign command (all)](#packman_cli_sign) * [sign\_retrieve command (vos3, titus)](#packman_cli_sign_retrieve) * [validate command (all)](#packman_cli_validate) * [cpapp\_convert command (vos3)](#packman_cli_cpapp_convert) * [gen\_activation command (vos3)](#packman_cli_gen_activation) * [upwd\_build command (vos3, vaos)](#packman_cli_upwd_build) * [uvrk\_build command (vos2, vos3, vaos, titus)](#packman_cli_uvrk_build) * [pre\_signingportal command (vos2)](#packman_cli_pre_signingportal) * [post\_signingportal command (vos2)](#packman_cli_post_signingportal) * [sponsor\_change\_create command (vos3)](#packman_cli_sponsor_change_create) * [sponsor\_change\_merge command (vos3)](#packman_cli_sponsor_change_merge) * [zip\_create command (vos3, titus)](#packman_cli_zip_create) * [zip\_sign command (vos3, titus)](#packman_cli_zip_sign) * [zip\_apply command (vos3, titus)](#packman_cli_zip_apply) * [stat command (all)](#packman_cli_stat) * [zontalk command (all)](#packman_cli_zontalk) * [ui command](#packman_cli_ui) * [Bundle filters (vos3)](#packman_bundle_filters) * [Signers](#packman_signers) * [dev signer (all plaforms)](#packman_signers_dev) * [local signer (vos1,vos2)](#packman_signers_local) * [signing portal signer (vos3, titus)](#packman_signers_signing_portal) * [User interface](#packman_ui) * [Start](#packman_ui_start) * [Add to catalog](#packman_ui_add_catalog) * [Tree view](#packman_ui_dlfile_treeview) * [Content view](#packman_ui_contentview) * [Search](#packman_ui_find) * [Validation report](#packman_ui_validation) * [Bread crumbs](#packman_ui_breadcrumbs) * [Create a project](#packman_ui_create_project) * [Writable nodes](#packman_ui_create_writable) * [Select signer and signer users](#packman_ui_select_signer) * [Delete selected nodes](#packman_ui_delete_selected) * [Undo / redo](#packman_ui_undo_redo) * [Context menu](#packman_ui_context_menu) * [Edit text file](#packman_ui_edit_text_file) * [Adding files to archive](#packman_ui_add_files) * [Change permissions](#packman_ui_change_permissions) * [Exporting](#packman_ui_export) * [Automatic fixes](#packman_automatic_fixes) * [Device mode validation (vos3)](#packman_device_modes) ## Packman tool This page contains information about the Packman tool usage and design. ## Introduction On **vos1** and **vos2** platforms, the packaging is using three levels of archives. * Dlfile * Bundle(s) * Package(s) Please refer to [Secure Installer](/s-adk-5.1-programmers-guide/readme/system_overview/pg_all_components/pg_vos_secins_guide.md#secins_page) for complete description of these archives. On **vos3** platform, the packaging is using two levels of archives. * Dlfile * Bundle csd(s) * Bundle inf(s) Please refer to VOS3\_Installer for complete description of these archives. On **titus** platform, the packaging is using one level archive. * TitusDl The Packman tool is providing three facilities to manage the creation, modification and signing of archives: 1. Command line interface 2. UI interface 3. Python library with APIs ## Installation ### Pre-requisites Packman tool has following pre-requisites: * Host OS: Windows or Linux. * HTML5 CSS3 Javascript browser (only if UI interface is used) ### Windows 1. Install python 3.8+ for windows * choose 'Customize Installation' ![](/files/UGGbkkxSvSYqDYgSfykF) * verify that install 'pip' is ticked ![](/files/jMsbal02vUpud60cb7j2) * launch installation 2. Extract packman release file (.zip) to a directory of your choice * tools like 7-zip and the like can be used * 'c:\tools\packman' is assumed in this documentation 3. Open a command line window 'cmd' 4. Change current directory to packman directory ```cpp cd c:\tools\packman ``` 5. Install requirements ```cpp py -m pip install -e . ``` ### Linux These steps may vary upon linux distributions. Ubuntu is assumed in the examples. 1. Install python 3.8+ ```cpp sudo apt install python3 ``` 2. Install pip ```cpp sudo apt install python3-pip ``` 3. Extract packman release file (tgz) to a directory of your choice * '\~/tools/packman' is assumed in this documentation ```cpp tar xzvf packman_x.y.z.tgz ``` 4. Change current directory to packman directory ```cpp cd ~/tools/packman ``` 5. Install requirements ```cpp pip install -e . ``` ### Reference ## Launch ### Windows 1. Open a command line window 'cmd' ```cpp py packman.py ``` ### Linux * Open a terminal (ie Ctrl+Alt+T) 1. Launch ```cpp packman.py ``` ## Command line interface ### Launch All command line examples will use the same format: ```cpp packman.py ``` Please adapt to: * on Windows: ```cpp python packman.py ``` * on Linux: ```cpp ./packman.py ``` ### Help * General help: ```cpp packman.py -h ``` Example output: ```cpp usage: packman.py [-h] [--show_all] [--winforce_permissions] {build,config,cpapp_convert,db_add,doc,extract,gen_activation,gen_diff,gen_removal,hps_build,hps_extract,list,merge,post_signingportal,pre_signingportal,sign,sign_retrieve,sponsor_change_create,sponsor_change_merge,stat,ui,up_build,upwd_build,uvrk_build,validate,zip_apply,zip_create,zip_sign,zontalk} ... Packman v1.17.1 positional arguments: {build,config,cpapp_convert,db_add,doc,extract,gen_activation,gen_diff,gen_removal,hps_build,hps_extract,list,merge,post_signingportal,pre_signingportal,sign,sign_retrieve,sponsor_change_create,sponsor_change_merge,stat,ui,up_build,upwd_build,uvrk_build,validate,zip_apply,zip_create,zip_sign,zontalk} Detailed command usage: -h options: -h, --help show this help message and exit --show_all do not collapse issues --winforce_permissions force usrX exec permissions on windows Examples: Build dlfile packman.py build -t vos2 -i input_dir -d dl.file.tgz packman.py build -t vos3 -i input_dir -d dl.file.tar Set and show configuration packman.py config -l packman.py config sign.online.product Convert CP application packman.py cpapp_convert -t vos3 -s dev -z cpapp-123345678.zip -o dl.dlfile.tar packman.py cpapp_convert -t vos3 -s dev --cpapp_type appdev -d dl.cpapp_prod.tar -o dl.cpapp_appdev.tar Add bundles to database packman.py db_add -t vos3 -d dl.file.tar User guide packman.py doc Extract dlfile packman.py extract -t vos2 -d dl.file.tgz -o ouputdir packman.py extract -t vos3 -d dl.file.tar -o ouputdir Generate activation dlfile packman.py gen_activation -t vos3 -s dev -d dl.file.tar -o dl.file_activate.tar Generate differential dlfile packman.py gen_diff -t vos3 --src dl.source.tar --dst dl.destination.tar -o dl.differential.tar Generate removal dlfile packman.py gen_removal -t vos3 -s dev -d dl.file.tar -o dl.file_remove.tar Build HPS archive (discouraged) packman.py hps_build -t vos3 --neo dlfile_neo1.tar --neo2 dlfile_neo1.tar -o allneo_dlfile.hps.tar Extract HPS archive (discouraged) packman.py hps_extract -t vos3 -i myfile.hps.tar -fo outputdir List content of dlfiles packman.py list -t vos2 -rd dlfile.tgz packman.py list -t vos3 -rd dl.file.tar Merge or filter dlfile packman.py merge -t vos2 -d dl.file1.tgz dl.file2.tgz -o dl.file_merged.tgz packman.py merge -t vos3 -d dl.file1.tar dl.file2.tar -o dl.file_merged.tar Postprocess dlfile after Signing Portal or Package Manager packman.py post_signingportal -t vos2 -d dlfile.tgz -o output.tgz Preprocess dlfile for Signing Portal or Package Manager packman.py pre_signingportal -t vos2 -d dlfile.tgz -o output.tgz Sign dlfile packman.py sign -t vos2 -s dev -d dl.file.tgz -o dl.file_signed.tgz packman.py sign -t vos3 -s dev -d dl.file.tar -o dl.file_signed.tar Retrieve result of online signature packman.py sign_retrieve -t vos3 --request_id 689b4363c4345a308395574c -o dl.file_signed.tar Create a sponsor change packman.py sponsor_change_create -t vos3 -s dev --current_sponsor 123456 --serial_numbers "123-456-789" -o dl.dlfile.tar Merge two sponsor change dlfiles packman.py sponsor_change_merge -t vos3 -i dl.signed_current.tar dl.signed_new.tar -o dl.dlfile.tar Output information on dlfile packman.py stat -t vos2 -d dlfile.tgz packman.py stat -t vos3 -d dl.file.tar User interface packman.py ui packman.py ui -t vos3 -d dl.file.tar Unified password packaging - UPWD packman.py upwd_build -t vos3 -s dev -e test -i password_changes.json -o file.upwd.tar packman.py upwd_build -t vos3 -s dev -e encryption_cert.pem -i password_changes.json -o file.upwd.tar packman.py upwd_build -t vaos -s dev -e encryption_cert.pem -i password_changes.json -o file.zip packman.py upwd_build -t vaos -s dev -e encryption_cert.pem -i password_changes.json -o file.apk Unified VRK packaging - UVRK packman.py uvrk_build -t vos3 -i payload_123-456-789.vrk2.json -o file.uvrk.tar Validate dlfile packman.py validate -t vos2 -d dl.file.tgz packman.py validate -t vos3 -d dl.file.tar Apply zip file signed to directory or dlfile packman.py zip_apply -t vos3 -i directory -z files_signed.zip packman.py zip_apply -t vos3 -d dlfile.tar -z files_signed.zip Create zip file to sign from directory or dlfile packman.py zip_create -t vos3 -i directory -o files_to_sign.zip packman.py zip_create -t vos3 -d dlfile.tar -o files_to_sign.zip Sign content of zip packman.py zip_sign -t vos3 -s dev -c EMV -z files.zip -o files_signed.zip Zontalk upload packman.py zontalk -p /dev/ttyUSB0 -u dlfile.tar packman.py zontalk -p COM6 -u dlfile.tar ``` {% hint style="info" %} that options can be combined: '-r -d dlfile.tgz' is equivalent to '-rd dlfile.tgz' {% endhint %} * Command help: ```cpp packman.py -h ``` Example output: ```cpp packman.py list -h ``` ```cpp usage: packman.py list [-h] [--report_type {security,dependency,content}] [-r] -t {vos1,vos2,vos3} (-d DLFILE | -b BUNDLE | -p PACKAGE) list content of archive optional arguments: -h, --help show this help message and exit --report_type {security,dependency,content} report type - vos1:{'content'} vos2:{'content'} vos3:{'security', 'dependency', 'content'} -r, --recurse act recursively -t {vos1,vos2,vos3}, --platform {vos1,vos2,vos3} target platform -d DLFILE, --dlfile DLFILE dlfile path -b BUNDLE, --bundle BUNDLE bundle path -p PACKAGE, --package PACKAGE package path ``` Here a summary of commands: | Command | Description | | ------------------------------------------------------------- | ----------------------------------------------- | | [doc](#packman_cli_doc) | show documentation | | [config](#packman_cli_config) | setup and list configuration | | [build](#packman_cli_build) | build archive from directories | | [cpapp\_convert](#packman_cli_cpapp_convert) | convert CP application | | [db\_add](#packman_cli_db_add) | add bundles to database | | [extract](#packman_cli_extract) | extract content of archive | | [gen\_activation](#packman_cli_gen_activation) | generate activation dlfile | | [gen\_diff](#packman_cli_gen_diff) | generate differential dlfile | | [gen\_removal](#packman_cli_gen_removal) | generate removal dlfile | | [list](#packman_cli_list) | list content of archive | | [merge](#packman_cli_merge) | merge several archives into one | | [pre\_signingportal](#packman_cli_pre_signingportal) | modify dlfile for usage with signing portal | | [post\_signingportal](#packman_cli_post_signingportal) | modify dlfile after signing portal usage | | [sign](#packman_cli_sign) | sign archive content | | [sign\_retrieve](#packman_cli_sign_retrieve) | retrieve online signing result | | [sponsor\_change\_create](#packman_cli_sponsor_change_create) | create a sponsor change | | [sponsor\_change\_merge](#packman_cli_sponsor_change_merge) | merge two sponsor change | | [stat](#packman_cli_stat) | output information on archive | | [ui](#packman_ui) | launch user interface | | [upwd\_build](#packman_cli_upwd_build) | build unified packaging password | | [uvrk\_build](#packman_cli_uvrk_build) | build unified packaging vrk | | [validate](#packman_cli_validate) | retrieve validation report on archive | | [zip\_create](#packman_cli_zip_create) | create zip file with files to sign in directory | | [zip\_sign](#packman_cli_zip_sign) | sign file within zip file | | [zip\_apply](#packman_cli_zip_apply) | add signatures in zip file back to directory | | [zontalk](#packman_cli_zontalk) | zontalk protocol | {% hint style="info" %} All packaging operations require to provide the target platform (ie '-t vos2') {% endhint %} ### Windows force permissions (vos1, vos2, vos3) In order to force executable permission bits when running packman on Windows, a special option flag '--winforce\_permissions' can be used: ```cpp packman.py --winforce_permissions build -t vos3 -s dev -i input_dir -fd dlfile.tar ``` On Windows, this will build a dlfile archive named 'dlfile.tar' from the content of the directories 'input\_dir' for the platform vos3 and if a user package has an executable file, its permissions bits for execution will be set where read bit permission is set. ### doc command The 'doc' command opens this documentation in a browser. ### config command The 'config' command allows to set configuration key / value that will be used as defaults by other commands. This allows to setup once and simplify command line arguments. Here is the list of currently supported configurations: | key | default value | option | Description | | ------------------------ | --------------------------------- | --------------------- | ------------------------------------------ | | sign.online\_product | empty | --online\_product | online signing product identifier | | sign.online\_token\_path | empty | --online\_token\_path | online signing token file full path | | sign.online\_url | | --online\_url | online signing product identifier | | sign.online\_timeout | 60 | --online\_timeout | online signing approval timeout in seconds | Example usage to set a value: ```cpp packman.py config sign.online_product o3fw8emrARQvXt9pE ``` Example usage to reset a value to default: ```cpp packman.py config -r sign.online_product ``` Example usage to list all current values: ```cpp packman.py config -l ``` Note: in the usage description, the configurable options are noted with '(config)' ### build command The 'build' command creates archives (dlfile, bundle, package) from the contents of directories. Please refer to 'build' help for all options. #### vos2 Example usage: ```cpp packman.py build -t vos2 -i input_dir input_dir2 -d dlfile.tgz ``` This will build a dlfile archive 'dlfile.tgz' from the content of the directories 'input\_dir' and 'input\_dir2' for the platform vos2. This input directory should normally contain CONTROL directory, bundles, ... The 'build' command can also act recursively to create archives from the content of a directory. The top directory provided contains bundle directories which in turn contain package directories. Each directory must contain the appropriate CONTROL directory and files. The recursive build will recursively package all of them to produce a dlfile. The recursive build is enabled using the option flag '-r'. Example usage (recursive): ```cpp packman.py build -t vos2 -ri input_dir -d dlfile.tgz ``` This will build a dlfile archive named 'dlfile.tgz' from the content of the directory 'input\_dir' recursively packaging dlfile/bundle/package directories inside for the platform vos2. #### vos3 Example usage: ```cpp packman.py build -t vos3 -s dev -i input_dir input_dir2 -d dlfile.tar ``` This will build a dlfile archive 'dlfile.tar' from the content of the directories 'input\_dir' and 'input\_dir2' for the platform vos3. Each input directory should normally contain manifest and package directories coresponding to one bundle. Here is an example of a bundle input directory structure: ![](/files/85vF7rLXrGL0HrMU9P7n) The 'build' command can also act recursively to create archives from the content of a directory. The top directory provided contains bundle directories which in turn contain package directories. Each directory must contain the appropriate manifest file and package directories (with their content). The recursive build will recursively package all of them to produce a dlfile. The recursive build is enabled using the option flag '-r'. Example usage (recursive): ```cpp packman.py build -t vos3 -s dev -ri input_dir -d dlfile.tar ``` This will build a dlfile archive named 'dlfile.tar' from the content of the directory 'input\_dir' recursively packaging dlfile/bundle directories inside for the platform vos3. This command allows to specify [Device mode validation (vos3)](#packman_device_modes) #### titus Example usage: ```cpp packman.py build -t titus -s dev -i input_dir -d titusdl.tar ``` This will build a titusdl archive 'titusdl.tar' from the content of the directories 'input\_dir' for the platform titus. Input directory should normally contain manifest and corresponding files. Here is an example of a bundle input directory structure: ![](/files/SpnKycHV4GkrLcqVViLc) Here is an example of 'manifest.json' for user configuration for titus: ```cpp { "name": "my_titus_usrconfig", "version": "1.0.0", "contents": [ { "name": "usrconfig.tar", "type": "usrconfig" } ] } ``` ### extract command (all) The 'extract' command extracts recursively the content of archives (dlfile, bundle, package) to directories. The extracted content is layed out such as a recursive build done on this output would recreate the original archive. Please refer to 'extract' help for all options. Example usage: ```cpp packman.py extract -t vos2 -d dlfile.tgz -o dlfile_dir ``` This will extract a dlfile archive named 'dlfile.tgz' recursively to the directory 'dlfile\_dir' for the platform vos2. ### db\_add command (vos3) The 'db\_add' command takes as input a dlfile and registers its content to a local database. This database is located at \/.packman/db/ The content of the database can be used for generating differentials: see [gen\_diff command (vos3)](#packman_cli_gen_diff). Before being registered, the dlfile is first validated. Example usage: ```cpp packman.py db_add -t vos3 -d dlfile.tar ``` This will look register to database all bundles and upfiles in 'dlfile.tar'. ### gen\_diff command (vos3) The 'gen\_diff' command takes as input source and destination bundles and creates a differential dlfile. This command operates either by providing a differential description file or by providing source ans destination dlfiles When providing source and destination dlfiles, packman will add all bundles and upfiles of all dlfiles to the database (see [db\_add command (vos3)](#packman_cli_db_add) ) then create a differential description file containing the matching information and run the differential command with it. Differential process overview: * In all steps, targeting of both source and destination are taken into account * For all upfiles, removal bundles and sponsor changes in destination: add to diff dlfile * In all other cases: perform entry by entry selection between "add", "copy" and "sbspatch" operations : add resulting differential bundle to diff dlfile Example usage (differential description file): ```cpp packman.py gen_diff -t vos3 --diff diff_file.json -o dl.diff.tar ``` This will look for the bundles listed in diff\_file.json (source and destination), check that they are present in database and generate a differential dlfile 'dl.diff.tar' for the platform vos3. Example usage (source and destination dlfiles): ```cpp packman.py gen_diff -t vos3 --src dl.source.tar --dst dl.destination.tar -o dl.diff.tar ``` This will add to database all bundles and upfiles in 'dl.source.tar' and 'dl.destination.tar' and then generate a differential dlfile 'dl.diff.tar' for the platform vos3. Here is shown the structure of a differential description file: ```cpp { "source": { "bundles": [ { "digest": "36e7300a0559831ede5065d1dd10d6802e4ad884d7965d512eabcb6f562430de", "name": "bundle_a", "version": "1.0.0" } ... ] "upfiles": [ { "digest": "6802e4ad884d7965d512eabcb6f562430de36e7300a0559831ede5065d1dd10d", "name": "mykeya.uvrk.tar" }, ... ] }, "destination": { "bundles": [ { "digest": "4ad884d7965d512eabcb6f562430de36e7300a0559831ede5065d1dd10d6802e", "name": "bundle_b", "version": "1.0.0" }, ... ] "upfiles": [ { "digest": "e36e7300a06802e4ad884d7965d512eabcb6f562430d559831ede5065d1dd10d", "name": "mykeyb.uvrk.tar" }, ... ] } } ``` Note: the differential process on entries ('copy' and 'sbspatch' operations) are allowed on all destination package types (read-only or not) and can refer any file of any source bundle/package as long as this source package is read-only. This command allows to specify [Bundle filters (vos3)](#packman_bundle_filters) ### gen\_removal command (vos3) The 'gen\_removal' takes as input a dlfile containing bundles and creates a dlfile containing the corresponding removal bundles. The type of remove bundles can be chosen with '--remove\_type' which takes one of the following values: * **bundle\_version** (default): this creates remove bundles for the bundle and its version * **bundle** : this creates remove bundles for the bundle without version specified * **user** : this creates remove bundles for the user (removing all bundles for that user) Please refer to 'gen\_removal' help for all options. Example usage: ```cpp packman.py gen_removal -t vos3 -s dev -d dl.file.tar -o dl.file_remove.tar ``` This will look for the bundles in dlfile named 'dlfile.tgz' and create in 'dl.file\_remove.tar' removal bundles using the 'bundle\_version' type for the platform vos3. This command allows to specify [Bundle filters (vos3)](#packman_bundle_filters) ### list command (all) The 'list' command lists content of archives (dlfile, bundle, package). Please refer to 'list' help for all options. Example usage: ```cpp packman.py list -t vos2 -rd dlfile.tgz ``` This will list recursively (-r) the content of a dlfile archive (-d) named 'dlfile.tgz' for the platform vos2. Example: ```cpp > ./packman.py list -t vos2 -rd dl.normal.tgz Dlfile dl.normal.tgz Bundle bdl_normal.tgz Dir CONTROL/ File control File filelist Package pkg_normal.tgz Dir CONTROL/ File control File filelist File normal Signature pkg_normal.tgz.p7s ``` Other types of reports are available by using the '--report\_type' option with: * **content** (all platforms, default): lists content and entry types * **package** (vos3): lists packages with Bundle name, Package name and package type * **security** (vos3): list bundles, their signer, user membership and requested capabilities * **dependency** (vos3): list bundles, their hardware platform, targeting and dependencies * **target** (vos3): lists installed entries with location, type (Dir, File, Symlink), size, linkname, user, group, mode, capabilities, sha1 * **similarity** (vos3) (experimental): lists equal or similar file contents ### merge command (vos1, vos2, vos3) The 'merge' command allows to combine several archives of same type (dlfile, bundle, package, uvrk, upwd) to create a single archive of that same type containing the merge of all contents. Merging archives with different types is not allowed except between dlfile and a unified package (uvrk, upwd). Please refer to 'merge' help for all options. Example usage: ```cpp packman.py merge -t vos2 -d dlfile1.tgz dlfile2.tgz -o dlfile.tgz ``` This will create a dlfile archive named 'dlfile.tgz' which contains all content of the 'dlfile1.tgz' and 'dlfile2.tgz' for the platform vos2. ```cpp packman.py merge -t vos3 -u mykey1.uvrk.tar mykey2.uvrk.tar -o mykeys.uvrk.tar ``` This will create a combined uvrk archive with both uvrk archive keys merged. ```cpp packman.py merge -t vos3 -d dlfile.tar -u mykeys.uvrk.tar mypasswords.upwd.tar -o dl.merged.tar ``` This will create a dlfile 'dl.merged.tar' that contains all bundles of 'dlfile.tar', 'mykeys.uvrk.tar' and 'mypasswords.upwd.tar'. This command allows to specify [Bundle filters (vos3)](#packman_bundle_filters) and [Device mode validation (vos3)](#packman_device_modes) ### sign command (all) The 'sign' command signs content of archives (dlfile, bundle, package). Please refer to 'sign' help for all options and to [Signers](#packman_signers). Example usage 1 (vos2): ```cpp packman.py sign -t vos2 -s dev -d dlfile.tgz -o dlfile_signed.tgz ``` This will list recursively sign the content of a dlfile archive (-d) named 'dlfile.tgz' for the platform vos2 and output result in 'dlfile\_signed.tgz'. Example usage 2 (vos2): ```cpp packman.py sign -t vos2 -rs dev -d dlfile.tgz -fo dlfile_signed.tgz ``` Same as above except that if a signature already exists, it will resign anyway (-r) and if output file already exists, it will force overwriting (-f). Example usage 3 (vos3): ```cpp packman.py sign -t vos3 -s dev -d dlfile.tar -fo dlfile_signed.tar ``` This will sign for development all bundles contained in dlfile.tar for the platform vos3 and output result in 'dlfile\_signed.tar'. For online signing, several options (option name starts with 'online') are available. See [signing portal signer (vos3, titus)](#packman_signers_signing_portal) Example usage 4 (vos3 online signing): ```cpp packman.py sign -t vos3 -s online --online_retrieve --online_product o3fw8emrARQvXt9pE --online_token_path /home/user/mytoken.txt --online_url https://sign.verifone.com:52443 --online_timeout 3600 -d dlfile.tar -fo dlfile_signed.tar ``` This command is generally simplified by use of configuration: see [config command](#packman_cli_config) It chooses synchronous mode with --online\_retrieve and will wait one hour for the approval on the portal with '--online\_timeout'. The product, token and url selected for signing are specified with '--online\_product', '--online\_token\_path' and '--online\_url' respectively. Once the request is approved on server (within the hour), the dlfile 'dlfile.tar' will be signed and stored in 'dlfile\_signed.tar'. ### sign\_retrieve command (vos3, titus) The 'sign\_retrieve' command is used to retrieve online signed results (asynchronous mode). Please refer to 'sign\_retrieve' help for all options. Packman stores locally all online signing requests that have been issued. A list of all online pending requests made from this PC can be shown by using command without specifying any request id: ```cpp packman.py sign_retrieve -t vos3 ``` The list of pending requests is sorted by ascending date, one per line which look like this one: ```cpp 2025-08-20 13:51:21 id: 68a5b6cbc4345a40839557e8 name: dl.bundle_usr1_signed.tar hash: 472e30141e11d8efd24a8f25e2b00037e2856310c9f61e334ce2a391d1261e05 product: o3fwBemrDRQvAt9pE ``` * **id** corresponds to the request id * **name** corresponds to name of the file sent for online signing * **hash** corresponds to hash of the file sent for online signing * **product** corresponds to signing product selected for for online signing In order to retrieve a request result, one need to provide the request id and the output path: ```cpp packman.py sign_retrieve -t vos3 --request_id 68a5b6cbc4345a40839557e8 -fo dlfile_signed.tar ``` The above example assumes that token path has already been configured with [config command](#packman_cli_config) The 'sign\_retrieve' command is also using the configured timeout (config or option '--online\_timeout') to determine how long to wait for an approval if request has not yet been approved. ### validate command (all) The 'validate' command creates a validation report for the content of archives (dlfile, bundle, package). Please refer to 'validate' help for all options. Example usage (vos2): ```cpp packman.py validate -t vos2 -rd dlfile.tgz ``` This will recursively scan the archive and display packaging errors if found. Example usage (vos3): ```cpp packman.py validate -t vos3 -rd dlfile.tar ``` This will recursively scan the archive and display packaging errors if found. Example output: ```cpp > ./packman.py validate -t vos2 -rd test_resources/dl.pkg_notcompressed.tgz ERROR (structure) - bdl_pkg_notcompressed.tgz/pkg_pkg_notcompressed.tar : Package is not compressed errors:1 warnings:0 ``` This command allows to specify [Device mode validation (vos3)](#packman_device_modes) ### cpapp\_convert command (vos3) The 'cpapp\_convert' command converts a CP application (Commerce Plaform) into an installable dlfile. The input can be a CP application zip file or a dlfile. The type of dlfile output can be chosen using the '--cpapp\_type' option: 'prod' for normal type, 'appdev' for development on appdev devices. Please refer to 'cpapp\_convert' help for all options. Example usage: ```cpp packman.py cpapp_convert -t vos3 -s dev -z mycpapp-887643134.zip -o dl.mycpapp-887643134.tar ``` This will extract the CP application zip named 'mycpapp-887643134.zip', generate a CP application dlfile and sign it for development for the platform vos3. ```cpp packman.py cpapp_convert -t vos3 -s dev --cpapp_type appdev -z mycpapp-887643134.zip -o dl.mycpapp-887643134_appdev.tar ``` This will extract the CP application zip named 'mycpapp-887643134.zip', generate a CP application dlfile for appdev device and sign it for development for the platform vos3. ```cpp packman.py cpapp_convert -t vos3 -s dev --cpapp_type appdev -d dl.mycpapp-887643134.tar -o dl.mycpapp-887643134_appdev.tar ``` This will convert the CP application dlfile named dl.mycpapp-887643134.tar to CP application dlfile for appdev device and sign it for development for the platform vos3. ### gen\_activation command (vos3) The 'gen\_activation' command creates usr1 activation installable dlfile which activates features of the system. This can be used typically to generate activation for Commerce Applications. Please refer to 'gen\_activation' help for all options. Example usage: ```cpp packman.py gen_activation -t vos3 -s dev -d dl.mycpapp-887643134.tar dl.mycpapp-887643134_activate.tar ``` This will extract the CP application bundle in dl.mycpapp-887643134.tar and generate a corresponding activation dlfile and sign it for development for the platform vos3. ### upwd\_build command (vos3, vaos) The 'upwd\_build' command creates unified packaging for password changes. Please refer to 'upwd\_build' help for all options. Example usage (vos3): ```cpp packman.py upwd_build -t vos3 -e encryption_cert.pem -s dev -i password_change.json -o file.upwd.tar ``` This will create the file.upwd.tar package containing encrypted and signed password changes instructions. The '-e encryption\_cert.pem' indicates which encryption certificate (pem file) to use for encryption and the '-s dev' indicates signing with development key. For testing purposes only, a generic 'test' encryption certificate is bundled with packman and can be specified with option '-e test' (to test both on prod and dev devices). The password changes instructions are passed using the content of a JSON file named 'password\_change.json' in this example. The structure of this instruction file is: * **password\_changes** (mandatory): array of objects * **target** (mandatory): array of strings containing target serial numbers expressions * **name** (mandatory): string containing name of the password * **pass** (mandatory): string containing value of the password. Valid passwords are 7 to 12 digits. * **expired** (optional, default to false): boolean indicating if password is expired * **require\_old** (optional, default to false): boolean indicating if old password is needed to change password For the target field, the serial number expression must be either: * a fully defined serial number for a single device: like "123-456-789" (1 serial number) * a globing serial number expression using one or more wildcard (\*) like "12\*-456-78\*" (100 serial numbers) Here is an example of such file: ```cpp { "password_changes": [ { "target": ["112-123-123"], "name": "SUPERVISOR", "pass": "1234567" }, { "target": ["112-123-123"], "name": "LEVEL1", "pass": "1234567" }, { "target": ["112-123-555","112-123-44*"], "name": "LEVEL1", "pass": "00123471321", "expired": true, "require_old": true } ] } ``` In such unified packaging, the naming of content and output archive is important and packman will fail on wrong namings. Note that 'merge' and 'validate' accept these type of unified packages for processing using the '-u' option. **Special case of vaos** Example usage (vaos): ```cpp packman.py upwd_build -t vaos -e encryption_cert.pem -s dev -i password_change.json -o file.zip ``` In order to be comply with vaos package signing, the upwd archive mentioned above will be automatically wrapped into a zip archive. The output archive file can be named with: * '.zip' extension: can be directly installed on device * '.apk' extension: can be used to sign online. Once signed, resulting file can be renamed with '.zip' extension for installation. If dev signature is requested (-s dev) this output file will be development signed using 'apksigner' tool. This 'apksigner' tool needs to be installed separately and PATH environment variable set for packman to invoke it. It is available in the Android SDK but can also be installed separately using the Android "Build tools" (choose OS flavor). Some linux distributions allow direct package installation (ie ubuntu: 'sudo apt install apksigner'). ### uvrk\_build command (vos2, vos3, vaos, titus) The 'uvrk\_build' command creates unified packaging for vrk payloads. Please refer to 'uvrk\_build' help for all options. Example usage: ```cpp packman.py uvrk_build -t vos3 -i payload_123-456-789.vrk2.json -o file.uvrk.tar ``` This will create the file.uvrk.tar package containing the payload passed as parameter. In such unified packaging, the naming of content and output archive is important and packman will fail on wrong namings. Note that 'merge' and 'validate' accept these type of unified packages for processing using the '-u' option. ### pre\_signingportal command (vos2) The 'pre\_signingportal' command preprocesses a dlfile before usage in Signing Portal or Package Manager. This command and the associated 'post\_signingportal' work as workarounds for those tools for vos2 platform. It performs the following operations: 1. remove blacklist directory in dlfile 2. applies all automatic fixes see [Automatic fixes](#packman_automatic_fixes) To restore the optimizations, it is recommended to use 'post\_signingportal' on resulting dlfile after Signing Portal and Package Manager usage. Please refer to 'pre\_signingportal' help for all options. Example usage: ```cpp packman.py pre_signingportal -t vos2 -d dlfile.tgz -o output.tgz ``` This will preprocess the dlfile 'dlfile.tgz' and write preprocessed dlfile to 'ouput.tgz'. ### post\_signingportal command (vos2) The 'post\_signingportal' command postprocesses a dlfile after usage in Signing Portal or Package Manager. This command and the associated 'pre\_signingportal' work as workarounds for those tools for vos2 platform. It performs the following operations: 1. restore blacklist directory in dlfile Please refer to 'post\_signingportal' help for all options. Example usage: ```cpp packman.py post_signingportal -t vos2 -d dlfile.tgz -o output.tgz ``` This will postprocess the dlfile 'dlfile.tgz' and write postprocessed dlfile to 'ouput.tgz'. ### sponsor\_change\_create command (vos3) The 'sponsor\_change\_create' command creates a sponsor change dlfile. Please refer to 'sponsor\_change\_create' help for all options. Example usage (unlock): ```cpp packman.py sponsor_change_create -t vos3 -s dev --current_sponsor 123456 --serial_numbers "123-456-789" -o dl.dlfile.tar ``` This will create dl.dlfile.tar that can be used to remove sponsor of device with serial number 123-456-789 and sponsor ID 123456. This dlfile will need to be production signed with matching sponsor signer 123456 that can sign for usr1. Example usage (change): ```cpp packman.py sponsor_change_create -t vos3 -s dev --current_sponsor 123456 --new_sponsor 456789 --serial_numbers "123-456-789" -o dl.dlfile.tar ``` This will create dl.dlfile.tar that can be used to change sponsor of device with serial number 123-456-789 and sponsor ID 123456 to sponsor 456789. This dlfile will need to be production signed two times: 1. signed with matching sponsor signer 123456 that can sign for usr1. 2. signed with matching sponsor signer 456789 that can sign for usr1. Those two signed outputs need then to be merged back with the merge command see [sponsor\_change\_merge command (vos3)](#packman_cli_sponsor_change_merge) ### sponsor\_change\_merge command (vos3) The 'sponsor\_change\_merge' command merges two signed dlfiles to create a sponsor change dlfile. Please refer to 'sponsor\_change\_merge' help for all options. Example usage: ```cpp packman.py sponsor_change_merge -t vos3 -i dl.signed_current.tar dl.signed_new.tar -o dl.dlfile.tar ``` This will create dl.dlfile.tar that can be used to change the sponsor of a device. The two dlfiles provided need to be signed by the correct signers for the current and new sponsors. see [sponsor\_change\_create command (vos3)](#packman_cli_sponsor_change_create) ### zip\_create command (vos3, titus) The 'zip\_create' command creates a zip file containing all files to be signed from a directory recursively or from a list of archives. This command is primarily intended for the following process: * gather all assets to be sigend into a zip file (**zip\_create** command) * upload manually the zip file for signing on Verifone Signing Portal (or **zip\_sign** command for testing) * download signed zip file after approval * apply the signatures back to original files (**zip\_apply** command) Please refer to 'zip\_create' help for all options. Example usage (on directory): ```cpp packman.py zip_create -t vos3 -i directory -fo zip_to_sign.zip ``` This will recursively scan files and archives in directory and create zip file to be signed. Example usage (on archives): ```cpp packman.py zip_create -t vos3 -d dlfile1.tar -fo zip_to_sign.zip ``` This will scan archives and create zip file to be signed. Multiple archives can be provided (-d dlfile1.tar dlfile2.tar ...), please make sure to provide the exact same list to the 'zip\_apply' command. ### zip\_sign command (vos3, titus) The 'zip\_sign' command signs the files contained in a zip file and create a signed zip file. The zip file to sign, is typically the output of the "zip\_create" command and when signed, the input of the "zip\_apply" command. This command is generally used as a local and test-only replacement to a more formal signature on the Verifone Signing Portal. Please refer to 'zip\_sign' help for all options. Example usage: ```cpp packman.py zip_sign -t vos3 -s dev -z zip_to_sign.zip -fo zip_zigned.zip ``` This will recursively scan files in zip\_to\_sign.zip and create zip\_zigned.zip containing dev signatures. ### zip\_apply command (vos3, titus) Please refer to [zip\_create command (vos3, titus)](#packman_cli_zip_create) for context. The 'zip\_apply' command will insert all signatures in zip file back to directories or archives. The zip file used as input is typically the output of a successfully signed zip file from Verifone Signing Portal. For testing, the "zip\_sign" command can mimick locally this signature step. As a for 'zip\_apply', this command can work either on a directory recursively or on archives directly. Please refer to 'zip\_apply' help for all options. When using a directory, the directory needs to be the exact same as when the 'zip\_create' command was used. Example usage (on a directory): ```cpp packman.py zip_apply -t vos3 -i directory -z zip_zigned.zip ``` This will recursively scan files in directories and add signatures from zip\_zigned.zip. Example usage (on archives): ```cpp packman.py zip_apply -t vos3 -d dlfile1.tar -z zip_zigned.zip ``` This will scan archives and add signatures from zip\_zigned.zip. Multiple archives can be provided (-d dlfile1.tar dlfile2.tar ...), please make sure to provide the same list as when the 'zip\_create' command was used. ### stat command (all) The 'stat' command outputs general information about an archive in a parsable form. Please refer to 'stat' help for all options. Example usage: ```cpp packman.py stat -t vos3 -d dlfile.tar ``` This will output information like: ```cpp name = dlfile.tar archive_type = Dlfile platform = vos3 size = 10240 hash_sha256 = 6b8018510c77b26fa80a651a86db4334d1dbe4f7dcefb843cab304a75644ee7e bundle_count = 1 sponsor_id = 010245 bundle_prod_count = 0 bundle_appdev_count = 0 bundle_osdev_count = 1 ``` ### zontalk command (all) The 'zontalk' command provides a way to upload archives to a device using serial port. Example usage (linux): ```cpp packman.py zontalk -p /dev/ttyUSB0 -u dlfile.tar ``` This connects to a device waiting for a zontalk connection using serial port '/dev/ttyUSB0' and default 115200 baudrate to upload 'dlfile.tar'. Example usage (windows): ```cpp packman.py zontalk -p COM6 -u dlfile.tar ``` This connects to a device waiting for a zontalk connection using serial port 'COM6' and default 115200 baudrate to upload 'dlfile.tar'. Other features: * multiple files can be uploaded * baudrate can be specified * message can be sent for display on device Please refer to 'zontalk' help for all options. ### ui command The 'ui' command without any options launches a local webserver and a browser client for user interface. Example usage: ```cpp packman.py ui ``` The 'ui' command can also directly provide one or multiple archives to be opened in the user interface. Example usage: ```cpp packman.py ui -t vos3 -d dl.file.tar ``` This will act as shortcut to open ui, upload the dl.file.tar, add it to catalog and select it in the user interface. Please refer to [User interface](#packman_ui) as guide to the user interface. ## Bundle filters (vos3) Where mentioned, commands like [gen\_removal command (vos3)](#packman_cli_gen_removal), [merge command (vos1, vos2, vos3)](#packman_cli_merge) and [list command (all)](#packman_cli_list) allow to use bundle filters to include or exclude some bundles from the processing. The following filter options are available: * **--include\_bundle\_name:** select which bundle names to be included (\*) * **--exclude\_bundle\_name:** select which bundle names to be excluded (\*) * **--include\_bundle\_user:** select which bundle users to be included (\*) * **--exclude\_bundle\_user:** select which bundle users to be excluded (\*) * **--include\_tgt\_devices:** select bundle matching target device models to be included * **--include\_tgt\_dt\_names:** select bundle matching target device tree names to be included * **--include\_tgt\_serial\_numbers:** select bundle matching serial numbers to be included * **--include\_tgt\_hardware\_platforms:** select bundle matching hardware\_platforms to be included * **--include\_arch\_type:** select type of archives to be included (one or more of 'bundle', 'upfile', 'upwd' and 'uvrk') * **--exclude\_arch\_type:** select type of archives to be excluded (one or more of 'bundle', 'upfile', 'upwd' and 'uvrk') (\*) accepts wilcard '\*' to specify globing for the match. All filters can be combined and each accept multiple values separated by spaces. ## Signers The [sign command (all)](#packman_cli_sign) as well most other commands allow to sign the output file as part of its processing. This is done by specifying a signer with the "--signer" (-s) option. Optionally, one can choose which user to sign for with the '--signed\_users' option to target specific device users (eg usr1). For 'vos1' and 'vos2' platforms, signing with development keys/certs will issue PKCS7 (\*.ps7) signatures. For 'vos3' platform, signing with development keys/certs will issue CMS (\*.cms) signatures. The '--cms\_signer' (-c) can be used to specify a specific cms signer. Following sections will describe each signer ### dev signer (all plaforms) The 'dev' signer is used for development signing and can be performed by packman directly using test keys/certs that are shipped with packman. ### local signer (vos1,vos2) The 'local' signer is used for production signing using smartcards and the File Signature Tool (FST). In order to use the 'local' signer: * File Signature Tool (FST) must be running (please refer to FST documentation) * use 'local' signer for signature requests with smartcards approval ### signing portal signer (vos3, titus) The Signing Portal API is used for 'online' signing from packman, primarily for requesting production signatures. Packman uses the Signing Portal API to upload the package to the Verifone Signing Portal to request signing approval and once approval is provided, packman will use the Signing Portal API to download and complete packaging of the signed file. To use packman with the Signing Portal API: To be done once: * Signing Portal user must have token access rights enabled and upload rights to use the Signing Portal API (must be first configured for your account by your Signing Portal administrator) * Signing Portal user logs into Verifone Signing Portal ' creates an [Auth](/s-adk-5.1-programmers-guide/readme/annotated/class_auth.md) token using "Add auth token" in profile / [Auth](/s-adk-5.1-programmers-guide/readme/annotated/class_auth.md) Token. This token is used by packman to access the Signing Portal API. * Copy the complete token value (\~500 characters) and save it to a text file (ie 'mytoken.txt') * Set configuration for the token: 'packman.py config sign.online\_token\_path mytoken.txt' * Copy the signing product ID from the Signing Portal for the signing key to be used for signing. * Set configuration for the signing product ID: 'packman.py config sign.online\_product o3fw8emrARQvXt9pE' With the above done, any command with '**online**' signer specified will use the provided token path and signing product ID. Naturally, you can still use the options '--online\_token\_path' and '--online\_product' to override the values (namely if you use several tokens and/or several products). The signing process can be synchronous (output of current command) or asynchronous (deferred command for result). * If option '--online\_retrieve' is present, synchronous mode will be used: packman will wait for the result of the approval in the Signing Portal for "--online\_timeout" seconds and if the signed package is available it will be automatically downloaded from the Signing Portal. * If option '--online\_retrieve' is absent, asynchronous mode will be used: packman will not wait for the result of the approval and the 'sign\_retrieve' command must be used later to retrieve the result from the Signing Portal. ## User interface ### Start When initially started, the browser window shows the following: ![](/files/RBEoo8lYGaVyJLNoiFxZ) ### Add to catalog To add an archive to the catalog, click on "Add", this will open this dialog: ![](/files/DNfqUhla4OpHjEnHGNk7) Select the archive on your disk, select the type of archive and the platform, then confirm with "Add" button. The newly added archive will appear in the list and can be removed using remove button "X". This operation can be performed several times and the current archive can be selected in the dropdown list. ### Tree view The selected archive from the catalog is shown using a tree view which looks like a file explorer view, you can fold and open directories as well as archives. ![](/files/mxR5Eqi4nZ1czZ5i0Pmz) ### Content view If the currently selected node in the tree has content that packman can display, the content of the file will be shown on the right side of the window. Control files, signatures, images, html, xml, css, etc. can be viewed this way. ![](/files/Ok7JRrtddJJoETLgWMQ6) ### Search The search entry area allows to look for nodes in the tree that contains the entered text. Note that clicking on the node path will bring you directly to the selected node in the tree. ![](/files/Sbv5k1VtvtJPxZtsjnUm) ### Validation report The billboard icon right to the catalog list shows the current number of validation errors, clicking on it will bring up the validation report. ![](/files/uURfhLiQXLRxoj5R70H4) ### Bread crumbs When selecting a node, the complete path of this node (separated by '/') is displayed. Each of these breadcrumbs are clickable to jump to their location. ![](/files/1ujqZrDO0qWezf7AxL9q) ### Create a project In order to edit an archive, select it and click on the 'pen' icon. It will ask for a name for this project archive. This project file must have a name that does not already exist in the catalog. ![](/files/2pC04xG2l3yrmTassMBN) ### Writable nodes Depending on the signer that is currently selected and the chosen signer users, the nodes of a project archive may be modifiable or not. This is shown with lock icons. ![](/files/q3yqcOLYQGa2DVmXJ1fJ) ### Select signer and signer users Choosing a signer is done using the signer dropbox. ![](/files/SUP9n7MhE1hSYbE1YuUB) When a signer has been selected, the icon next to it allows to select the signer users. The users shown are the ones supported by the current signer. Thus for local signer, this is also depending on the currently inserted smartcard. Checking or unchecking users allows to limit the allowed signed users. ![](/files/cqXBoMdZzMPc0gZCJ4Rb) ### Delete selected nodes Nodes can be selected (checkbox) and removed using 'X' button ![](/files/ffOGSGdhhnyVosfsak7Q) ### Undo / redo Operations done to the project can be undone or redone using these buttons. ![](/files/u96kVSXxLe6VxDhxpff7) ### Context menu A context menu is available on nodes for renaming, deleting, ... ![](/files/xr5kkizGKw4baLxcfxPU) ### Edit text file In order to edit text files, select the file (file must be writable) and when content is displayed on the right pane, click on 'edit' button. This allows to modify content and save modified content into selected file. ![](/files/OxJ9SAsWh2GrXRFfzWge) ### Adding files to archive In order to add files to the current project, select the "Add from catalog" from the "Add" button. This will bring the catalog list into the right part of the window for selection and will show treeview too. To add files to the current project, drag and drop the file into the project. ![](/files/UcLTSajrio7CuXaqiL8s) Another way to add a file is to choose "Add from disk". The will bring up a file chooser dialog box to insert it into the tree. ![](/files/QnKbH9TdHyOof2Uatl5q) ### Change permissions Selecting and right-click on node allows to choose "Permissions" that let you choose the permissions to set/unset. ![](/files/PIeO5zNOC1LC5aWm2vrq) ### Exporting The exporting operation will use the current signer and create the resulting archive you edited. Some specific exports are also available which correspond to command line operation. Please refer to [Command line interface](#packman_cli) for more information on their usage. ![](/files/zXbP9Varmrt3OvcyQJ7k) ## Automatic fixes When generating an archive, packman applies automatic fixes on contents that are writable. A content is considered writable when one of the following applies: * content does not involve a signature nor signature of its parent * content involves a signature and selected signer is applicable * special operation where signing is postponed: ie pre\_signingportal Here is the list of automatic fixes: * fix depth-first ordering of archives * fix compression on archives * fix naming of extensions for archives, signature, certificate directory, remove '.' directories * fix filelist presence and content * fix blacklist presence and content * fix order of items in archives * fix permissions on windows * remove permissions on non-executable files * fix VHQ manifest presence and content * fix control file fields like ensuring 'Name' usage in bundle and 'Package' in packages ## Device mode validation (vos3) When validating an archive, packman checks for signature coherency. User can specify four different behaviors explained here: * Specifying "--mode prod", both system and user bundles must be prod signed * Specifying "--mode osdev", both system and user bundles must be osdev signed * Specifying "--mode appdev", system bundles must be appdev signed and user bundles must be osdev signed * Without specifying the mode, one of the below must validate: * one of the above modes is matching * system bundles must be prod and user bundles may be osdev signed: this however triggers a warning that user prod signing is needed --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://sandbox-docs.verifone.com/s-adk-5.1-programmers-guide/readme/developing_applications/packman_users_guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.