Searched full:fi (Results 1 – 17 of 17) sorted by relevance
21 fi43 fi50 fi53 fi60 fi63 fi66 fi74 fi
19 fi20 fi29 fi48 fi
31 fi39 fi41 fi52 fi
19 fi20 fi
30 fi
29 fi
52 fi
31 fi108 fi123 fi124 fi131 fi168 fi178 fi183 fi187 fi191 fi
49 fi60 # Load the CSV FI manifest file, and output in START, END lines. Effectively75 # Invoke the fi tester script
34 fi
24 fi
1 # Travis configuration. Run FI hardening tests.64 fi65 fi
16 fi20 fi
290 @if [ -z "$$ZEPHYR_BASE" ]; then echo "Zephyr environment not set up"; false; fi291 @if [ -z "$(BOARD)" ]; then echo "You must specify BOARD=<board>"; false; fi
8 fi
1230 As MCUboot is deployed on a microcontroller, testing FI would not make much1234 with `-O0` optimisation is more resilient against FI attacks than the code
