Yes, there are times that it makes sense to disable the standard
checksum behavior. You can disable the checks per changeSet using the
<validCheckSum> tag with known good values, or with
<validCheckSum>ANY</validCheckSum> to allow all checksum values.
I thought there was an extension to disable checksums globally, but
it looks like on hasn't been made yet. It should be possible to
extend the liquibase.changelog.ChangeLogHistoryService class to not
deal with checksums, but starting with per-changeSet disabling is
probably the best way to start since it is simpler and only affects
changeSets you know can be problems and you will still get
notifications of unexpected changes everywhere else.
Nathan