Skip to content
This repository was archived by the owner on Jun 24, 2026. It is now read-only.

Update the README#1064

Merged
yan merged 10 commits into
masterfrom
dev-slack-link
Aug 28, 2018
Merged

Update the README#1064
yan merged 10 commits into
masterfrom
dev-slack-link

Conversation

@yan

@yan yan commented Aug 21, 2018 •
edited by offlinemark
Loading

Copy link
Copy Markdown
Contributor

This change is Reviewable

@yan yan added this to the 0.2.1 milestone Aug 21, 2018
@yan yan changed the title Add "Getting Help" section to the readme Update the README Aug 21, 2018
offlinemark
offlinemark reviewed Aug 24, 2018
View reviewed changes
Comment thread README.md Outdated
- Ethereum smart contracts (EVM bytecode)
- Linux ELF binaries (x86, x86_64 and ARMv7)

Manticore includes a symbolic Ethereum Virtual Machine (EVM) and a convenient interface for automated compilation and analysis of Solidity. It integrates with [Ethersplay](https://github.com/trailofbits/ethersplay), Trail of Bits’ visual disassembler for EVM bytecode, for analysis visualization.

@offlinemark offlinemark Aug 24, 2018

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like this is a little too much detail for this part of the readme, but i'm not sure where it would go. maybe try to incorporate the content into the below sections somehow?

"Use the CLI to conveniently explore possible states in Solidity smart contracts using Manticore's symbolic Ethereum Virtual Machine." <- that would take care of the first sentence. not sure where we would put the second one about ethersplay (or if it really even belongs here). i feel like it is a better fit for a wiki page or something, and not the readme.

@dguido

dguido commented Aug 24, 2018

Copy link
Copy Markdown
Member

I think Getting Help maybe could get merged with Documentation at the bottom?

For the Ethereum API example, could we use a real-er example? It's hard for me to understand the value of tracking foo and bar in a dummy contract. Maybe the same for the Linux API example.

offlinemark
offlinemark reviewed Aug 27, 2018
View reviewed changes
Comment thread README.md Outdated
contract_account.incremented(value)

for state in m.running_states:
print(f"can value be 1? {state.can_be_true(value == 1)}")

@offlinemark offlinemark Aug 27, 2018

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think we might want to not use a f-str here. imo this gets into hard to read territory due how it's a complex expression, rather than just a simple variable name. also i expect many users will not exactly be familiar with this new python feature, which can slightly interfere with comprehension.

offlinemark
offlinemark reviewed Aug 27, 2018
View reviewed changes
Comment thread README.md
Manticore has a Python programming interface which can be used to implement custom analyses and is capable of detailed verification of arbitrary properties of smart contracts via its Python API. Set starting conditions, identify symbolic transactions, then review discovered states to ensure invariants for your contract hold.

```python
from manticore.ethereum import ManticoreEVM

@offlinemark offlinemark Aug 27, 2018

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i also think we should change the contract we use here. i think the contract here should, as concisely as possible, showcase the features to

  • execute contract functions with symbolic input
  • execute arbitrary sequences of contract functions
  • peruse the discovered states, looking for states that match a certain criteria (e.g. had an exception)

I think a good candidate for this would be a contract based on the umd example, but slightly simplified, as this example is a bit long. what i like about this example is that it's not immediately obvious from a human perspective how to cause the assertion to fail, but it's trivial to use manticore to find out the answer. i think we should come up with a slightly similar example in the same vein and use it here. https://github.com/trailofbits/manticore/blob/master/examples/evm/umd_example.sol

just putting these notes here; this is pretty low priority work and we should probably focus on other things for the moment

@dguido dguido Aug 27, 2018

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like the UMD example because it's too "academic." I don't want a demo of features, I want to see how Manticore helps me solve a problem or achieve a goal.

@yan yan mentioned this pull request Aug 28, 2018
Open
offlinemark
offlinemark reviewed Aug 28, 2018
View reviewed changes
Comment thread README.md Outdated
### API

Manticore has a Python programming interface which can be used to implement custom analyses.
Manticore has a Python programming interface which can be used to implement custom analyses and is capable of detailed verification of arbitrary properties of smart contracts via its Python API. Set starting conditions, identify symbolic transactions, then review discovered states to ensure invariants for your contract hold.

@offlinemark offlinemark Aug 28, 2018

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is a runon sentence, and also has redundancy w.r.t "Python programming interface" / "Python API". i'd like to keep "Manticore has a Python programming interface which can be used to implement custom analyses." as a standalone platform-agnostic first sentence of the intro

maybe something like this?

Manticore has a Python programming interface which can be used to implement custom analyses.	

For Ethereum smart contracts, it can be used for detailed verification of arbitrary contract properties. Set starting conditions, *execute* symbolic transactions, then review discovered states to ensure invariants for your contract hold.

note: changed identify to execute since i don't understand what "identify symbolic transactions" means.

offlinemark
offlinemark reviewed Aug 28, 2018
View reviewed changes
Comment thread README.md Outdated
Manticore has a command line interface which can be used to easily symbolically execute a supported program. Analysis results will be placed into a new directory beginning with `mcore_`.
Manticore has a command line interface which can be used to easily symbolically execute a supported program or smart contract. Analysis results will be placed into a new directory beginning with `mcore_`.

Use the CLI to explore possible states in Ethereum smart contracts. Manticore includes _detectors_ which flag certain conditions, including known vulnerable code, as it explores possible states. Solidity smart contracts must have a `.sol` extension for analysis by Manticore. See a [demo](https://asciinema.org/a/154012).

@offlinemark offlinemark Aug 28, 2018

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i know was just copied and pasted, but while we're here... i think "which flag certain conditions, including known vulnerable code" sounds kind of weird ( i think i wrote it :x ).

maybe this?

Manticore includes _detectors_ which flag potentially vulnerable code that is detected in an explored state.

offlinemark
offlinemark reviewed Aug 28, 2018
View reviewed changes
Comment thread README.md Outdated
### API

Manticore has a Python programming interface which can be used to implement custom analyses.
Manticore has a Python programming interface which can be used to implement custom analyses. For Ethereum smart contracts, can be used for detailed verification of arbitrary contract properties. Set starting conditions, execute symbolic transactions, then review discovered states to ensure invariants for your contract hold.

@offlinemark offlinemark Aug 28, 2018

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

paragraph break at the end of first sentence?

offlinemark
offlinemark reviewed Aug 28, 2018
View reviewed changes
Comment thread README.md Outdated

Manticore has a Python programming interface which can be used to implement custom analyses.

For Ethereum smart contracts, can be used for detailed verification of arbitrary contract properties. Set starting conditions, execute symbolic transactions, then review discovered states to ensure invariants for your contract hold.

@offlinemark offlinemark Aug 28, 2018

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"can be used"

@yan
yan merged commit 15b2257 into master Aug 28, 2018
@yan
yan deleted the dev-slack-link branch August 28, 2018 18:56
yan added a commit that referenced this pull request Sep 6, 2018
@yan
Update FPSE-like memory model (#1100)
b9cef7b 
* Python 3; optimization / stylization pass
  * cleanup list() from automation tools
  * style; use dict comprehensions
  * style; use set literals

* Experiment reporting the finding at a JUMPI (#949)

* Experiment reporting the finding at a JUMPI

* Fix taint. Detect returned overflowded data

* Fix contract names in benchmark

* Move default plugin registration

* merge

* rm make_evm (#978)

* Yolo dev evm fix address concretization (#1002)

* DAO detector + bugfixes

* The actual benchmark tests

* The actual benchmark tests

* CC

* Experiment reporting the finding at a JUMPI

* Fix taint. Detect returned overflowded data

* DAO -> Reentrancy

* DAO -> reentrancy, C -> Benchmark

* DAO -> reentrancy, C -> Benchmark

* Allow function names to have numbers

* Fix contract names in benchmark

* Fix contract names in benchmark

* Move default plugin registration

* Better regexp

* Fix minimal_bytecode example

* Fix Array Slice and test

* add tests

* correct other bug

* implement bytesM

* BROKEN partial progress

* need bytearray here

* rm cmt

* add basic tests for bytesM and bytes symbolic

* correct bytes symbolic test

* Refactor, clean bytesM handling

* Add initial symbolic 'bytes' handling

* refactor tests

* Unify symbolic/concrete bytes handling in bytesM/bytes

* Rm import

* Rm debug assert

* cc

* Visitor/migrate/simplify fixes to make the seth refactor pass

* Fix concolic?

* Fix concolic?

* CC

* bytesM fix

* Fix address and caller concretization on symb tx

* Fix account policy refactor

* CC

* cleanup

* numbers.Integral

* super()

* remove/update deprecated

* Report test coverage to CodeClimate (#1004)

This PR enables the reporting of test coverage of all the test jobs (`eth` and `tests`) to CodeClimate. This uses S3 to temporarily store results between jobs and later upload them to CC.

Fixes #1000

* codeclimate

* codeclimate - bump similar-code thresh; false positive

* Fix CC coverage (#1007)

This fix does two things:

 1. Ignores non-manticore files from the coverage report to limit what can fail.
 2. Changes how travis runs s3 sync on completion. (Fixes #1006)

* Report test coverage to CodeClimate (#1004)

This PR enables the reporting of test coverage of all the test jobs (`eth` and `tests`) to CodeClimate. This uses S3 to temporarily store results between jobs and later upload them to CC.

Fixes #1000

* Fix CC coverage (#1007)

This fix does two things:

 1. Ignores non-manticore files from the coverage report to limit what can fail.
 2. Changes how travis runs s3 sync on completion. (Fixes #1006)

* re-enable and fix eth regression 808 (#1011)

* cleanup examples (#1010)

* resolves #1008 (#1014)

* Addresses performance issues;
  * reimplement caching for `arithmetic_simplifier` and `constant_folder`
  * optimize `ArithmeticSimplifier.visit_ArraySelect`

* File mode fix - resolves #1018

* Fixes closed file serialization (#955)

Fixes #954

* Add unit test for 954 (#1022)

* Change how we query for version (#1023)

Fixes #1021

This also should decrease how many times we invoke z3. (The instance used to query version should stick around)

* Use capstone 3.0.5 and no longer rc2 (#1026)

* binja cleanup

* fixes docker - resolves #991

* Dev yolo retvalthing (#1001)

* DAO detector + bugfixes

* The actual benchmark tests

* The actual benchmark tests

* CC

* Experiment reporting the finding at a JUMPI

* Fix taint. Detect returned overflowded data

* DAO -> Reentrancy

* DAO -> reentrancy, C -> Benchmark

* DAO -> reentrancy, C -> Benchmark

* Allow function names to have numbers

* Fix contract names in benchmark

* Fix contract names in benchmark

* Move default plugin registration

* Better regexp

* Fix minimal_bytecode example

* Fix Array Slice and test

* add tests

* correct other bug

* implement bytesM

* BROKEN partial progress

* need bytearray here

* rm cmt

* add basic tests for bytesM and bytes symbolic

* correct bytes symbolic test

* Refactor, clean bytesM handling

* Add initial symbolic 'bytes' handling

* refactor tests

* Unify symbolic/concrete bytes handling in bytesM/bytes

* Rm import

* Rm debug assert

* cc

* Visitor/migrate/simplify fixes to make the seth refactor pass

* Fix concolic?

* Fix concolic?

* CC

* bytesM fix

* Fix address and caller concretization on symb tx

* Fix/refactor symbolic address/caller concretization

* Fix caller concretization

* Fix expression visiting

* Fix account policy refactor

* Accept numbers in function names abitypes

* Simplify installation instructions to recommend install manticore only for the current user

* Run some tests in parallel (#970)

This PR splits the current test runner into three environments: 

1. Linux examples
2. Ethereum tests
3. Remaining tests

to faster complete each testing run. Ethereum tests include a number of integration tests that execute scripts to completion, which takes a while. We run them concurrently with other tests to save on execution time. The split is done by naming Ethereum tests differently (`eth_*.py` vs `test_*.py`) and updating what pattern unittest's `discover` uses.

This change also updates the installation script and chooses to forego installing Keystone for EVM tests as it takes a while, and it adds a `setup.cfg` config file so that Nose finds the eth tests as well by default.

* Be less verbose when testing

* Fix slicing wrongly reference to proxyArray. Fix #912

* Only export human/external tx in the testcase (#972)

* Make ManticoreEVM.make_symbolic_value size adjustable (#974)

* Make size adjustable

* Default to 256

* Dev evm yolo fix gas (#975)

* Fix gas stipend on CALL and check dao

* Add order dependence 1

* Going linter. Report/Detect that thing when code does not check returned value

* cleaner example of fail

* Update retval_crazy.sol

* new solc for travis

* CC

* Remove duplicated ReentrancyDetector

* POrt to py3

* POrt to py3

* P0rt to py3

* CC

* Tests doc

* CC

* review changes

* remove stray comment

* missed one

* resolves #992 (#1033)

* resolves #992

* fix sys_write logger output (#1024)

* fix sys_write logger output - resolves #1020
* write/writev/read fixes
* openat((int32)dirfd, ...) resolves #940, syscall logging
* disable E701, interferes with PEP484/526

* readme Ethereum update issue #1003 (#1034)

* readme ethereum update issue #1003

* simplify

* Update README.md

* ignore resource warnings (e.g. unclosed files) (#1038)

* Test manticore on MacOS (#1032)

* Test manticore on MacOS

like test_binaries.py for path to binary to test

* MacOS compatibility achieved

Replacement of /bin/ls in tests
Use of basename in test_load_maps

* Fix gast (#1039)

* Readme updates (#1037)

* add some more heft to the Ethereum section

* no longer needed

* Integrate requirements into installation

* Update README.md

* Update README.md

* Update README.md

* Update README.md

* Duplicate commands for docker quick start

* Rm --process-dependency-links note, moved into the faq on the wiki

* Small tweaks

* pedantic formatting

* Emphasize new python requirement (#1041)

* Emphasize new python requirement

* Consistent formatting

* Port remaining examples to py3 (#1042)

* port use_def

* port some scripts, cleanup

* ported `scripts/gdb.py` - untested

* misc

* Manticore 0.2.0 (#1043)

* Bump version

* Initial changelog changes

* Bump version in setup.py

* Add skeleton and externals

* Fill in 0.2.0 readme

* Updates

* Add logo to readme (#1046)

* add logo to README

* Fix missing profiling data (#1057)

* fix missing profiling data - resolves #982
* unit test

* Code cleanup and coverage (#1035)

* dead code elimination, __init__ cleanup
* `binary.Elf` bugfix, add `binary` package tests

* Serialization cleanup (#1048)

* refactor serialization / recursion limit handling

* evm: aggressively check & migrate expressions into current ConstraintSet in case they are global/external (#1009)

* Be mega forgiving on global expression usage - EVM

* Refactor new_bitvector api

* Fix neW_bool

* CC

* rename avoid_collisions collision

* rename avoid_collisions collision

* migrate on state.constraint too..

* Migration bugfixes

* CC bugfixes

* invalid assert removed

* move rep code to method

* reviewing the codes

* CC

* Change variable names

* typo

* Some mini docstrings and a unittest

* Add migration integration testion

* Keep fuzz-refactoring it

* CC

* Bugfixfixfixfix

* CC

* re refactor mig algorithm

* better cleaner stronger. (reviewing)

* CC

* Small refactor and Fix strange strcmp test.

* CC

* re re refactor for readability

* CC

* rev

* forgoten var

* Fix for #1008 (#1063)

* Fix for #1008

* add test for funcall output

* Implements support for function overloading in ethereum (#1049)

* implements `signature` kwarg for overloaded functions - resolves #810

* Fix typo mistake in multi-million word (#1073)

* eth: add selfdestruct detector & misc bug fixes (#1068)

* Don't keep selfdestruct states alive

* Use avoid_collisions=True for internal uses of the .new_ methods

* Better err msgs

* Output pc in hex

* Fix ignored workspace cli flag

* hex pc

* hex pc one last time

* add selfdestruct detector

* Add cli support

* Add ok selfdestruct test

* Add selfdestruct not ok - true positive

* Add selfdestruct crazy - true negative

* Reorganize plugin/detectors. Add LoopDepthLimiter plugin + cli flag

* rename files

* add another test

* Add initial selfdestruct tests

* Move integer overflow detector test into eth_detectors

* cc

* add missing import

* add other missing import

* Added --txnoether option to avoid sending ether to contracts (#1078)

* added --txnoether option

* Improved command line description

* eth: add ether leak detector (#1077)

* Add initial ether leak detector

* Initial test

* correct

* Add another neg

* rm stray print

* initial tests refactoring + ether leak tests

* finding name

* initial refactor

* clean comment

* correct this test

* update tests

* Add fp comment

* add other test

* remove unnecessary payable function

* make LoopDepthLimiter configurable

* Use real pc

* cc

* Add other test

* Add cli interface

* Create readthedocs.yml (#1085)

* Fix rtd (#1086)

* test

* wrong number

* sorry Popen :(

* mocking

* x

* clean

* better explain this arcane stuff

* don't need io

* Improved printing of constructor call with decoded constructor arguments and transaction result (#1080)

* added printing of decoded constructor arguments

* Fixed test

* Add --no-testcases flag (#1083)

* Update the README (#1064)


<!-- Reviewable:start -->
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/trailofbits/manticore/1064)
<!-- Reviewable:end -->

* Add detector for plain external call (#1087)

* initial refactor etherleak to also do general external call

* refactor

* Update users

* Update tests

* Update

* Fix tests

* Don't use signed operator, check != 0

* Record constraint

* Record constraint

* Use did_evm_execute

So we don't falsely report if the CALL were to fail

* Revert "Use did_evm_execute"

96a84f2

* simplify deref logic

* clean up derefs; rename backing array

* reduce write calls

* simplify

* add name field

* Detection of environmental and potentially manipulable instruction/data (#1096)

* unittest

* CC

* import fix

* typo

* forgotten test

* eth: new/alternative reentrancy detector (#1082)

* initial second one

* update

* polish

* correct

* Correctly check gas

* Record gas constraint and save in finding

* simplify logic

* Check if destination is a contract

* Revert "Check if destination is a contract"

901be37

* better context key

* Be lenient with Constants

* Add new simpler/less input required reentrancy detector, use in the cli

* Fix bad merge import

* Fix import

* Add final missing import

* add an iter() interface to Memory

* Add env instruction detector to cli (#1105)

* Sha3 rework and performance enhancements (#1031)

* DAO detector + bugfixes

* The actual benchmark tests

* The actual benchmark tests

* CC

* Experiment reporting the finding at a JUMPI

* Fix taint. Detect returned overflowded data

* DAO -> Reentrancy

* DAO -> reentrancy, C -> Benchmark

* DAO -> reentrancy, C -> Benchmark

* Allow function names to have numbers

* Fix contract names in benchmark

* Fix contract names in benchmark

* Move default plugin registration

* Better regexp

* Fix minimal_bytecode example

* Fix Array Slice and test

* add tests

* correct other bug

* implement bytesM

* BROKEN partial progress

* need bytearray here

* rm cmt

* add basic tests for bytesM and bytes symbolic

* correct bytes symbolic test

* Refactor, clean bytesM handling

* Add initial symbolic 'bytes' handling

* refactor tests

* Unify symbolic/concrete bytes handling in bytesM/bytes

* Rm import

* Rm debug assert

* cc

* Visitor/migrate/simplify fixes to make the seth refactor pass

* Fix concolic?

* Fix concolic?

* CC

* bytesM fix

* Fix address and caller concretization on symb tx

* Fix/refactor symbolic address/caller concretization

* Fix caller concretization

* Fix expression visiting

* Fix account policy refactor

* Accept numbers in function names abitypes

* Simplify installation instructions to recommend install manticore only for the current user

* Run some tests in parallel (#970)

This PR splits the current test runner into three environments: 

1. Linux examples
2. Ethereum tests
3. Remaining tests

to faster complete each testing run. Ethereum tests include a number of integration tests that execute scripts to completion, which takes a while. We run them concurrently with other tests to save on execution time. The split is done by naming Ethereum tests differently (`eth_*.py` vs `test_*.py`) and updating what pattern unittest's `discover` uses.

This change also updates the installation script and chooses to forego installing Keystone for EVM tests as it takes a while, and it adds a `setup.cfg` config file so that Nose finds the eth tests as well by default.

* Be less verbose when testing

* Fix slicing wrongly reference to proxyArray. Fix #912

* Only export human/external tx in the testcase (#972)

* Make ManticoreEVM.make_symbolic_value size adjustable (#974)

* Make size adjustable

* Default to 256

* Dev evm yolo fix gas (#975)

* Fix gas stipend on CALL and check dao

* Add order dependence 1

* Going linter. Report/Detect that thing when code does not check returned value

* cleaner example of fail

* Update retval_crazy.sol

* new solc for travis

* CC

* Remove duplicated ReentrancyDetector

* POrt to py3

* POrt to py3

* P0rt to py3

* CC

* Be mega forgiving on global expression usage - EVM

* Tests doc

* Refactor new_bitvector api

* function id to binary

* Fix neW_bool

* CC

* rename avoid_collisions collision

* rename avoid_collisions collision

* migrate on state.constraint too..

* Migration bugfixes

* CC bugfixes

* invalid assert removed

* move rep code to method

* unittets fixes and CC

* CC

* Refactor result_ref out in favor of change_last_result()

* CC

* reviewing the codes

* CC

* Change variable names

* typo

* Basic refactors and output enhancements

* Some minid docstrings and a unittest

* Some mini docstrings and a unittest

* Add migration integration testion

* Keep fuzz-refactoring it

* CC

* Bugfixfixfixfix

* CC

* re refactor mig algorithm

* better cleaner stronger. (reviewing)

* CC

* Small refactor and Fix strange strcmp test.

* CC

* funtion selector abinary

* bugfix.. waiting for migreation PR

* convenient tx abi parsing func

* convenient tx abi parsing func

* convenient tx abi parsing func

* convenient tx abi parsing func

* re re refactor for readability

* CC

* rev

* CC

* forgoten var

* CC

* CC

* review

* typo

* CC

* review

* Adding single example to sha3 trick when there are not know examples

* CC

* review

* CC

* Forgotten rollback

* CC

* Detect the odd delegatecall instruction (#1108)

* DAO detector + bugfixes

* The actual benchmark tests

* The actual benchmark tests

* CC

* Experiment reporting the finding at a JUMPI

* Fix taint. Detect returned overflowded data

* DAO -> Reentrancy

* DAO -> reentrancy, C -> Benchmark

* DAO -> reentrancy, C -> Benchmark

* Allow function names to have numbers

* Fix contract names in benchmark

* Fix contract names in benchmark

* Move default plugin registration

* Better regexp

* Fix minimal_bytecode example

* Fix Array Slice and test

* add tests

* correct other bug

* implement bytesM

* BROKEN partial progress

* need bytearray here

* rm cmt

* add basic tests for bytesM and bytes symbolic

* correct bytes symbolic test

* Refactor, clean bytesM handling

* Add initial symbolic 'bytes' handling

* refactor tests

* Unify symbolic/concrete bytes handling in bytesM/bytes

* Rm import

* Rm debug assert

* cc

* Visitor/migrate/simplify fixes to make the seth refactor pass

* Fix concolic?

* Fix concolic?

* CC

* bytesM fix

* Fix address and caller concretization on symb tx

* Fix/refactor symbolic address/caller concretization

* Fix caller concretization

* Fix expression visiting

* Fix account policy refactor

* Accept numbers in function names abitypes

* Simplify installation instructions to recommend install manticore only for the current user

* Run some tests in parallel (#970)

This PR splits the current test runner into three environments: 

1. Linux examples
2. Ethereum tests
3. Remaining tests

to faster complete each testing run. Ethereum tests include a number of integration tests that execute scripts to completion, which takes a while. We run them concurrently with other tests to save on execution time. The split is done by naming Ethereum tests differently (`eth_*.py` vs `test_*.py`) and updating what pattern unittest's `discover` uses.

This change also updates the installation script and chooses to forego installing Keystone for EVM tests as it takes a while, and it adds a `setup.cfg` config file so that Nose finds the eth tests as well by default.

* Be less verbose when testing

* Fix slicing wrongly reference to proxyArray. Fix #912

* Only export human/external tx in the testcase (#972)

* Make ManticoreEVM.make_symbolic_value size adjustable (#974)

* Make size adjustable

* Default to 256

* Dev evm yolo fix gas (#975)

* Fix gas stipend on CALL and check dao

* Add order dependence 1

* Going linter. Report/Detect that thing when code does not check returned value

* cleaner example of fail

* Update retval_crazy.sol

* new solc for travis

* CC

* Remove duplicated ReentrancyDetector

* POrt to py3

* POrt to py3

* P0rt to py3

* CC

* Be mega forgiving on global expression usage - EVM

* Tests doc

* Refactor new_bitvector api

* function id to binary

* Fix neW_bool

* CC

* rename avoid_collisions collision

* rename avoid_collisions collision

* migrate on state.constraint too..

* Migration bugfixes

* CC bugfixes

* invalid assert removed

* move rep code to method

* unittets fixes and CC

* CC

* Refactor result_ref out in favor of change_last_result()

* CC

* reviewing the codes

* CC

* Change variable names

* typo

* Basic refactors and output enhancements

* Some minid docstrings and a unittest

* Some mini docstrings and a unittest

* Add migration integration testion

* Keep fuzz-refactoring it

* CC

* Bugfixfixfixfix

* CC

* re refactor mig algorithm

* better cleaner stronger. (reviewing)

* CC

* Small refactor and Fix strange strcmp test.

* CC

* funtion selector abinary

* bugfix.. waiting for migreation PR

* convenient tx abi parsing func

* convenient tx abi parsing func

* convenient tx abi parsing func

* convenient tx abi parsing func

* re re refactor for readability

* CC

* rev

* CC

* forgoten var

* CC

* CC

* Delete duplicated detector

* WIP delegatecall. Lot of fixes. Recursion fix.

* review

* typo

* CC

* Sha3 random concre example when none. Concretize SIZE/OFFSET more. Initial calldata size management

* remove debug print

* Add check in constraints.add

* review

* Adding single example to sha3 trick when there are not know examples

* CC

* review

* CC

* about to merge sha3

* cleanups

* make gas budget configurable by user

* cleanups

* cleanups

* CC:

* CC

* Fix typo in tests

* Fix import typo

* pump some gas

* typo in skipping slow/big test

* skipping more test to make travis happy

* skipping more test to make travis happy

* debugging travis like a caveman

* dbg

* dbg

* dbg

* undbg

* undbg

* undbg

* undbg

* undbg and fixed

* undbg and fixed

* CC

* Updates to README.md relating to Python 3 migration and sudo within virtualenv setup (#1109)

* updated README.md to use python3 commands

* updated README.md to add sudo to system pip3 install commands

Line 186 uses a path to the specific pip3 binary (as per https://stackoverflow.com/questions/41429988/inside-virtual-env-sudo-pip-links-to-the-global-python-pip ).

* Manticore 0.2.1 (#1106)

* Bump version num

* changelog skeleton

* Switch to agpl

* readme license update

* update

* gas

* Add dc

* Date update

* Add last minute contributions

* Release 0.2.1c (#1111)

* Fix the versioning hell (#1112)

* Fix version number / release (#1113)

* Manticore 0.2.1-berlin (#1114)

* Manticore 0.2.1-b (#1115)

* manticore 0.2.1.1 (#1116)

* start scan_mem refactor

* Fix DecodeException message

* Only import mapped memory

* get a single value, instead of all, when decoding

* clean up instruction decoding

* simplify scan_mem

* Changed instances of Concretice to Concretize (#1118)

* Fix typo

* rename a field

* Attempt decoding with an arraystore simplifier

* python3 update to linux example makefile (#1122)

Ubuntu 18.04 doesn't alias python to python3

* Update decoding logic

* Simplify [skip] importing read-only maps

* Fix name serialization with anonmaps
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

2 more reviewers
@dguido dguido dguido left review comments
@offlinemark offlinemark offlinemark approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

@offlinemark offlinemark

Labels

None yet

Projects

None yet

Milestone

0.2.1

Development

Successfully merging this pull request may close these issues.

3 participants

@yan @dguido @offlinemark