In message <[EMAIL PROTECTED]>, Stefan =?iso-8859-1
>And that is what this thread is about: Secure removal of data from
>storage media. There definitely is a difference between RLL (as in
>1,7i RLL) and modern PRML drives under this aspect.
No there isn't.
It's been proven again and again that
On Mon, Nov 24, 2003, Pawel Jakub Dawidek wrote:
> If one is using strictly defined types as uint8_t, uint16_t, int32_t, etc.
> those macros are helpful IMHO, because futher value size changes does not
> affects code for byte order managing. This also does not hit perfromance,
> because this should
On Tuesday 25 November 2003 01:36, Leo Bicknell wrote:
> In a message written on Mon, Nov 24, 2003 at 03:00:12PM +1030, Daniel
O'Connor wrote:
> > make release will make an directory suitable to put on a CD or DVD. It's
> > just that if you use a DVD you can fit a lot more packages/distfiles on
>
On Tue, Nov 18, 2003 at 04:31:32PM -0800, Rayson Ho wrote:
> I am wondering if it is useful to have a "secure" file flag??
>
> The secure file flag will be set for files that contain sensitive data.
> Then the OS will take special care when operating on those "secure"
> files.
>
> e.g. when delet
On 2003-11-24 12:20 +0100, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote:
> Stefan Eßer <[EMAIL PROTECTED]> writes:
> > Ok. I've also thought some about this, and I think that different media
> > might need different methods (i.e. MFM vs. RLL vs. PRML, but also vs.
> > Flash media).
>
> PRML is n
Tried this on current, but no responses...maybe some one here has some ideas?
Hello,
I looking to extend the smartmontools support
(/usr/ports/sysutils/smartmontools) to include support for drives behind
a TWE device.
I looked at the source for the TWE driver, and it seems to support what
I need
i386/FreeBSD-4.x/lkm.
How does one get into 'realmode' inside a kernel driver?
The reason for the need is a tight timeing loop that measures the lenght of
pulses. And disableing interrupts is just not enough.
Target cpu's are AMD K5 + AMD XP.
Asfair when reading cycles per opcode. The number of
In a message written on Mon, Nov 24, 2003 at 03:00:12PM +1030, Daniel O'Connor wrote:
> make release will make an directory suitable to put on a CD or DVD. It's just
> that if you use a DVD you can fit a lot more packages/distfiles on the disk
> (which make release doesn't do for you anyway).
We
Travis Campbell and I are looking at apcupsd to get it working with
the APC RS/XS series of USB capable UPSs. We're concentrating on
4.x.
Some work has been done in this area by Riccardo Torrini. See
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=57225+0+archive/2003/free
bsd-hardware/20030608.
On Sun, Nov 23, 2003 at 08:50:45PM -0500, Michael E. Mercer wrote:
> Hello peoples,
>
> I posted this to questions with no reply, I was hoping
> someone here may be able to give some insight.
>
>
> Question: Should I be able to open /dev/ugen0 more than once?
>
> I am using FreeBSD 4.9-Stable,
Hi,
i have stability problems with a xeon dual (same problems with UP
kernel) and 4 GB of memory.
After about 1 day, one apache does not deliver content and no logins
are performed (console, ssh, ftp, ...) anymore. Console shows only
motd message and nothing more.
I have tried to set the followin
Stefan Eßer <[EMAIL PROTECTED]> writes:
> Ok. I've also thought some about this, and I think that different media
> might need different methods (i.e. MFM vs. RLL vs. PRML, but also vs.
> Flash media).
PRML is not an encoding scheme like MFM or RLL, it is an algorithm for
recovering a bitstream f
On 2003-11-23 10:11 -0800, Wes Peters <[EMAIL PROTECTED]> wrote:
> > Encrypting data and secure removal of data are orthogonal and in case
> > you need one, the other propbably won't be a good choice.
>
> Both are completely adequate to protect the data on the disk from
> disclosure.
Yes, if eff
Hello hackers...
Macros in attached patch are designed for doing life a little easier.
If one is using strictly defined types as uint8_t, uint16_t, int32_t, etc.
those macros are helpful IMHO, because futher value size changes does not
affects code for byte order managing. This also does not hit
I got this message :
# fsck_ext2fs -d /dev/ad3
** /dev/ad3
BAD SUPER BLOCK: MAGIC NUMBER WRONG
ioctl (GCINFO): Inappropriate ioctl for device
/dev/ad3: can't read disk label
is this due to geom or to FreeBSD 5.1? It worked on a 4.6.2.
Though /dev/ad3 could be mounted when it was clean.
___
In message <[EMAIL PROTECTED]>, Stefan =?iso-8859-1
?Q?E=DFer?= writes:
>Yes, probably. But encryption is only as good as key
>management and secure storage (and deletion) of keys.
>How do you implement unattended reboot, if you consider
>unauthorized (physical) access to your system as one
>of
On 2003-11-23 18:04 +0100, Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
> 1. Look for BIO_DELETE in the kernel.
Seems that BIO_DELETE isn't really supported anymore
(according to a comment in your GEOM sources ;-)
AFAICT, BIO_DELETE can't easily be made a long running
operation (taking tens of
On 2003-11-23 17:31 +0100, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote:
> Stefan Eßer <[EMAIL PROTECTED]> writes:
> > What I'm suggesting is to have the obliteration implemented as an
> > add on to the dirty buffer flush, with the difference that the
> > buffer contents is prepared for the next
18 matches
Mail list logo