[EMAIL PROTECTED] on Wed 6/08 12:13 -0500:
And anyone who can get local root on his/her workstation
can use 'amrecover' to obtain any filesystem backed up from
'localhost', since localhost is valid on any system.
then what prevents joe user from just modifying /etc/hosts
on his machine to
Jon == Jon LaBadie [EMAIL PROTECTED] writes:
[...]
Jon That might be one reason to encrypt the backups.
Jon A method was posted using pgp about 18 months ago.
The reference I found was from 1999, and was very fuzzy on details.
If someone is actually doing this, could they update the
On Tue, Aug 05, 2003 at 12:13:38PM -0400, Scott Mcdermott wrote:
anyone know of an easy way to get columns to appear somewhat
legibly without hacking the amanda source?
localhostuser-e1 12390460 12390460.00 --33:36 6147.200195
33:36 6146.399902
I don't recall ever
On Wednesday 06 August 2003 14:25, Scott Mcdermott wrote:
[EMAIL PROTECTED] on Wed 6/08 12:26 -0500:
How far do you want to take your paranoia? I take it
pretty far as a system admin, but I think I know where to
draw the line.
what are you talking about? you think if anyone with root on
any
On Tuesday 05 August 2003 16:25, Russell Adams wrote:
Also, get rid of 'localhost'! Amanda is a client/server program
and will only work right (although no effect on this formatting
problem) for all functions if the FQDN of the machine is used. We
should fix a filter to add this to the sig
On Wed, Aug 06, 2003 at 05:06:40PM -0400, Scott Mcdermott wrote:
Paul Bijnens on Wed 6/08 22:45 +0200:
But if you only have one computer and it is the server and
client itself, then there is indeed no problem to using
localhost. (But don't say we didn't warn you :-)
now *that* is a
Gene Heskett on Tue 5/08 20:02 -0400:
I've heard this before. What exactly is the problem with
localhost? Could you elaborate?
Primarily its a security issue because *any* machine can
be localhost. By using the FQDN, there is then no
ambiguity as to which machine is being addressed.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 06 August 2003 11:45, Scott Mcdermott wrote:
Gene Heskett on Tue 5/08 20:02 -0400:
I've heard this before. What exactly is the problem with
localhost? Could you elaborate?
Primarily its a security issue because *any* machine
Paul Bijnens on Wed 6/08 22:45 +0200:
But if you only have one computer and it is the server and
client itself, then there is indeed no problem to using
localhost. (But don't say we didn't warn you :-)
now *that* is a reasonable answer.
I'm still concerned though, that anyone on any client
Scott Mcdermott wrote:
[EMAIL PROTECTED] on Wed 6/08 12:26 -0500:
How far do you want to take your paranoia? I take it
pretty far as a system admin, but I think I know where to
draw the line.
what are you talking about? you think if anyone with root on
any client amanda backs up, or the DNS
[EMAIL PROTECTED] on Wed 6/08 12:26 -0500:
How far do you want to take your paranoia? I take it
pretty far as a system admin, but I think I know where to
draw the line.
what are you talking about? you think if anyone with root on
any client amanda backs up, or the DNS admin, can restore
And anyone who can get local root on his/her workstation
can use 'amrecover' to obtain any filesystem backed up from
'localhost', since localhost is valid on any system. This
applies to all those sensitive file systems that are stored
on your server and password/access protected to keep the
anyone know of an easy way to get columns to appear somewhat
legibly without hacking the amanda source?
here's what output looks like for me:
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- --
localhost
Also, get rid of 'localhost'! Amanda is a client/server program and
will only work right (although no effect on this formatting problem)
for all functions if the FQDN of the machine is used. We should fix
a filter to add this to the sig of every message posted thru the
list. If you
14 matches
Mail list logo
