Format first-party source according to .clang-format

This commit is contained in:
Pretty Printer
2020-04-17 09:56:34 -05:00
committed by manojsdoshi
parent 65dfc5d19e
commit 50760c6935
1076 changed files with 86161 additions and 77449 deletions

View File

@@ -22,30 +22,34 @@
namespace ripple {
void
sign (STObject& st, HashPrefix const& prefix,
KeyType type, SecretKey const& sk,
sign(
STObject& st,
HashPrefix const& prefix,
KeyType type,
SecretKey const& sk,
SF_Blob const& sigField)
{
Serializer ss;
ss.add32(prefix);
st.addWithoutSigningFields(ss);
set(st, sigField,
sign(type, sk, ss.slice()));
set(st, sigField, sign(type, sk, ss.slice()));
}
bool
verify (STObject const& st, HashPrefix const& prefix,
PublicKey const& pk, SF_Blob const& sigField)
verify(
STObject const& st,
HashPrefix const& prefix,
PublicKey const& pk,
SF_Blob const& sigField)
{
auto const sig = get(st, sigField);
if (! sig)
if (!sig)
return false;
Serializer ss;
ss.add32(prefix);
st.addWithoutSigningFields(ss);
return verify(pk,
Slice(ss.data(), ss.size()),
Slice(sig->data(), sig->size()));
return verify(
pk, Slice(ss.data(), ss.size()), Slice(sig->data(), sig->size()));
}
// Questions regarding buildMultiSigningData:
@@ -80,20 +84,20 @@ verify (STObject const& st, HashPrefix const& prefix,
// So, if we support multiple levels of signing, then we'll need to
// incorporate the "signing for" accounts into the signing data as well.
Serializer
buildMultiSigningData (STObject const& obj, AccountID const& signingID)
buildMultiSigningData(STObject const& obj, AccountID const& signingID)
{
Serializer s {startMultiSigningData (obj)};
finishMultiSigningData (signingID, s);
Serializer s{startMultiSigningData(obj)};
finishMultiSigningData(signingID, s);
return s;
}
Serializer
startMultiSigningData (STObject const& obj)
startMultiSigningData(STObject const& obj)
{
Serializer s;
s.add32 (HashPrefix::txMultiSign);
obj.addWithoutSigningFields (s);
s.add32(HashPrefix::txMultiSign);
obj.addWithoutSigningFields(s);
return s;
}
} // ripple
} // namespace ripple