Github messages for voidlinux
 help / color / mirror / Atom feed
From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Building pcsclite with polkit enabled causes problems for existing setups.
Date: Mon, 27 Nov 2023 09:23:09 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47426@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]

New issue by dataCobra on void-packages repository

https://github.com/void-linux/void-packages/issues/47426

Description:
### Is this a new report?

Yes

### System Info

Void 6.5.12_1 x86_64 AuthenticAMD uptodate FFFFFF

### Package(s) Affected

pcsclite-2.0.1_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://bbs.archlinux.org/viewtopic.php?id=286779
https://github.com/drduh/YubiKey-Guide/issues/376

### Expected behaviour

The package works like before the update to 2.0.1 without manual adjustment/configuration.

### Actual behaviour

Non-root users are no longer able to use the functionality of pcsclite when not installing elogind because the polkit policy which is packaged with pcsclite does only work when polkit recognizes a session as active which is only possible with elogind.

There is a workaround when manual creating a separate rules file for polkit if someone doesn't want to install elogind.

### Steps to reproduce

1. Update to pcsclite 2.0.1. (Make sure elogind or seatd is not installed)
2. Try to execute pcsc_scan or scdaemon via gnupg.
3. Get informed about denied access.

             reply	other threads:[~2023-11-27  8:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27  8:23 dataCobra [this message]
2023-11-27  8:25 ` dataCobra
2023-11-27 22:20 ` 0x5c
2023-11-27 23:32 ` dataCobra
2023-11-29  6:28 ` dataCobra
2023-11-29 15:20 ` [ISSUE] [CLOSED] " abenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47426@inbox.vuxu.org \
    --to=datacobra@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).