kiran-authentication-devices-devel-2.5.2-3.oe2203sp4,>   f{ ;G|`u`  };(-]RSK˟݌L&p % SDD81<8^QULeyq]J7ҡ% 4(qqY퍯бCC6tqnPyYVh۩(tk &V={bpN8̦W5c7 9^:\\,I Zz'RF˕y!<(qmo6{{ 09O~J[m47gPnDFFk@Cل觅W?mT&'``GUǖ-W2po~e߷;=8K;f9{Ἕ:r \t  C5>uiqmTXnbZ*33f779254e5e8d860f8f56504e1545b051bc0b80b1c4ef7d65601a47c166a568d146f1622ef5b10f590e27bbfdcdd9e64719fd035eGo|%k_Hu>9M?=d%+ 7 j     E HLQVx(8 9 :: F G H I X Y \ ] ^ b IdIeNfQlStputvxzCkiran-authentication-devices-devel2.5.23.oe2203sp4Development files for kiran authentication devicesDevelopment files for kiran authentication devicesf{dc-64g.compass-ci MulanPSL-2.0http://openeuler.orgUnspecifiedlinuxx86_64 d051a0b0e9ba322947421c21fcf7c5f22ae597353a7e897f63fa550ffc14066a5rootrootkiran-authentication-devices-2.5.2-3.oe2203sp4.src.rpmkiran-authentication-devices-develkiran-authentication-devices-devel(x86-64)    kiran-authentication-devicesrpmlib(CompressedFileNames)rpmlib(FileDigests)rpmlib(PayloadFilesHavePrefix)rpmlib(PayloadIsXz)2.5.2-3.oe2203sp43.0.4-14.6.0-14.0-15.2-14.17.0ed@d dNdydydm@dm@dBzdBzdA)@d?d*luoqing - 2.5.2-3yinhongchang - 2.5.2-2luoqing - 2.5.2-1luoqing - 2.5.1-5luoqing - 2.5.1-4luoqing - 2.5.1-3luoqing - 2.5.1-2luoqing - 2.5.1-1wangyucheng - 2.5.0-5wangyucheng - 2.5.0-4luoqing - 2.5.0-3luoqing - 2.5.0-2luoqing - 2.5.0-1- KYOS-B: Fixed a crash caused by repeatedly calling disConnectDev in resetUkey and destructor to release the same device handle - KYOS-R: Modify the code according to the https://gitee.com/openeuler/kiran-authentication-devices/pulls/17 review opinions - KYOS-B: when the iris face integrated device is removed, the memory cannot be released and the process is blocked.When the face iris device object is removed, restart the service to release resources (#25243) - KYOS-B: When the driver is enabled, the device is scanned and the corresponding device object is created.When the driver is disabled,the corresponding device object is released. (#25387) - KYOS-B: fix file install path error- KYOS-F: fix QUuid::WithoutBraces for qt low version- KYOS-F: Fixed an issue where fish's UKey device could not Verify on arm machines - KYOS-F: Remove the context class; - KYOS-F: ConfigHelper is responsible for obtaining device configuration information based on the id, and DeviceCreator is responsible for creating the device； - KYOS-F: After the vid and pid are obtained, the configuration file is read. The driver name in the configuration file can generate the specific driver object and device object- KYOS-F: Fix the issue of duplicate binding of the same UKey device (#I78P3F)- KYOS-F: Fix the issue of not obtaining features from the database when deviceSerialNumber is empty- KYOS-F: Fix the issue where only one ukey can be bound to a device, some self-test bugs.(#I78P3F)- KYOS-F: fix compilation issues with std:: function in lower versions.- KYOS-F: add Ukey management tool. - KYOS-F: added iristar device , supporting iris and facial enroll and identify. - KYOS-F: fix some defects.- KYOS-F: fix ld error: undefined reference to symbol 'dlclose@@GLIBC_2.2.5'.- KYOS-F: qt5 cmake command compatible.- KYOS-F: Add libusb dependency.- KYOS-F: The UKey device is adapted.- Inital builddc-64g.compass-ci 17193419992.5.2-3.oe2203sp42.5.2-3.oe2203sp4kiran-auth-device-i.h/usr/include/kiran-authentication-devices/-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/generic-hardened-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection cpioxz2x86_64-openEuler-linux-gnuC source, Unicode text, UTF-8 textq[Ub|Y*wutf-874777c45fda97045cbbb873623d541923bdedaac2094b6724a734bee503dfb00e8621cf32b7136071aa6c388eb5df98ab78a3a2ab09e5df0f3642ad00f0d0bc4?p7zXZ !#, ] b2u Q{LVO.IIr9-F>HhzɗWrruq5dٔsG*5ƏGUN%#6֞Z.-$62#PKa~؎8ی$۱שFC_>yU7Zk*fsnm+4B^C:VKdM{{-bp% %jRpgyC/B,7Bٻv2P! QQE !:yju/DjA^+;K"Up un 6ʂZi0eᜠ吵y݁Ϭ~,@ȋHd0wupH8KU\F(K)bÛzrT KW?g]o̺ A>tv[_q qh^+1b+q6È]:*]d*  ޏ YZ