CLIMBER is a defense mechanism to neutralizeFlipping Address Attack.CLIMBER dynamically change harmful address mappings so that intensive writes to weak cells are redirected to strongcells.CLIMBER also conceals weak NVM cells from attackers by randomly mapping cold addresses to weak NVM regions.
1.External Dependencies
Before running CLIMBER codes, it's essential that you have already install dependencies listing below.
- numpy
- python(>=2.7)
- Zsim-NVMain (We use Zsim to collect memory access trace. You can also use other simulators to collect trace) axle-zsim-nvmain
2.Running
- First, get trace files by:
[root @node1 CLIMBER/trace]# cat trace.tar.gz.* > trace.tar.gz
[root @node1 CLIMBER/trace]# tar -zxvf trace.tar.gz- Then, copy the python files(.py) to the trace directory(CLIMBER/trace/*/).
- Run CLIMBER codes by:
[root @node1 CLIMBER/trace/*/]# python typeX_*_climber.py arg1 arg2 arg3 arg4- X = 0 is non-attack (needs memory trace); X = 1 is Inconsistent Write Attack.
- Arg1 and arg2 are used to enable our CLIMBER and WPRM schemes. Arg1 = 0 means running without CLIMBER, arg1 = 1 means running CLIMBER with the baseline systems and arg1 = 2 means running CLIMBER only. Arg2 = 0 means running without WPRM and Arg2 = 1 means running with WPRM. Arg3 means the region size of CLIMBER (10-19) and arg4 means the climber-threshold of CLIMBER.
3.Result
The endurance result is recorded by *mm_climber.py in *.dat files.