Timeline for Let's protect that CLI Python script
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 6, 2016 at 8:30 | comment | added | Xiong Chiamiov | What sort of security are you aiming for? That is, what type of attack is this supposed to defend against? | |
| Sep 14, 2016 at 4:43 | vote | accept | Grajdeanu Alex | ||
| Sep 13, 2016 at 13:22 | answer | added | 301_Moved_Permanently | timeline score: 6 | |
| Sep 13, 2016 at 12:56 | comment | added | Grajdeanu Alex | @MathiasEttinger Yes, basically there will be a function which will contain the rest of the logic. The program will be delivered as a compiled source. So unless somebody reverse-engineer it, there won't be such a case. | |
| Sep 13, 2016 at 12:54 | comment | added | 301_Moved_Permanently |
So basically, you will have your business logic instead of print('Match MAC and execute program here\n'). Most likely in a function, say foo(). What could possibly prevent any user to open this file and modify if __name__ == '__main__': main() into if __name__ == '__main__': foo()?
|
|
| Sep 13, 2016 at 12:14 | comment | added | Dan |
well if uid_file.cfg isn't present you're a bit buggered
|
|
| Sep 13, 2016 at 12:13 | history | edited | Peilonrayz♦ |
edited tags
|
|
| Sep 13, 2016 at 11:53 | history | asked | Grajdeanu Alex | CC BY-SA 3.0 |