pyCertWiz 2.0.1__tar.gz

pycertwiz-2.0.1/CHANGELOG.md

@@ -0,0 +1,198 @@
+# Changelog
+
+## 2.0.1
+
+### Fixed
+
+- Every request to the UK CA looked up this computer's full name for the
+  `LocalHost` header, a reverse DNS lookup that takes seconds where reverse
+  DNS is slow. It is now looked up once per run. On GitHub's macOS runners
+  this made the test suite crawl until it timed out.
+
+## 2.0.0
+
+**pyCert is now pyCertWiz.** The distribution (`pip install pyCertWiz`), the
+application and the GitHub repository (rob-c/pyCertWiz) carry the new name, and
+a `pycertwiz` command joins `pycert`. Nothing else moves: the `pycert` command,
+the `pycert` Python package, the configuration and data folders
+(`~/.config/pycert`, `~/.local/share/pycert`) and the Keychain/Secret Service
+entry (`pyCert`) keep their names, so existing installations carry on working.
+
+pyCertWiz becomes a manager for many personal and host certificates from several
+CAs, with a new desktop application.
+
+### New
+
+- **Qt desktop application** (`pip install 'pyCertWiz[gui]'`, PySide6). It
+  replaces the Tkinter GUI and includes:
+  - a sidebar with views and per-CA reachability, summary cards, and
+    renewal/unreachable banners;
+  - a sortable, searchable table with status pills and days-left bars;
+  - a detail panel with Overview, Chain, Deployment and History tabs;
+  - a request wizard that adapts to the CA and requests many host names at
+    once;
+  - background collection of issued certificates, with tray/menu-bar
+    notifications;
+  - the Java bundle inspector;
+  - live light/dark appearance.
+
+  It is tested headless with pytest-qt.
+- **Several CAs per configuration.** `[ca]` is the primary profile and
+  `[cas.<name>]` tables add more. `default_ca` chooses the profile for new
+  requests, and each request records its CA. Manage profiles with
+  `pycert ca list|show|default|add-acme|add-ukca|remove|eab` or the GUI
+  settings.
+- **CA provider interface** (`pycert.providers`). It has two built-in
+  providers, `ukca` (the CertWizard protocol, unchanged on the wire) and
+  `acme`, plus third-party providers through the `pycert.providers` entry
+  point.
+- **ACME client** (RFC 8555) on pyCertWiz's hardened transport:
+  - accounts, External Account Binding, and http-01 (standalone or webroot)
+    or dns-01 (hook or manual) validation;
+  - wildcards with dns-01, renewal, revocation, crash-safe resumption of
+    orders, and cancellation;
+  - tested end to end against the sandbox ACME server.
+- **Java keystores as a live store** (`pycert keystore link|list|sync|password|unlink|import`,
+  GUI *Link a Java keystore…* and the bundle inspector's *Use as certificate
+  store…*):
+  - every key entry of a CertWizard `cakeystore.pkcs12` (or a modern keytool or
+    OpenSSL keystore) is managed by pyCertWiz;
+  - issued and renewed certificates are written back, while other entries stay
+    byte-for-byte unchanged;
+  - certificates renewed elsewhere are picked up, and CertWizard's pending
+    requests are finished by pyCertWiz.
+- **Private keys are never written unprotected.** Deployed keys and bundles
+  and proxy bundles use the saved secret or a passphrase you choose; exports
+  and `~/.globus/userkey.pem` need a new passphrase (see below). A single
+  exported key file may be left without a passphrase only after an
+  interactive confirmation (type `unencrypted`); bundles never.
+- **Exports in many formats, always with a new passphrase**:
+  `pycert export --format p12|pem-bundle|pem-files|key|cert|fullchain|der|p7b`
+  and `--encryption aes256|3des|pkcs8|traditional`, and an **Export…** dialog
+  in the GUI. PKCS#12 with AES-256 is the default. Anything with a private key
+  needs a new passphrase of at least 8 characters, entered twice; pyCertWiz's
+  saved secret is refused. `pycert install` follows the same rule.
+  `pycert export --stored` re-writes pyCertWiz's own copy (the old default
+  behaviour). See [docs/EXPORTING.md](docs/EXPORTING.md).
+- **Rename certificates**: `pycert edit ALIAS --name NEW`, and **Rename…** (F2)
+  in the GUI. With `--rename-keystore-entry`, or the checkbox, the linked
+  Java keystore entry is renamed too.
+- **Certificate, keys and chain viewer** in the GUI (Ctrl/Cmd+K): the full
+  chain with details and PEM, the public key, and the private key on request
+  (type `show`; never copied; cleared on close).
+- **User/host type is shown** in the certificate list (the Type column is on
+  by default) and in the details.
+- **Keystore passphrases are never stored.** They are asked for each session
+  (the GUI asks at start-up), and locked keystores are reported by
+  `pycert check`.
+- **Bulk host requests**: `pycert request h1 h2 … --type host` or
+  `--from-file hosts.txt`.
+- **Deployment targets** (`pycert deploy list|add|remove|run|presets`, and in
+  the GUI):
+  - presets for grid-host, globus-user, nginx and Apache, or custom
+    paths;
+  - atomic writes with explicit modes, owner/group, `.bak` backups, symlink
+    refusal and reload hooks;
+  - automatic re-deployment after issuance and renewal.
+- **Monitoring**:
+  - `pycert check` is a Nagios/Icinga plugin (exit 0/1/2/3). It reports
+    expiry, requests stuck at the RA, failed requests, unverified chains and
+    deployment drift.
+  - `pycert report` exports an inventory as a table, CSV or JSON.
+  - `pycert doctor` now checks deployments and every CA.
+- `pycert edit ALIAS --description … --auto-renew/--no-auto-renew`;
+  `pycert renew --due` honours the flag and accepts `--ca` and
+  `--include-manual`.
+- `pycert ping --all` / `--ca`, and `pycert info --ca` (ACME directory
+  metadata).
+- Optional **`keyring` secret backend** (`pip install 'pyCertWiz[keyring]'`).
+- `PYCERT_GUI_SETTINGS` keeps GUI preferences in an INI file;
+  `XDG_CONFIG_HOME` is searched for the configuration.
+- GitHub Actions CI on Linux and macOS for Python 3.10–3.14. The test suite
+  runs in parallel (`pytest -n auto`).
+- **Packages** that carry their own Python and Qt: a macOS app in a `.dmg`
+  (Apple silicon and Intel), and for Linux an AppImage, `.deb`, `.rpm` and
+  Arch package (x86_64 and aarch64), plus a Nix flake. They add a desktop
+  entry, and the bundled executable is both the GUI and the command line.
+  Each package is installed in clean containers of eleven distributions and
+  tested end to end against the sandbox CA, including the GUI on X11. Tagged
+  releases are published to GitHub Releases, with checksums and build
+  provenance, and to PyPI. See [docs/PACKAGING.md](docs/PACKAGING.md).
+- **First-run setup in the GUI.** With no configuration yet, the desktop
+  application asks for the e-mail address, RA and where to keep the saved
+  secret, and writes the same files as `pycert init`, which now shares its
+  code. `pycert gui --check` renders a window once and exits, for package
+  tests.
+
+### Changed
+
+- **Renewals start from the CA's record, as in CertWizard.** Before a UK-CA
+  renewal pyCertWiz looks the certificate up by its public key. It refuses
+  certificates the CA does not report as VALID, or that expired more than 30
+  days ago, and checks any e-mail in the name against the one being sent. All
+  of this happens before a key is generated. The contact e-mail defaults to
+  the one the CA holds (previously the local or configured address); changing
+  it is reported. Imported certificates get their record from
+  `pycert status --refresh`, **Check now** or the GUI's background check.
+- The sandbox CA issues subjects in production order (C, O, OU, L, CN) and
+  challenges with the production PPPK realm.
+
+- **Python 3.10+ is required** (was 3.6+). The hand-written TOML parser, the
+  dataclasses backport and the compatibility layer have been removed in favour
+  of `tomllib`/`tomli`, `dataclasses` and current `cryptography` (≥ 42) APIs.
+- Packaging moved to PEP 621 metadata in `pyproject.toml` (`setup.cfg`
+  removed). Extras: `gui`, `keyring`, `all`, `dev`.
+- Configuration format version 2. Version 1 files load unchanged; `[ca]` gains
+  `name` and `display_name`.
+- Request state version 2 adds `ca`, `provider`, `deploy`, `auto_renew` and
+  `description`. Older state files are read as before.
+- Example automation now uses `pycert watch --once` (collect and deploy). New
+  examples cover ACME renewal timers, Nagios/NRPE and cron.
+
+### Fixed
+
+- With PySide6 older than 6.10 (for example 6.9 on RHEL/AlmaLinux 8) every
+  change of view or search in the GUI failed: Qt 6.9 has `beginFilterChange()`
+  but not `endFilterChange()`. Both are now required, with a fallback.
+- On current Fedora, pyCertWiz found no system trust anchors: OpenSSL there is
+  configured with a hashed CA directory only, which Python does not list. ACME
+  chains (Let's Encrypt and others) could therefore not be validated against
+  system trust. pyCertWiz now falls back to the distribution's CA bundle
+  (`$SSL_CERT_FILE`, then the usual Fedora/RHEL, Debian/Ubuntu/Arch, openSUSE
+  and BSD locations).
+- A deploy or dns-01 hook whose program is missing or not executable is now
+  reported as such ("deploy hook not found", "could not be run (not
+  executable)") on every platform; under emulation the exec error could be
+  lost, leaving only "exit 127".
+
+- The GUI crashed (segmentation fault) when the appearance changed after the
+  new-certificate wizard had been opened and a background CA check had run.
+  Wizards and dialogs are now disposed after use instead of living on as
+  hidden children of the main window.
+- CertWizard's pending-request placeholders (`<CN> CSR cert`) were imported
+  as *user* certificates with that CN. A host renewal collected that way
+  would have been renewed later with an extra e-mail SAN. The real CN and
+  type are now used, and the issued certificate corrects older imports.
+- Exporting onto a path that is a folder failed with a raw `IsADirectoryError`;
+  write failures are now reported clearly.
+
+- `pycert request --key-algorithm/--rsa-bits/--ec-curve`, and the GUI key
+  choice, were silently ignored for new requests; the configuration defaults
+  were always used. They are now honoured, and pyCertWiz warns that the UK
+  e-Science CA cannot renew EC certificates in place.
+- A host request with extra `--san-dns` names no longer omits the host's own
+  name from the SANs.
+- The GUI's busy indicator could clear before a background result had been
+  delivered.
+- A PKCS#12 bundle whose certificates are encrypted with PBES2 (modern keytool,
+  OpenSSL 3) lost all but its first key entry when re-saved from the bundle
+  inspector.
+- Writing a file re-moded its existing parent directory to 0700. This affected
+  deployment to `/etc/grid-security`, ACME webroots, and `export --out`.
+- A failing secret backend (locked keychain, failing password-manager command)
+  could make pyCertWiz generate and save a new passphrase.
+
+### Removed
+
+- The Tkinter GUI. `pycert gui` and `pycert-gui` start the Qt application.
+- Python 3.6–3.9 support, `tools/check_py36.py` and the `vermin` check.

