All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Leonard Milcin, Jr" <thervoy@post.pl>
To: Kenny Mann <Kennymann@cdrobot.com>, linux-kernel@vger.kernel.org
Subject: Re: Help with virus/hackers
Date: Thu, 17 Apr 2003 19:24:33 +0200	[thread overview]
Message-ID: <3E9EE351.2000608@post.pl> (raw)
In-Reply-To: <78939086E7E52D4A9CDBEAB7A609781201F68B@mainsrv.cdrobot.com>

Kenny Mann wrote:

>Another method, that just popped to mind, is perhaps having
>Some form of a network share somewhere to which only write access
>Is granted. No on could list the files, no one could read the files
>(except for admin of course!). I'm unsure if it's possible to allow
>Only additions to files and no deletions... Just a thought.
>
>Samba Masters> Would this be possible via samba?
>

Yes, it is possible,  at least using ftp. If you create ftp, or ftp-like 
service that
allow only storing data in one particular directory for each user 
account (or server
account if we would like to name it this way) and no listing directory 
or reading
files (just a matter of file/dir permissions) then we got the solution. 
Server must
ensure that no one could read or delete a file.

It is even possible to create service with anonymous login. It should serve
one directory, for writing only (no read or list operations) as in 
previous case.
Users should store files with uniqe names, to prevent write errors when new
file have the same name as previously created.

It meets all your requirements. And it is possible to configure almost 
all common
ftp deamons to do their work this way.

Leonard Milcin, Jr


  reply	other threads:[~2003-04-17 17:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 16:34 Help with virus/hackers Kenny Mann
2003-04-17 17:24 ` Leonard Milcin, Jr [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-17 20:56 Kenny Mann
2003-04-17 18:12 Kenny Mann
2003-04-17 14:15 joe briggs
2003-04-17 12:42 ` Alan Cox
2003-04-17 13:55 ` Richard B. Johnson
2003-04-17 14:12   ` Alan Cox
2003-04-17 15:31     ` John Jasen
2003-04-17 15:45     ` John Bradford
2003-04-17 16:26       ` Alan Cox
2003-04-17 18:00         ` John Bradford
2003-04-17 17:17       ` Christopher Curtis
2003-04-17 14:12   ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E9EE351.2000608@post.pl \
    --to=thervoy@post.pl \
    --cc=Kennymann@cdrobot.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.