Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specifics of encrypting sealed bids #231

Closed
Bjwebb opened this issue Sep 1, 2015 · 3 comments
Closed

Specifics of encrypting sealed bids #231

Bjwebb opened this issue Sep 1, 2015 · 3 comments
Labels
Focus - Extensions Relating to new or proposed extensions, or the governance and maintenance of extensions

Comments

@Bjwebb
Copy link
Contributor

Bjwebb commented Sep 1, 2015

The general approach to encryption in an OCDS file is being discussed at #226 (e.g. what metadata format should be used, what ciphers etc.). However, there are also some specific questions relating to how to implement sealed bids (the main known use case atm*), that may be independent of the encryption/metadata scheme.

For example:

  • Bids should be encrypted individually, as these may come from different authors (eMalls in the ProZorro case), and also because the number of bids should be public.
  • Some information within bids may be released (e.g. the author of the bid), but no other information. This may mean we don't want to encrypt the whole of a bids JSON object. @myroslav do you know if this would be the case for Prozorro?

(*Note that bids are not currently in the OCDS standard, but are being used by Prozorro, and there are plans to develop a bid extension #197 to standardise this).

@Bjwebb Bjwebb added help wanted Focus - Extensions Relating to new or proposed extensions, or the governance and maintenance of extensions labels Sep 1, 2015
@myroslav
Copy link

The bid is quite complex structure in regards to encryption. Something as complex as field level encryption will be applied. It is because different information that bid consist of will be released in different moment of time. I.e. The initial price has to be revealed when auction starts. The MEAT cbid parameters should be revealed when auction starts and only to auction module. But author of the bid and documents cannot be revealed until auction ends.

Ideally until auction is started the number of bidders should be protected. But the way to achieve this is more complex then individual bid encryption.

After we add Lots extension the bid encryption becomes one magnitude more complex since each lot will have its own set of properties to encrypt (auctions for every lot take place in different moment of time).

@timgdavies
Copy link
Contributor

Thanks @myroslav

It seems to me that if OCDS is to tackle this, we're going to need to do quite a bit more work reviewing existing solutions etc. to this kind of problem out there.

I've just sent around an e-mail to start exploring whether we can prioritise that kind of research.

@timgdavies
Copy link
Contributor

There have been no updates on this issue since 2015. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Focus - Extensions Relating to new or proposed extensions, or the governance and maintenance of extensions
Projects
None yet
Development

No branches or pull requests

3 participants