#3187 Enrollment is successful when there is no read permission to the applet file
Closed: migrated 3 years ago by dmoluguw. Opened 3 years ago by dmoluguw.

Description of problem:

Enrollment is successful when there is no read permission to the applet file

Version-Release number of selected component (if applicable):

pki-tps-10.4.1-10.el7pki.x86_64

How reproducible:

always

Steps to Reproduce:

  1. [root@nocp1 ~]# chmod 000 /usr/share/pki/tps/applets/1.4.58768072.ijc
  2. Enroll a smartcard token

Actual results:

Enrollment is successful

Expected results:

Enrollment should fail when trying to use the applet version

Additional info:

Format operation fails.

[07/Sep/2017:16:01:31][http-bio-25080-exec-12]: TPSProcess.getAppletMemorySize: returning: 5000
[07/Sep/2017:16:01:31][http-bio-25080-exec-12]: TPSProcessor.getChannelDefKeyVersion: 0
[07/Sep/2017:16:01:31][http-bio-25080-exec-12]: TPSProcessor.getChannelDefKeyIndex: 0
[07/Sep/2017:16:01:31][http-bio-25080-exec-12]: TPSProcessor.getAppletDirectory: getting config: op.format.userKey.update.applet.directory
[07/Sep/2017:16:01:31][http-bio-25080-exec-12]: getAppletDirectory: returning: /usr/share/pki/tps/applets
[07/Sep/2017:16:01:31][http-bio-25080-exec-12]: TPSProcessor.upgradeApplet: applet target directory: /usr/share/pki/tps/applets
[07/Sep/2017:16:01:31][http-bio-25080-exec-12]: TPSProcessor.getAppletExtension: returning: ijc
[07/Sep/2017:16:01:31][http-bio-25080-exec-12]: TPSProcessor.upgradeApplet: targe applet file name: /usr/share/pki/tps/applets/1.4.58768072.ijc
[07/Sep/2017:16:01:31][http-bio-25080-exec-12]: TPSProcessor.getAppletFileData: IOException java.nio.file.AccessDeniedException: /usr/share/pki/tps/applets/1.4.58768072.ijc
[07/Sep/2017:16:01:31][http-bio-25080-exec-12]: TPSSession.process: IO error happened during processing: java.nio.file.AccessDeniedException: /usr/share/pki/tps/applets/1.4.58768072.ijc

Metadata Update from @dmoluguw:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1489588
- Custom field type adjusted to None
- Custom field version adjusted to None

3 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/3304

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata