Ticket #71 (new enhancement)

NB! Read about ReportingBugs before filing a ticket!

Opened 6 years ago

Last modified 2 years ago

pkcs15-tool --dump/-D should also show the profile used.

Reported by: martin Owned by: opensc-devel@…
Priority: low Milestone: 0.13
Component: tools Version: trunk
Severity: normal Keywords: newcomer
Cc: Blocked By:
Blocking:

Description

See  http://www.opensc-project.org/pipermail/opensc-user/2006-February/000825.html

Change History

comment:1 Changed 6 years ago by martin

  • Milestone set to 0.11.2

comment:2 Changed 2 years ago by martin

  • Milestone 0.11.7 deleted

Milestone 0.11.7 deleted

comment:3 Changed 2 years ago by martin

  • Keywords newcomer added
  • Priority changed from normal to low
  • Version changed from 0.10.1-rc1 to trunk
  • Component changed from opensc to tools
  • Milestone set to 0.13

comment:4 Changed 2 years ago by viktor.tarasov@…

Do we really need it in pkcs15-tool? No actions in this tool that need knowledge of profile; 'profile' concept is absent in PKCS#15 specification; 'profile' is used only in pkcs15init part;

Path to OPENSC_INFO is actually known only in pkcs15init, as well as procedure to parse it's content is static procedure in pkcs15-lib.c .

For me it's not logical to implement it in pkcs15-tool. It can be done in pkcs15-init, but, afaik, for a moment, 'pkcs15-init' tool have no 'info' actions -- only the 'init' ones.

Note: See TracTickets for help on using tickets.