$SAFE >= 2

[Mark Volkmann]

When $SAFE is >=3D 2 then code can't be loaded from "globally writable loca=
tions".
Can someone clarify what a "globally" writable location is?
What locations are not globally writable?

--=20
R. Mark Volkmann
Partner, Object Computing, Inc.

 

[Rob Rypka]

------=_Part_6208_4071040.1126985836293
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

=20
When $SAFE is >=3D 2 then code can't be loaded from "globally writable=20
locations".
Can someone clarify what a "globally" writable location is?
What locations are not globally writable?
=20

I assume you're getting this out of the "pick axe" book. Later down, they=
=20
refer to it also as "world writable," a term you might be familiar with.

It just means the permissions on the file/directory are such that any user=
=20
on the host has the ability to write to the file, rather than just a=20
particular user or group. If your system hosting the program is accessable=
=20
to lots of people, it means you could load a program that was changed and=
=20
possibly harmful.

I really don't know how it's handled on FAT filesystems (which have no=20
permission mechanism), but I assume it considers those bad as well.

Here's the first UNIX file permission tutorial that came up on Google -=20
looks decent:
http://www.dartmouth.edu/~rc/help/faq/permissions.html

Hope that helps you out.

Rob

------=_Part_6208_4071040.1126985836293--

 

[Mark Volkmann]

=20
I assume you're getting this out of the "pick axe" book.
Yes.

Later down, they
refer to it also as "world writable," a term you might be familiar with.

Ah, if I had seen that it would have helped. What page do you see that on?
=20

It just means the permissions on the file/directory are such that any use= r
on the host has the ability to write to the file, rather than just a
particular user or group. If your system hosting the program is accessabl= e
to lots of people, it means you could load a program that was changed and
possibly harmful.
=20
I really don't know how it's handled on FAT filesystems (which have no
permission mechanism), but I assume it considers those bad as well.

I tried the following under Windows and Ruby didn't complain.

$SAFE =3D 2
load 'moreCode.rb' # just contains a puts

Shouldn't it have complained?

Here's the first UNIX file permission tutorial that came up on Google -
looks decent:
http://www.dartmouth.edu/~rc/help/faq/permissions.html
=20
Hope that helps you out.

Thanks!

--=20
R. Mark Volkmann
Partner, Object Computing, Inc.

 

[Rob Rypka]

------=_Part_6236_17462938.1126991451546
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline