Gnus development mailing list
 help / color / mirror / Atom feed
From: Alan Shutko <ats@acm.org>
Subject: Re: Gnus Access mail spool by ssh
Date: 08 Jul 2000 22:03:57 -0400	[thread overview]
Message-ID: <m3u2e0qctu.fsf@acm.org> (raw)
In-Reply-To: Harry Putnam's message of "08 Jul 2000 14:02:27 -0700"

Harry Putnam <reader@newsguy.com> writes:

> Now I want to have a laptop running FreeBSD 4.0 networked to desktop
> running Redhat linux, be able to  view/manipulate mail on the parent machine
> but don't want to  setup pop, imap or  special sendmail stuff.  I
> don't want more daemons running that can be exploited from the internet.
> And haven't really looked into firewall technique.

Well, first, you should _really_ look into the firewall technique.
Otherwise, you'll be jumping through hoops that nobody else has
considered, because they've all set up a firewall and forgotten about
it.

If you don't want to do that... well, you could use the ssh to set up
a ppp tunnel between your computers, and run NFS, imap, or whatever
over that.  In some cases, that makes sense (ie, laptop halfway across
the continent, over very untrusted ethernet).  But not in a home
network.  Unless you have a very untrusted home network (ie, both
machines are just connected via a hub to a cable modem) it's much more
convenient to set up some firewall rules on the host connected to the
internet, and trust the internal network.  ssh was _not_ designed to
be a mail protocol, and as Kai pointed out, locking issues will be a
bitch.

I'm not sure precisely how you are expecting ssh to access
/var/spool/mail on the other host, as it doesn't set up any file
access from this side... you could send over ssh parent "cat
/var/spool/mail/ats", but editing the file will not be easy.  You
could do some weird use of files to lock on the other side, and scp
the file over... but it would be a mess.

-- 
Alan Shutko <ats@acm.org> - In a variety of flavors!
125 days, 13 hours, 37 minutes, 6 seconds till we run away.
A PC is for manipulation of data, not the manipulation of thought.



  parent reply	other threads:[~2000-07-09  2:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-08 21:02 Harry Putnam
2000-07-08 23:08 ` Kai Großjohann
2000-07-09  2:03 ` Alan Shutko [this message]
2000-07-10  4:56   ` Harry Putnam
2000-07-10 11:48     ` Kai Großjohann
     [not found]     ` <lfllmzam504.fsf@rupert.informatik.uni-stuttgart.de>
2000-07-11 12:39       ` Harry Putnam
2000-07-11 22:28         ` Alexandre Oliva
2000-07-12  0:01           ` Harry Putnam
2000-07-12  2:31             ` Alexandre Oliva
2000-07-12  8:06               ` Kai Großjohann
2000-07-12  8:52                 ` Nuutti Kotivuori
2000-07-12 11:26                   ` Harry Putnam
2000-07-12 14:54                     ` Nuutti Kotivuori
2000-07-12 15:10                       ` Harry Putnam
2000-07-12 17:07                         ` Kai Großjohann
2000-07-12 19:22                       ` Harry Putnam
2000-07-12 19:42                         ` Alan Shutko
2000-07-12 21:28                           ` Harry Putnam
2000-07-13  3:50                             ` Nuutti Kotivuori
2000-07-13  3:46                         ` Nuutti Kotivuori
2000-07-14 11:02                           ` Harry Putnam
2000-07-16 15:11                             ` Nuutti Kotivuori
2000-07-15  0:29                   ` Simon Josefsson
2000-07-10 12:00 ` Nuutti Kotivuori

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=m3u2e0qctu.fsf@acm.org \
    --to=ats@acm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).