pycertwiz-2.0.1/LICENSE

@@ -0,0 +1,339 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+                            NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License along
+    with this program; if not, write to the Free Software Foundation, Inc.,
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.

pycertwiz-2.0.1/MANIFEST.in

@@ -0,0 +1,5 @@
+include README.md SECURITY.md CHANGELOG.md LICENSE Makefile pyproject.toml
+recursive-include docs *.md
+recursive-include examples *
+recursive-include tests *.py
+recursive-include src/pycert/data *.pem

pycertwiz-2.0.1/Makefile

@@ -0,0 +1,84 @@
+PYTHON ?= python3
+VENV ?= .venv
+BIN := $(VENV)/bin
+JOBS ?= auto
+
+.PHONY: help venv install dev test test-serial coverage lint format check selftest gui screenshots build package-macos package-linux package-test clean
+
+help:
+	@echo "make venv         create the virtualenv and install pyCertWiz (editable, with the GUI)"
+	@echo "make dev          venv + test tooling (pytest, pytest-qt, pytest-xdist, ruff, build)"
+	@echo "make test         run the test suite in parallel (JOBS=auto)"
+	@echo "make test-serial  run the test suite in one process"
+	@echo "make coverage     full suite with the 100% line and branch coverage gate (GUI included)"
+	@echo "make lint         ruff check"
+	@echo "make format       ruff format + autofix"
+	@echo "make check        lint + test"
+	@echo "make gui          start the desktop application"
+	@echo "make screenshots  regenerate docs/images against a throw-away sandbox CA"
+	@echo "make build        build a wheel and sdist in dist/"
+	@echo "make package-macos   pyCertWiz.app and a .dmg for this Mac, in dist/"
+	@echo "make package-linux   Linux bundle, AppImage, .deb, .rpm, Arch package (Docker; ARCH=x86_64|aarch64)"
+	@echo "make package-test    install the Linux packages in clean containers and test them (IMAGE=, FORMAT=)"
+	@echo "make clean        remove caches and build artefacts"
+
+venv:
+	$(PYTHON) -m venv $(VENV)
+	$(BIN)/pip install --upgrade pip
+	$(BIN)/pip install -e ".[gui]"
+
+dev: venv
+	$(BIN)/pip install -e ".[dev]"
+
+install: venv
+
+test:
+	QT_QPA_PLATFORM=offscreen $(BIN)/pytest -n $(JOBS)
+
+test-serial:
+	QT_QPA_PLATFORM=offscreen $(BIN)/pytest
+
+coverage:
+	QT_QPA_PLATFORM=offscreen $(BIN)/pytest -n $(JOBS) --cov=src/pycert --cov-report=term-missing --cov-fail-under=100
+
+lint:
+	$(BIN)/ruff check src tests sandbox_ca
+
+selftest:
+	$(BIN)/pycert selftest
+
+format:
+	$(BIN)/ruff format src tests sandbox_ca
+	$(BIN)/ruff check --fix src tests sandbox_ca
+
+check: lint test
+
+gui:
+	$(BIN)/pycert gui
+
+screenshots:
+	QT_QPA_PLATFORM=offscreen $(BIN)/python tools/screenshots.py docs/images
+
+build: dev
+	$(BIN)/python -m build
+
+package-macos:
+	packaging/macos/build-app.sh
+
+# Docker builds for this machine's architecture; ARCH=x86_64 on Apple silicon emulates.
+ARCH ?= $(shell uname -m | sed 's/arm64/aarch64/')
+BUILD_IMAGE = $(if $(filter aarch64,$(ARCH)),almalinux:10,almalinux:8)
+DOCKER_PLATFORM = $(if $(filter aarch64,$(ARCH)),linux/arm64,linux/amd64)
+package-linux:
+	docker run --rm --platform $(DOCKER_PLATFORM) -v "$(CURDIR):/src" -w /src $(BUILD_IMAGE) packaging/linux/build.sh
+	docker run --rm --platform $(DOCKER_PLATFORM) -v "$(CURDIR):/src" -w /src ubuntu:24.04 sh -c \
+		'apt-get update -qq && apt-get install -y -qq curl ca-certificates binutils file >/dev/null && packaging/linux/package.sh $(ARCH)'
+
+IMAGE ?= debian:13
+FORMAT ?= deb
+package-test:
+	packaging/tests/container-test.sh $(IMAGE) $(FORMAT)
+
+clean:
+	rm -rf $(VENV) dist build *.egg-info src/*.egg-info .pytest_cache .ruff_cache .coverage htmlcov
+	find . -name __pycache__ -type d -prune -exec rm -rf {} +