You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://jira.hyperledger.org/browse/FAB-1693
The previous configuratoin transaction manager verified all signature
policies against signature sets every time regardless of whether they
had been modified. This caused a problem that if the backing policy
changed, or the certificate expired, etc., an existing policy item might
cause a config transaction to be rejected. This changeset fixes this
oversight.
Change-Id: Iec2f42d51a9a213650b80a2f735ff2fc8d8d16ac
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>
// Config was modified if any of the contents changed
213
+
isModified=!reflect.DeepEqual(val, config)
235
214
} else {
236
215
ifconfig.LastModified!=seq {
237
216
returnnil, fmt.Errorf("Key %v for type %v was new, but had an older Sequence %d set", config.Key, config.Type, config.LastModified)
238
217
}
239
218
isModified=true
240
219
}
241
220
242
-
// If a config item was modified, its LastModified must be set correctly
221
+
// If a config item was modified, its LastModified must be set correctly, and it must satisfy the modification policy
243
222
ifisModified {
244
223
ifconfig.LastModified!=seq {
245
224
returnnil, fmt.Errorf("Key %v for type %v was modified, but its LastModified %d does not equal current configtx Sequence %d", config.Key, config.Type, config.LastModified, seq)
246
225
}
226
+
227
+
// Get the modification policy for this config item if one was previously specified
0 commit comments