Project

General

Profile

Actions

Feature #1794

closed

Make KeyChain use PIB Service

Added by Yingdi Yu over 10 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Security
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Implement SecPublicInfo interface to use PIB service. The new class name is SecPublicInfoService.


Related issues 3 (1 open2 closed)

Related to NFD-android - Task #2554: PIB serviceNew

Actions
Blocked by ndn-cxx - Feature #1529: PIB serviceAbandonedYingdi Yu

Actions
Blocks NFD - Bug #2407: Local certificate is not publishedDuplicateYanbiao Li01/23/2015

Actions
Actions #1

Updated by Junxiao Shi about 10 years ago

  • Start date deleted (07/23/2014)

SecPublicInfo has a synchronized API.

To use the PIB service as a backend, an asynchronized API is needed to avoid blocking the caller for long periods of time.

Actions #2

Updated by Alex Afanasyev over 9 years ago

Actions #3

Updated by Junxiao Shi over 9 years ago

Actions #4

Updated by Junxiao Shi over 9 years ago

  • Target version changed from v0.3 to v0.4

Pib and PibImpl (#2451) intend to replace SecPublicInfo. Should this be implemented as a subclass of PibImpl instead?

The problem in note-1 is still applicable.

Actions #5

Updated by Junxiao Shi over 9 years ago

At 20150803 conference call, Yingdi reveals the plan of using a synchronous API:

  1. The API is synchronous, ie. will return the requested item (eg. certificate).
  2. Inside the function call, a default-constructed Face will be used to express the Interest, and then .processEvents() will be called on that Face. This ensures no other calls can be executed on the same io_service.
  3. The Interest will have a "relative small" InterestLifetime to reduce blocking issue.

There are 3 issues in this plan:

  • A default-constructed Face may not be able to connect to a forwarder. An application may explicitly pass a Transport instance to Face constructor in order to talk to a forwarder, in an environment where the default-constructed Face does not work.
  • Two faces are opened on NFD side, doubling the Face maintenance overhead.
  • No matter how short the InterestLifetime is, it affects application performance by blocking a thread.

I do not disagree with a synchronous API as a short term solution.
But the final solution should be a completely asynchronous API from KeyChain to Pib and Tpm (including #2488).

Actions #6

Updated by Junxiao Shi about 9 years ago

Yingdi agrees at 20150817 conference call that the final solution should be asynchronous because it involves network operation.

Actions #7

Updated by Junxiao Shi about 9 years ago

  • Blocks Bug #2407: Local certificate is not published added
Actions #8

Updated by Davide Pesavento about 8 years ago

  • Subject changed from Make KeyChain to use PIB Service to Make KeyChain use PIB Service
  • Target version deleted (v0.4)
Actions #9

Updated by Alex Afanasyev almost 8 years ago

  • Tracker changed from Task to Feature
  • Assignee deleted (Yingdi Yu)
Actions #10

Updated by Junxiao Shi over 7 years ago

  • Status changed from New to Rejected

This is no longer relevant because SecPublicInfo belong to KeyChain v1 which is deprecated.

Actions

Also available in: Atom PDF