From: Florian Philipp <lists@f_philipp.fastmail.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Recovering root password
Date: Tue, 25 Mar 2008 18:14:19 +0100 [thread overview]
Message-ID: <1206465259.30987.62.camel@NOTE_GENTOO64.PHHEIMNETZ> (raw)
In-Reply-To: <49bf44f10803250932q138a1627mba929844d0218689@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
On Tue, 2008-03-25 at 09:32 -0700, Grant wrote:
> > > > On a notebook, there isn't an OS in existence that is immune to a
> > > > LiveCD.
> > >
> > > Linux is. In the sense that you can't get at the data if the disc is
> > > encrypted, even not with a LiveCD. You can only destroy/overwrite it.
> >
> > Yes, I realised that when typing the original, but left it as is - too
> > many IF conditionals would be needed to be accurate and English is
> > almost useless at getting IFs to parse correctly :-)
> >
> > Passwords come from a time when users had terminals that log onto
> > machines that are somewhere else and the user can't lay a finger on
> > them. Things have indeed changed since 1978
>
> Would the type of filesystem encryption you guys are talking about be
> unsuitable for a high-traffic server because of performance
> considerations?
>
> - Grant
I did some benchmarks recently, posted them on gentoo-security. Long
story short: Even my 64bit single-core Celeron can do 256bit AES, 320bit
Anubis or 256bit Twofish faster than writing data to the disk (37MB/s).
Blowfish, CAST and Serpent are too slow.
128bit AES (which I deem good enough for the near future) causes around
40% CPU-utilization.
Whether it is suitable for your server depends on its usage patterns.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-25 17:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 20:30 [gentoo-user] Recovering root password Grant
2008-03-24 20:34 ` Boris Fersing
2008-03-24 20:39 ` Dale
2008-03-24 20:49 ` Florian Philipp
2008-03-24 20:40 ` Ricardo Saffi Marques
2008-03-24 20:45 ` Steven Lembark
2008-03-24 20:49 ` Ricardo Saffi Marques
2008-03-25 7:12 ` Dirk Heinrichs
2008-03-24 21:57 ` Neil Bothwick
2008-03-24 23:52 ` Steven Lembark
2008-03-25 0:14 ` Grant
2008-03-24 20:42 ` Alan McKinnon
2008-03-25 5:41 ` Uwe Thiem
2008-03-25 8:03 ` Liviu Andronic
2008-03-25 8:09 ` Dirk Heinrichs
2008-03-25 8:25 ` Alan McKinnon
2008-03-25 8:32 ` Dirk Heinrichs
2008-03-25 15:28 ` Alan McKinnon
2008-03-25 16:32 ` Grant
2008-03-25 17:04 ` Uwe Thiem
2008-03-25 17:26 ` Grant
2008-03-25 21:28 ` [gentoo-user] " Michael Schmarck
2008-03-26 8:07 ` [gentoo-user] " Dirk Heinrichs
2008-03-26 10:04 ` Uwe Thiem
2008-03-25 17:14 ` Florian Philipp [this message]
2008-03-25 17:55 ` Steven Lembark
2008-03-25 19:12 ` Alan McKinnon
2008-03-25 9:12 ` Neil Bothwick
2008-03-25 12:08 ` Liviu Andronic
2008-03-25 14:44 ` Neil Bothwick
2008-03-25 17:53 ` Steven Lembark
2008-03-25 18:02 ` Dirk Heinrichs
2008-03-25 20:06 ` Wael Nasreddine
2008-03-26 7:59 ` Dirk Heinrichs
2008-03-25 19:23 ` Neil Bothwick
2008-03-25 8:30 ` Wael Nasreddine
2008-03-25 17:23 ` Mick
2008-03-25 20:02 ` Wael Nasreddine
2008-03-25 17:51 ` Steven Lembark
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=1206465259.30987.62.camel@NOTE_GENTOO64.PHHEIMNETZ \
--to=lists@f_philipp.fastmail.net \
--cc=gentoo-user@lists.gentoo.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