On Monday, January 27, 2020 at 7:58:27 AM UTC-8, Dima Pasechnik wrote:
>
> I suppose the idea of closing ~/.sage/ to the world was that it may 
> contain something like (salted or not?) passwods for sagenb, 
> as well as sagenb notebooks, so that students on the same host don't 
> have a way to peek at each other homework, etc. 
>
> Indeed. If someone wants to be careful about it, sage might refuse to use 
or save information there it considers sensitive. Ssh does something 
similar when it's not satisfied with the permissions of the configuration 
directory. You'd have to decide if group readable is vulnerable, though.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/96c9b4fd-c430-4d20-8b11-26aa2e9ab97f%40googlegroups.com.

Reply via email to