PCSC Smart Cards Library
The purpose of PCSC Lite is to provide a Windows(R) SCard interface in
a very small form factor for communication with smart cards and
readers. PCSC Lite can be compiled directly for a desired reader driver
or can be used to dynamically allocate/deallocate reader drivers at
runtime (the default behavior).
PCSC Lite uses the same winscard API as used in Windows(R).
Security aware people should read the SECURITY file for possible
vulnerabilities of pcsclite and how to fix them. For information on how
to install drivers please read the DRIVERS file.
Memory cards will be supported through the MCT specification, which is
an APDU like manner sent normally through the SCardTransmit() function.
This functionality is exercised in the driver.
- Developed at security:chipcard
-
5
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory/pcsc-lite && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| README.SUSE | 0000000106 106 Bytes | |
| pcsc-lite-1.4.3-64bit-compat2.patch | 0000082491 80.6 KB | |
| pcsc-lite-1.4.3.tar.bz2 | 0000464038 453 KB | |
| pcsc-lite.changes | 0000011955 11.7 KB | |
| pcsc-lite.spec | 0000011552 11.3 KB | |
| pcscd.init | 0000001588 1.55 KB | |
| pre_checkin.sh | 0000000713 713 Bytes | |
| ready | 0000000000 0 Bytes |
Revision 7 (latest revision is 104)
unknown
committed
(revision 7)
Comments 9
Hello. systemd isn't required for operation of pcscd, I propose systemd being moved as a recommendation instead. A container wouldn't need systemd to use pcsc-lite for instance.
You are most likely right. Almost no daemon requires systemd. On the other hand the whole integration is based on systemd with socket activation and stuff. As this seem to be some sort of new requirement and potentially affects many packages can you point me to an example of a package which works as you suggested? Or a pointer to the packaging guidelines where there are hints about that?
I found a single package which looking at the .spec it doesn't seem to require systemd directly (although requires it indirectly): gdm-systemd. It's not even a recommended package though, so not the same thing.
The guidelines talk about %{?systemd_requires} 1. I wouldn't be surprised if I'm the first to install a daemon on an openSUSE container. We have to catch up on this trend.
Solutions:
1) Use %systemd_ordering instead 2; 2) Split the package to pcsc-lite-systemd, which requires systemd and provides the systemd unit file(s) 3. Existing installs should pick up the new package automatically. The subpackage would then be recommended for new installs. And containers won't have it.
Whether for desktops, servers or containers, either option works.
Thanks for considering it!
Links: - https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines - https://lists.freedesktop.org/archives/systemd-devel/2016-July/037220.html - https://en.opensuse.org/openSUSE:Package_dependencies#Splitting_off_a_sub-package
For completeness, talk from another community 1. Removing systemd as a requirement (in all packages that don't absolutely need it) free us from discussing a need for a fakesystemd 3.
Dammit, missing link: https://pagure.io/packaging-committee/issue/644
ok, removing the dependency on systemd might be possible but actually the pcscd actually currently is using libsystemd. So actually this would require two different variants one with and one without libsystemd support!?
pcsc-lite-lite? Probably we wouldn't like to have that. Unless openSUSE creates a release targeted at containers, I guess keeping libsystem0 is a good compromise. Keeping systemctl out of the image is progress (for containers of course).
Hello again, I just noticed that there's new official guidance, just in time ;) https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines#Requirements