mirror of
https://github.com/Zygo/bees.git
synced 2025-05-17 21:35:45 +02:00
BeesBlockData: don't leak file contents in the log
The data field of BeesBlockData is only interesting to those who want to debug the BeesBlockData implementation or other battle-tested parts of bees. Users who want to do this can modify and rebuild the source to enable the output. To everyone else, the data field is a huge, ongoing infoleak through the log. Don't bother with an option, just output the length of the data field and nothing else. Fixes: https://github.com/Zygo/bees/issues/53 Signed-off-by: Zygo Blaxell <bees@furryterror.org>
This commit is contained in:
parent
71be53eff6
commit
4ecd467ca0
@ -877,6 +877,9 @@ operator<<(ostream &os, const BeesBlockData &bbd)
|
||||
os << ", hash = " << bbd.m_hash;
|
||||
}
|
||||
if (!bbd.m_data.empty()) {
|
||||
// Turn this on to debug BeesBlockData, but leave it off otherwise.
|
||||
// It's a massive data leak that is only interesting to developers.
|
||||
#if 0
|
||||
os << ", data[" << bbd.m_data.size() << "] = '";
|
||||
|
||||
size_t max_print = 12;
|
||||
@ -893,6 +896,9 @@ operator<<(ostream &os, const BeesBlockData &bbd)
|
||||
}
|
||||
}
|
||||
os << "...'";
|
||||
#else
|
||||
os << ", data[" << bbd.m_data.size() << "]";
|
||||
#endif
|
||||
}
|
||||
return os << " }";
|
||||
}
|
||||
|
Loading…
x
Reference in New Issue
Block a user