[K12OSN] A couple of questions

[Terrell Prude', Jr.]

I don't know how yet to do #2 (I just haven't had to yet), but maybe 
this'll help for #1.

I recall having to do this w/ a publicly accessible FTP server.  Set it 
execute/write (don't give 'em the "read" bit), and they can upload to 
their heart's content, but they can't see any files once they're in.  
Doing a "ls -alsF" shows absolutely nada.

Assume you have the drop folder set as root:root ownership.  You'd do this:

     chmod 773 /my/drop/folder/

and voila, you're done!  If a smart-aleck kid tries something like "rm 
-rf *" in that directory, it won't work, 'cause there's no way for the 
rm process to get any filenames, 'cause you denied them "read" 
permission on the directory.

Of course, test this before you put it into production.

The other way is to have 'em email it to you.  We assume here that 1.) 
you don't give your students access to your email account, and 2.) 
they're not emailing you HUMONGO file attachments (hopefully your mail 
admins have implemented attachment size limits!).

--TP

John P. Conlon wrote:

> 1. How do I go about creating a drop folder that students can put work 
> in but not access after they have done so?
>
> 2. How do I go about setting things so that a password is required in 
> order to print?
>
> Thanks
> Bye
> Pat
>