Hello,
> thanks, I tried all that onwww.sagenb.org.
> I could access files many of the files of 221 visible 'users' in /
> home,
> like some vincent, a certain notorious wstein, a victor, a carlos, a
> Ulrike etc. by
>
> import os; dn = '/home/some_user'; os.listdir(dn);
> os.chdir(dn); fin = open('some_file'); fin.read(); ...
That is a relative privacy leak in Sage which will be resolved by
using a database instead of files for worksheets and setting well
permissions for it (planned for google summer of code I think). But
Sage can not avoid all problems arising from having a python console
on a remote computer !
> but I could _not_ access a directory /home/risse which is me onwww.sagenb.org
> Imho this is a security leak and at the same time rather dodgy:
> I still do not know where to find my *.sage, *.py or *.pyx files
> onwww.sagenb.org
> which I want to import into another worksheet. Any help very much
If you do not have access to the computer sagenb.org (ssh or telnet or
ftp or anything else) you may not use it for this kind of stuff. But
as you have a python console access and some write permissions you can
do
{{{
sage: f = open("/home/a path to which I have right to write/my
file.sage")
sage: f.write("def f(x):\n")
sage: f.write(" return x+1")
sage: f.close()
}}}
{{{
sage: attach "home/a path to which I have right to write/my
file.sage"
}}}
{{{
sage: f(3)
4
}}}
It is neither useful nor a good practice. If you want to attach .sage
or .py files, the only way is to install a server on your own
computer.
Vincent
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
