>> now's the time to go off and start committing code.
>
> hope you are kidding.. I'm not even finished to collect all the
> information and ideas, then i need to crunch them up, come out with a
> protocol schema, check with whatever is interested if sound..
Nope. Not kidding.
The first version
I understand what you say, but for now I'm still thinking if use a
certificate for lvl1 or a key.. For sure in the next days I want to produce
a basic schematic of the system, protocol, expected workflow..
I already attempted something but so far I always changed idea halfway
thought.
On Fri, Sep
On 14/09/17 07:26, NIIBE Yutaka wrote:
> Philip Jackson wrote:
>> I have the log file which I attach.
>>
>> It shows a number of reports of the same error (lines 89,91,97,99,101)
>> ERR 83886254 Unknown option , before it asks me for the pin
>> (line 111). It says 'confidential data not shown' t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/09/17 23:53, Philip Jackson wrote:
> Card status seems to be ok :
>
> gpg --card-status
> Application ID ...: D2760001240102052870
> Version ..: 2.0
> Manufacturer .: ZeitControl
> Serial number : 2870
> Name of
On 15.09.2017 10:52, Robert J. Hansen wrote:
> Often, the best way to begin learning how to do something is to go out
> and do it.
While I have nothing against (rapid) prototyping in general, it is not
the advisable method for each and every project or person. I prefer
spending time designing sof
> While I have nothing against (rapid) prototyping in general, it is not
> the advisable method for each and every project or person.
Enthusiastically agreed.
> This, of course, should best be discussed elsewhere. ;-)
This, as well. :)
___
Gnupg-user
Philip Jackson wrote:
> I created the scdaemon.conf file as you suggested and then ran a decrypt
> test :
Thank you.
> Perhaps there is something you can see which explains the problem ?
As far as I can see, it looks like no problem of scdaemon, but card
failure.
Here is the decrypt operation
