Hi,
I am trying to extend openpgp-tool to load data to the various writable DOs,
and - if possible - I want it to determine automatically the permissions of
the (emulated) files using standard interfaces, i.e. security attributes or
preferably ACLs. As the file system on openPGP cards only is e
Hi Peter
I am trying to extend openpgp-tool to load data to the various writable DOs,
> and - if possible - I want it to determine automatically the permissions of
> the (emulated) files using standard interfaces, i.e. security attributes or
> preferably ACLs. As the file system on openPGP cards o
Hi PEter,
thanks for your answer.
On Monday, 28. May 2012, Peter Koch wrote:
> Have a look at "Security Attributes" in ISO 7816-4 and table
> "Access mode byte for EFs".
Unfortunately I do not have access to that either.
But you have me more hints to search the web.
> You may either use compac
> Insisting on changing some hosting situation that has been set up is
> nothing but obnoxious protesting and spitting on the already
> established hosting.
Peter, do you mean that moving OpenSC to GIThub and opening
administration to a group of core developers would be "obnoxious" and
"spitting"
Hello,
On Sun, May 27, 2012 at 11:18 PM, Peter Marschall wrote:
> Hi,
>
> On Friday, 25. May 2012, Martin Paljak wrote:
>
>> In the long run, I don't think that it helps to emulate a filesystem
>> on top of non-filesystem cards (like OpenPGP or Muscle). Or to try to
>> make it fit into the filesy
Hello,
On Mon, May 28, 2012 at 11:10 AM, Peter Marschall wrote:
> I am trying to extend openpgp-tool to load data to the various writable DOs,
> and - if possible - I want it to determine automatically the permissions of
> the (emulated) files using standard interfaces, i.e. security attributes o
Hi,
On Monday, 28. May 2012, Martin Paljak wrote:
> I don't really understand how you would use ACL-s with the "gender"
> field, for example.
Let me try to explain what I want to achieve.
card-openpgp.c emulates a filesystem for the DOs on the card.
Now, some of the DOs are
* readable after VER
Hi,
On Monday, 28. May 2012, Martin Paljak wrote:
> > If it works (even in a limited/restricted way), it is better than not
> > having any support at all.
>
> Sure. If this can be accomplished without changing the underlying
> mechanics/assumptions, perfect.
That's what we try to achieve with ope
On Monday, May 28 at 01:34PM, Peter Marschall wrote:
>
> Hi PEter,
>
> thanks for your answer.
>
> On Monday, 28. May 2012, Peter Koch wrote:
> > Have a look at "Security Attributes" in ISO 7816-4 and table
> > "Access mode byte for EFs".
>
> Unfortunately I do not have access to that either.
>
On Sun, May 27, 2012 at 11:59 PM, Peter Stuge wrote:
> Jean-Michel Pouré - GOOZE wrote:
> > What I suggest is that OpenSC should be hosted on GIThub with write
> > access to core developers (at least 5/6 people).
>
> Insisting on changing some hosting situation that has been set up is
> nothing b
Hi Peter,
Does this
pgp2_objects[] = {/* OpenPGP card spec 2.0 */
{ 0x004d, CONSTRUCTED, READ_NEVER | WRITE_PIN3,
NULL, sc_put_data },
{ 0x004f, SIMPLE, READ_ALWAYS | WRITE_NEVER,
sc_get_data,NULL},
{ 0x005b, SIMPLE, READ_ALWAYS | WRITE_PI
11 matches
Mail list logo