# PICO ClassOps discussion points - 22nd Nov ## Experiences from using Pico 19.2.3 for Fall 2020 - The gcc update broke a lot of binary exploitation problems - `lib-pam` broke the logins - 8Gig of `/system` partition was hogged up by users installing `vscode` and `python3` *(which I see is now installed in v19.2.5! by default (good))* - several other minon issues due to `unattended-updates` - No steps to configure reset password (Couldn't find) ## Possible feature updates - Increase the max VM size to 20Gig? - Make sure `python3` is installed by default (lot of students asked for it) - Students **will** run `VSCode Server`. What's the best way to stop/allow them? - Install it in ansible config / other way - what happens January 2021 once `python 2.7` is dropped? Does `pip2` stop working? How does that impact us? - Should be fine for now. - Can we think about disabling `unattended-updates`? I understand not a good idea in PROD, but if it breaks something during the semester, migrating to a newer version might not be up the alley of the TA incharge. my argument is that the VM in on a private subnet anyway. - Set in anisble to disable `unattended-updates` - Make it togglable in ansible - TA tracks major CVE ## Pico NG and Future - What's the status of PicoNG? - I vaguely remember @Ivan recommending shifting to it, but maybe I misunderstood. Why aren't we going for it? (Just curious) - Lot of current problems depend on `python 2.7`. Will they run on PicoNG? What's the best way to update them so they work with `Pico2019` and be easy to make compatible with `PicoNG`? ## Any Recommendations - @hashprks plans to update 14-741(Info Sec) and 14-828(Browser Sec) CTF problems. Any recommendations with the future in mind to update the problems? ## TODOs - Increase disk space - Make vagrant param - Unattended updates - Make ansible - For binary / general problems - navigating to /problems/.... won't work (on picoNG in future) - use remote version if possible - Migrate problems that use python2 to python3 - SQLite dependency