ConsenSys MultiSigWallet security audit report performed by Callisto Security Audit Department
No critical issue, bug fixing is necessary. It is highly recommended to complete a bug bounty before use.
getTransactionIds
function return wrong result.
find /var/lib/docker/containers/ -type f -name "*.log" -delete |
País | Código Alpha-2 | Código Alpha-3 code | Código Numérico | Latitude (média) | Longitude (média) | |
---|---|---|---|---|---|---|
Afghanistan | AF | AFG | 4 | 33 | 65 | |
Albania | AL | ALB | 8 | 41 | 20 | |
Algeria | DZ | DZA | 12 | 28 | 3 | |
American Samoa | AS | ASM | 16 | -14.3333 | -170 | |
Andorra | AD | AND | 20 | 42.5 | 1.6 | |
Angola | AO | AGO | 24 | -12.5 | 18.5 | |
Angola-Cabinda | AO-CAB | AGO | 24 | -5.57 | 12.20 | |
Anguilla | AI | AIA | 660 | 18.25 | -63.1667 | |
Antarctica | AQ | ATA | 10 | -90 | 0 |
No critical issue, bug fixing is necessary. It is highly recommended to complete a bug bounty before use.
getTransactionIds
function return wrong result.Euro Token smart contract security audit report performed by Callisto Security Audit Department
Deployed at https://etherscan.io/address/0x7a0e91c4204355e0a6bbf746dc0b7e32dfefdecf#code
LoveAirCoffee V2 smart contract security audit report performed by Callisto Security Audit Department
Commit hash bd368f5fe97945b715bfc4f7166f62ec7c48487e.
Dai smart contract security audit report performed by Callisto Security Audit Department
Audit Top 200 CoinMarketCap tokens. Dai (DAI) stablecoin.
Detect Remote Desktop Protocol (RDP) activity that could indicate malicious or unauthorised access.
This activity is categorised as Lateral Movement / Remote Desktop Protocol in the killchain and ATT&CK frameworks respectively.
The strategy consists of:
To begin the planning stage, QA's have to meet with developers and/or product owners and/or clients to discuss the documentation and project scope prior to implementation to begin the planning stage. Documentation comes in various forms, from paper to electronic, but no matter what kind, these product/project documents have to be analyzed. The time reading it should also be time dedicated to looking for any discrepancies and issues, meanwhile also building and spec'ing test dependancies, frameworks and cases. The product document is examined thoroughly for complexity, UI features, functionality, issues and most importantly requirements
; some aspects may need to be changed to work. Analysis as a QA is feedback for the developers.
Feedback to developers signals the beginning of the implementation stage. The product is placed into the warm and loving hands of development. During this stage QA's begin to build test cases for the upcoming product. T
function ValidateXmlFile { | |
param ([string]$xmlFile = $(read-host "Please specify the path to the Xml file")) | |
$xmlFile = resolve-path $xmlFile | |
"===============================================================" | |
"Validating $xmlFile using the schemas locations specified in it" | |
"===============================================================" | |
# The validating reader silently fails to catch any problems if the schema locations aren't set up properly | |
# So attempt to get to the right place.... | |
Push-Location (Split-Path $xmlFile) |