On (21/03/2012 11:13), Vincent Hoffman wrote:
> On 21/03/2012 10:47, Andrey V. Elsukov wrote:
> > On 21.03.2012 14:09, Victor Balada Diaz wrote:
> >> You would need to modify UFS, or maybe do something like CFS[1]. CFS works
> >> as an NFS server and you could modify it to only cipher the needed fi
On Wed, Mar 21, 2012 at 05:18:07PM +0200, Vitaly Magerya wrote:
> Baptiste Daroussin wrote:
> > when a package can be installed in both i386 and amd64
> >
> > and maybe in the Makefile:
> >
> > PKGARCH=i386 amd64
> >
> > or
> >
> > PKGARCH=x86:32 x86:64
>
> Baptiste, if ABI/arch ids wi
On Wed, Mar 21, 2012 at 03:59:38PM +0100, Alexander Leidinger wrote:
> Quoting Baptiste Daroussin (from Wed, 21 Mar 2012
> 14:59:20 +0100):
>
> > On Wed, Mar 21, 2012 at 02:34:03PM +0100, Alexander Leidinger wrote:
> >> Quoting Bruce Cran (from Tue, 20 Mar 2012
> >> 14:26:42 +):
> >>
> >
Baptiste Daroussin wrote:
> when a package can be installed in both i386 and amd64
>
> and maybe in the Makefile:
>
> PKGARCH= i386 amd64
>
> or
>
> PKGARCH= x86:32 x86:64
Baptiste, if ABI/arch ids will leak out to port Makefiles (i.e. I will
need to care about them), then please lea
Quoting Baptiste Daroussin (from Wed, 21 Mar 2012
14:59:20 +0100):
On Wed, Mar 21, 2012 at 02:34:03PM +0100, Alexander Leidinger wrote:
Quoting Bruce Cran (from Tue, 20 Mar 2012
14:26:42 +):
> On 20 Mar 2012, at 10:20, Konstantin Belousov wrote:
>
>> i386-32 and amd64-64 is weird and
On Wed, Mar 21, 2012 at 02:34:03PM +0100, Alexander Leidinger wrote:
> Quoting Bruce Cran (from Tue, 20 Mar 2012 14:26:42 +):
>
> > On 20 Mar 2012, at 10:20, Konstantin Belousov wrote:
> >
> >> i386-32 and amd64-64 is weird and confusing.
> >>
> >> IMO, you should go either with x86-{32,64} n
Quoting Bruce Cran (from Tue, 20 Mar 2012 14:26:42 +):
On 20 Mar 2012, at 10:20, Konstantin Belousov wrote:
i386-32 and amd64-64 is weird and confusing.
IMO, you should go either with x86-{32,64} names, or with i386/amd64,
not with a mix.
Would we ever want to support something like x3
On 21/03/2012 10:47, Andrey V. Elsukov wrote:
> On 21.03.2012 14:09, Victor Balada Diaz wrote:
>> You would need to modify UFS, or maybe do something like CFS[1]. CFS works
>> as an NFS server and you could modify it to only cipher the needed files.
>>
>> Also you could write a simple FS on FUSE, b
On 21.03.2012 14:09, Victor Balada Diaz wrote:
> You would need to modify UFS, or maybe do something like CFS[1]. CFS works
> as an NFS server and you could modify it to only cipher the needed files.
>
> Also you could write a simple FS on FUSE, but last time i checked, our
> FUSE support had some
On 21.03.2012 13:47, Harald Schmalzbauer wrote:
> Was such a policy based file encryption control doable with GEOM?
> Maybe it's easier to make use of existing tools like gpg with GEOM
> interaction?
> I don't want to reinvent any file encryption, I just need some automatic
> encryption (without _m
On Wed, Mar 21, 2012 at 10:47:45AM +0100, Harald Schmalzbauer wrote:
> Hello,
>
> I personally don't have the need to encrypt whole filesystems and if I
> need to transfer sensitive data I use gpg to encrypt the tarball or
> whatever.
> But, I'd like to see some single files encrypted on my syste
Hello,
I personally don't have the need to encrypt whole filesystems and if I
need to transfer sensitive data I use gpg to encrypt the tarball or
whatever.
But, I'd like to see some single files encrypted on my systems, eg.
wpasupplicant.conf, ipsec.conf aso.
Since I recently secured LDAP queries
12 matches
Mail list logo