Skip to content
This repository has been archived by the owner on Sep 26, 2019. It is now read-only.

[PAN-3010] Enforce privateFrom to be present. #1829

Merged
merged 3 commits into from
Aug 12, 2019

Conversation

iikirilov
Copy link
Contributor

@iikirilov iikirilov commented Aug 7, 2019

PR description

In eeaSendRawTransaction we are currently assuming that the user can send a transaction without the privateFrom field. The node will populate the private transaction with the default enclave key that is specified when starting up Pantheon.

On the face of it, this seems ok. But because the transaction comes in signed - the signature does not take into account the privateFrom field.

When computing the sender address on the node it is wrong.

We decided to enforce that privateFrom is mandatory,

Fixed Issue(s)

PAN-3010

@iikirilov iikirilov force-pushed the iikirilov-pan-3010 branch from 025337f to 41cb16d Compare August 7, 2019 16:21
@iikirilov iikirilov force-pushed the iikirilov-pan-3010 branch from 41cb16d to d78edb9 Compare August 8, 2019 07:52
Copy link
Contributor

@jframe jframe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@MadelineMurray MadelineMurray merged commit 5c2bc03 into PegaSysEng:master Aug 12, 2019
@iikirilov iikirilov deleted the iikirilov-pan-3010 branch August 16, 2019 14:01
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants