![]() They waited to be asked about it,” one ex-monitoring team member, who agreed to speak on the condition of anonymity, said. “HSBC never voluntarily disclosed money laundering to us. The bank, which is headquartered in London, would have been expected to disclose the information to an independent monitor brought in by the US Department of Justice (DoJ) in 2012, when criminal proceedings were deferred on condition the bank reform its anti-money laundering checks.Ī number of former members of the DoJ monitoring team say they were never made aware of the network, raising questions over whether HSBC was fully transparent with the monitor, which was meant to keep tabs on the bank as it tried to improve its anti-money laundering standards. The majority of funds passing through the network appeared to be from multiple users not connected to the Guptas. Money flow from Gupta-linked companies into this network was “contained and minimal”, the bank concluded, amounting to just £12m. When the report was circulated in 2017, 60 of these accounts were still open. ![]() The network was identified as involving 92 HSBC Hong Kong accounts that received $4.2bn worth of payments between 20, some of which may have been used for legitimate purposes. While tracing funds flowing from these companies, bank investigators uncovered what they suspected was a professional money laundering network controlled by unrelated parties. The report – which represents findings at the time – identified three companies with accounts at its Hong Kong branch that media reports had previously concluded were controlled by associates of the Gupta family. here the vgo project replaced -no-show-signature with -c log.showsignature=false which seems to have the same effect.A redacted internal HSBC report, published last week by authorities in South Africa, suggests the bank uncovered the previously undisclosed multibillion-pound network as early as 2016, while it was trying to assess its potential exposure to the controversial Gupta family, who were embroiled in a national corruption scandal in South Africa. I couldn't find out which version of git introduced the the -no-show-signature switch, but I did find unrelated project which face the same issue. $ git describe -tags -abbrev=0 Įrror: fatal: unrecognized argument: -no-show-signatureĪt Transform._transform (/builds/REDACTED/node_modules/git-raw-commits/index.js:84:30)Īt Transform._read (/builds/REDACTED/node_modules/readable-stream/lib/_stream_transform.js:177:10)Īt Transform._write (/builds/REDACTED/node_modules/readable-stream/lib/_stream_transform.js:164:83)Īt doWrite (/builds/REDACTED/node_modules/readable-stream/lib/_stream_writable.js:409:139)Īt writeOrBuffer (/builds/REDACTED/node_modules/readable-stream/lib/_stream_writable.js:398:5)Īt (/builds/REDACTED/node_modules/readable-stream/lib/_stream_writable.js:307:11)Īt Socket.ondata (_stream_readable.js:719:22)Īt readableAddChunk (_stream_readable.js:280:11)Įmitted 'error' event on Readable instance at:Īt Transform._transform (/builds/REDACTED/node_modules/git-raw-commits/index.js:84:16) ![]() $ git for-each-ref -format="%(upstream:short)" refs/heads/master ![]() Npx release-it -ci -disable-metrics -VV -npm.skipChecks=true ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |