|
| 1 | +# Jupyter Security Bi-weekly Meeting |
| 2 | + |
| 3 | +## April 4, 2023 |
| 4 | + |
| 5 | +| Name | affiliation| username | |
| 6 | +| -------------------| -----------| -----------------| |
| 7 | +| Jason Weill | AWS | @JasonWeill | |
| 8 | +| Joe Lucas | NVIDIA | @josephtlucas | |
| 9 | +| Rollin Thomas | NERSC | @rcthomas | |
| 10 | +| Rick Wagner | UCSD | @rpwagner | |
| 11 | + |
| 12 | +* Workshop: |
| 13 | + * What do we want to get out of it? |
| 14 | + * Should we require best practices of other Jupyter subprojects |
| 15 | + * Would discussing this at the workshop be a good use of the opportunity? |
| 16 | + * Socialize and get feedback on this |
| 17 | + * Do the subprojects want guidance on this? |
| 18 | + * Dependency analysis vs actual issues with Jupyter code? |
| 19 | + * Logging and auditing w/Zeek? |
| 20 | + * What is there even for web HTTP/websockets applications? |
| 21 | + * Instrumentation at various levels of the stack |
| 22 | + * Different situations and their corresponding security best practices: |
| 23 | + * On my laptop |
| 24 | + * Dashboards (voila) |
| 25 | + * Multi-user w/JupyterHub etc |
| 26 | + * OWASP: https://owasp.org/ |
| 27 | + * What is the calendar and schedule? |
| 28 | + * Summit Tuesday, Wednesday, Thursday, plenaries Wednesday |
| 29 | + * From the TrustedCI perspective, things still in flux, more content than previously thought |
| 30 | + * Possibility that we wind up on Friday, or Monday |
| 31 | + |
0 commit comments