Package Details: eszig 1.7.3-1

Git Clone URL: https://aur.archlinux.org/eszig.git (read-only, click to copy)
Package Base: eszig
Description: eSzemelyi Kliens, Hungarian personal electronic ID card software client
Upstream URL: https://eszemelyi.hu/
Licenses: custom
Submitter: imrehg
Maintainer: Ambr051us
Last Packager: Ambr051us
Votes: 5
Popularity: 0.24
First Submitted: 2018-01-27 11:15 (UTC)
Last Updated: 2024-01-08 12:50 (UTC)

Latest Comments

Ambr051us commented on 2024-01-08 13:14 (UTC)

Updated to latest version. I also tested the dynamic linking approach suggested by @kris7t and found that the app launches successfully with its local Qt5 and OpenSSL library files removed, but there's a catch. When the system is set to a dark theme, most text is invisible in the eSzemelyi GUI. I'm not familiar with the inner workings of Qt, but I'm guessing that this app hard-codes some colors while leaving others at their default values, resulting in white-on-white or black-on-black text in most UI elements. Using more up-to-date libraries at the expense of breaking the GUI for everyone using dark mode is not a worthy trade-off IMO. I could publish a modified version under a different name with the included libraries deleted, but removing them from /usr/lib/ESZEMELYI/ after installation achieves the same result.

kris7t commented on 2023-08-11 14:20 (UTC) (edited on 2023-08-11 23:11 (UTC) by kris7t)

A new version 1.7.3 is available from https://eszemelyi.hu/letoltesek/

diff --git a/PKGBUILD b/PKGBUILD
index 4fd6bf3..f57e844 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,16 +1,16 @@
 # Maintainer: Gergely Imreh <imrehg@gmail.com>
 pkgname=('eszig')
-pkgver=1.6.30
+pkgver=1.7.3
 _pkgver=$(echo ${pkgver} | sed -r 's/\./_/g')
-pkgrel=2
+pkgrel=1
 pkgdesc="eSzemelyi Kliens, Hungarian personal electronic ID card software client"
 arch=('x86_64')
 license=('custom')
 url="https://eszemelyi.hu/"
 depends=('pcsclite' 'qt5-base')
-source=(https://eszemelyi.hu/letoltesek/eSzemelyi_Kliens_x64_${_pkgver}.deb
+source=(https://eszemelyi.hu/wp-content/uploads/2023/05/eSzemelyi_Kliens_x64_${_pkgver}.deb
         https://eszemelyi.hu/wp-content/uploads/2021/09/eSzemelyi_Kliens_vegfelhasznaloi_nyilatkozat_v13.pdf)
-sha256sums=('50321a36afe81a0c14f0182eb79a925ef1c44af1ab7418312591aaa00d6f6949'
+sha256sums=('9fd36ac71eb81b057735e86fb872bd8faf9f5299410a82d96d0a793c03928622'
             '518d83d0702051bc7e82f29ccb29504aa14104a0f006a19c3c25b8c78313c5c5')

 package() {

Also, removing the qt5 libraries from the installation directory (imageformats, platforms, and Qt5 directories) would enable dynamically linking with newer Qt5 libraries from the Arch repos. This should be allowed as per the LGPL3.0 license of Qt5, and would considerably improve security by allowing the use of Wayland instead of X11 (the embedded Qt5 version doesn't support the Wayland QPA).

In theory, removing libcrypto.so and libssl.so would also enable dynamically linking with openssl-1.1 from the Arch repos to further improve security. However, I'm not sure if this would actually be allowed by the EULA.

imrehg commented on 2022-04-02 06:32 (UTC)

Fixed it up, sorry for the delay, @imr0

imr0 commented on 2021-08-06 09:24 (UTC)

Hey, please change the version number in the végfelhasználói nyilatkozat PDF.

 install -m644 -D "${srcdir}/eSzemelyi_Kliens_vegfelhasznaloi_nyilatkozat_v13.pdf" \
"${pkgdir}/usr/share/licenses/eszig/eSzemelyi_Kliens_vegfelhasznaloi_nyilatkozat_v13.pdf"

should be the correct line at the bottom of the PKGBUILD.

merlin16 commented on 2019-04-20 08:28 (UTC) (edited on 2019-04-20 08:32 (UTC) by merlin16)

Hi, please update the PKGBUILD with the info from https://eszemelyi.hu/letoltesek.

Changes needed for new version to build successfully (users can do this in the meantime manually):

pkgver=1.5.19

sha256sums=('5a0ba682d39c1681a72668ee52b060f970d333cf1600850b776943229034bd79' '4670589538ea4d86d02fec2565653a36c2bfb4bc09751c1b7a3548def176a9da')

Also, please note that if the card reader is not recognized first (and pscsd is already installed), you should try to connect it via an USB 2 port on the rear I/O of the motherboard (and re-start the application).

Thank you!