On 2019-02-03, Juan Francisco Cantero Hurtado wrote:
> On Sun, Feb 03, 2019 at 11:35:52AM +0300, Denis wrote:
>> How to enable AES-NI AES system wide hardware acceleration support for
>> crypto disciplines like LibreSSL, softraid0 crypto etc?
>
> If your CPU supports AES-NI, the kernel and base
Hi,
I'm trying to configure Nextcloud on a subdomain. My config has 2
vhosts and connection max request body is not respected for my subdomain.
default vhost:
server "default" {
listen on * port 80
location "/.well-known/acme-challenge/*" {
root "/acme"
request strip 2
Am 3. Februar 2019 16:43:20 MEZ schrieb Chris Narkiewicz :
>Hi,
>
>I'm trying to configure Nextcloud on a subdomain. My config has 2
>vhosts and connection max request body is not respected for my
>subdomain.
>
>default vhost:
>
>server "default" {
>listen on * port 80
>
>location
I'm trying to compile a GENERIC.MP kernel on amd64
6.4 -stable. I've followed the instructions in the
FAQ for building a custom kernel, but the 'make'
step fails with an unknown argument: '-msave-args'
error. I've copied the compiler messages and dmesg
below. Suggestions for a cure or workaround
On Sun, Feb 03, 2019 at 11:35:52AM +0300, Denis wrote:
> How to enable AES-NI AES system wide hardware acceleration support for
> crypto disciplines like LibreSSL, softraid0 crypto etc?
If your CPU supports AES-NI, the kernel and base software will use it by
default.
--
Juan Francisco Cantero
On Sun, Feb 03, 2019 at 03:43:20PM +, Chris Narkiewicz wrote:
> Hi,
>
> I'm trying to configure Nextcloud on a subdomain. My config has 2
> vhosts and connection max request body is not respected for my subdomain.
this has been fixed in current. Wild guess, you are on 6.4?
This diff should
Good evening,
We inserted a 2x40G NIC into one of our old franken-pc's, and got this:
ixl0 at pci2 dev 0 function 0 "Intel XL710 QSFP+" rev 0x02: port 0, FW
5.0.40043 API 1.5, msi, address 0c:c4:7a:5e:f9:c8
ixl0: unable to query phy types
ixl1 at pci2 dev 0 function 1 "Intel XL710 QSFP+" rev
John Rigg wrote:
> I'm trying to compile a GENERIC.MP kernel on amd64
> 6.4 -stable.
No way, you are not. Only -current has that, as of a few days ago.
I've followed the instructions in the
> FAQ for building a custom kernel, but the 'make'
> step fails with an unknown argument:
And since you are doing this with -current *ALL OVER THE PLACE*
there are instructions that if you have trouble you should upgrade
to a snapshot.
Those instructions to exist the noise on the list everytime we
make a change and people don't notice or understand it and suddenly
they are in over
On Sun, Feb 03, 2019 at 02:51:08PM -0700, Theo de Raadt wrote:
> John Rigg wrote:
>
> > I'm trying to compile a GENERIC.MP kernel on amd64
> > 6.4 -stable.
>
> No way, you are not. Only -current has that, as of a few days ago.
I used the wrong cvs command and didn't spot it. Stupid mistake.
On 2019-02-03, Stuart Henderson wrote:
>> If your CPU supports AES-NI, the kernel and base software will use it by
>> default.
>
> You do need to pick suitable ciphers though. And it is only supported
> on OpenBSD/amd64 not OpenBSD/i386.
Only the kernel support (IPsec, softraid crypto) is
How to enable AES-NI AES system wide hardware acceleration support for
crypto disciplines like LibreSSL, softraid0 crypto etc?
On 2019-02-02, Rachel Roch wrote:
> Hi,
>
> Subject line says it all really, I'm looking to hear of people's experiences
> with recent models of Dell single-socket machines (i.e. R230/R330/R340 -
> especially the newest R340, obviously!).
>
> I'm looking for a decent machine with enterprisey
Denis wrote:
> How to enable AES-NI AES system wide hardware acceleration support for
> crypto disciplines like LibreSSL, softraid0 crypto etc?
Hi, just enable it in bios.
14 matches
Mail list logo
