Re: [gentoo-user] google SMTP with postfix - Password not accepted

[Peter Humphrey]

On Tuesday, 20 June 2023 09:55:10 BST William Kenworthy wrote:
> getmail can facilitate getting googlemail into postfix.  In my case, it
> fetches an mail then invokes sendemail to forward into postfix.  The
> docs for the google side of the equation are quite good.

Coming to this after a while, can you point me to the one that helps, please? 
I've had a look round but I haven't found anything helpful. Thanks.

-- 
Regards,
Peter.

Re: [gentoo-user] Getting output of a program running in background after a crash

[Dale]

Frank Steinmetzger wrote:
> Am Thu, Oct 12, 2023 at 08:35:21PM -0500 schrieb Dale:
>
>> Frank Steinmetzger wrote:
>>> Am Thu, Oct 12, 2023 at 10:44:39PM +0100 schrieb Michael:
>>>
 Why don't you test throughput without encryption to confirm your 
 assumption?
>>> What does `cryptsetup benchmark` say? I used to use a Celeron G1840 in my 
>>> NAS, which is Intel Haswell without AES_NI. It was able to do ~ 150 MB/s 
>>> raw 
>>> encryption throughput when transferring to or from a LUKS’ed image in a 
>>> ramdisk, so almost 150 % of gigabit ethernet speed.
>> […]
>> I've never used that benchmark.  Didn't know it exists.  This is the
>> results.  Keep in mind, fireball is my main rig.  The FX-8350 thingy. 
>> The NAS is currently the old 770T system.  Sometimes it is a old Dell
>> Inspiron but not this time.  ;-)
>>
>> root@fireball / # cryptsetup benchmark
>> […]
>> # Algorithm |   Key |  Encryption |  Decryption
>>     aes-cbc    128b    63.8 MiB/s    51.4 MiB/s
>>     serpent-cbc    128b    90.9 MiB/s   307.6 MiB/s
>>     twofish-cbc    128b   200.4 MiB/s   218.4 MiB/s
>>     aes-cbc    256b    54.6 MiB/s    37.5 MiB/s
>>     serpent-cbc    256b    90.4 MiB/s   302.6 MiB/s
>>     twofish-cbc    256b   198.2 MiB/s   216.7 MiB/s
>>     aes-xts    256b    68.0 MiB/s    45.0 MiB/s
>>     serpent-xts    256b   231.9 MiB/s   227.6 MiB/s
>>     twofish-xts    256b   191.8 MiB/s   163.1 MiB/s
>>     aes-xts    512b    42.4 MiB/s    18.9 MiB/s
>>     serpent-xts    512b   100.9 MiB/s   124.6 MiB/s
>>     twofish-xts    512b   154.8 MiB/s   173.3 MiB/s
>> root@fireball / #
> Phew, this looks vry slow. As you can clearly see, this is not enough to 
> even saturate Gbit ethernet. Unfortunately, I don’t have any benchmark data 
> left over from the mentioned celeron.
> (Perhaps that’s why the industry chose to implement AES in hardware, because 
> it was the slowest of the bunch.)
>
> It looks like there is no hardware acceleration involved. But according to 
> https://en.wikipedia.org/wiki/List_of_AMD_FX_processors#Piledriver-based and 
> https://www.cpu-world.com/CPUs/Bulldozer/AMD-FX-Series%20FX-8350.html it has 
> the extension. I’d say something is amiss in your kernel.
>
> Heck, even my ultra-low-end eeepc with its no-AES Atom processor N450 from 
> 2009 is less than 50 % slower, and for aes-xts 512b it is actually faster! 
> And that was a snail even in its day. It is so low-end that its in-order 
> architecture is not vulnerable to spectre and meltdown. :D It just scrunched 
> several minutes on updating the GPG keyring of its arch linux installation.
>
> eeePC # LC_ALL=C cryptsetup benchmark
> # Tests are approximate using memory only (no storage IO).
> PBKDF2-sha1   228348 iterations per second for 256-bit key
> PBKDF2-sha256 335222 iterations per second for 256-bit key
> PBKDF2-sha512 253034 iterations per second for 256-bit key
> PBKDF2-ripemd160  172690 iterations per second for 256-bit key
> PBKDF2-whirlpool   94705 iterations per second for 256-bit key
> argon2i   4 iterations, 71003 memory, 4 parallel threads (CPUs) for 
> 256-bit key (requested 2000 ms time)
> argon2id  4 iterations, 71506 memory, 4 parallel threads (CPUs) for 
> 256-bit key (requested 2000 ms time)
> # Algorithm |   Key |  Encryption |  Decryption
> aes-cbc128b31.0 MiB/s33.6 MiB/s
> serpent-cbc128b28.1 MiB/s62.9 MiB/s
> twofish-cbc128b28.6 MiB/s31.0 MiB/s
> aes-cbc256b24.0 MiB/s25.6 MiB/s
> serpent-cbc256b28.3 MiB/s62.7 MiB/s
> twofish-cbc256b28.6 MiB/s31.0 MiB/s
> aes-xts256b32.5 MiB/s33.4 MiB/s
> serpent-xts256b50.5 MiB/s60.5 MiB/s
> twofish-xts256b25.6 MiB/s30.7 MiB/s
> aes-xts512b25.0 MiB/s25.6 MiB/s
> serpent-xts512b60.2 MiB/s60.4 MiB/s
> twofish-xts512b30.2 MiB/s30.7 MiB/s
>
>> root@nas:~# cryptsetup benchmark
>> […]
>> # Algorithm |   Key |  Encryption |  Decryption
>>     aes-cbc    128b   130.6 MiB/s   128.0 MiB/s
>>     serpent-cbc    128b    64.7 MiB/s   161.8 MiB/s
>>     twofish-cbc    128b   175.4 MiB/s   218.8 MiB/s
>>     aes-cbc    256b   120.1 MiB/s   122.2 MiB/s
>>     serpent-cbc    256b    84.5 MiB/s   210.8 MiB/s
>>     twofish-cbc    256b   189.5 MiB/s   218.6 MiB/s
>>     aes-xts    256b   167.0 MiB/s   162.1 MiB/s
>>     serpent-xts    256b   173.9 MiB/s   204.5 MiB/s
>>     twofish-xts    256b   204.4 MiB/s   

Re: [gentoo-user] Getting output of a program running in background after a crash

[Frank Steinmetzger]

Am Thu, Oct 12, 2023 at 08:35:21PM -0500 schrieb Dale:

> Frank Steinmetzger wrote:
> > Am Thu, Oct 12, 2023 at 10:44:39PM +0100 schrieb Michael:
> >
> >> Why don't you test throughput without encryption to confirm your 
> >> assumption?
> > What does `cryptsetup benchmark` say? I used to use a Celeron G1840 in my 
> > NAS, which is Intel Haswell without AES_NI. It was able to do ~ 150 MB/s 
> > raw 
> > encryption throughput when transferring to or from a LUKS’ed image in a 
> > ramdisk, so almost 150 % of gigabit ethernet speed.
> […]
> I've never used that benchmark.  Didn't know it exists.  This is the
> results.  Keep in mind, fireball is my main rig.  The FX-8350 thingy. 
> The NAS is currently the old 770T system.  Sometimes it is a old Dell
> Inspiron but not this time.  ;-)
> 
> root@fireball / # cryptsetup benchmark
> […]
> # Algorithm |   Key |  Encryption |  Decryption
>     aes-cbc    128b    63.8 MiB/s    51.4 MiB/s
>     serpent-cbc    128b    90.9 MiB/s   307.6 MiB/s
>     twofish-cbc    128b   200.4 MiB/s   218.4 MiB/s
>     aes-cbc    256b    54.6 MiB/s    37.5 MiB/s
>     serpent-cbc    256b    90.4 MiB/s   302.6 MiB/s
>     twofish-cbc    256b   198.2 MiB/s   216.7 MiB/s
>     aes-xts    256b    68.0 MiB/s    45.0 MiB/s
>     serpent-xts    256b   231.9 MiB/s   227.6 MiB/s
>     twofish-xts    256b   191.8 MiB/s   163.1 MiB/s
>     aes-xts    512b    42.4 MiB/s    18.9 MiB/s
>     serpent-xts    512b   100.9 MiB/s   124.6 MiB/s
>     twofish-xts    512b   154.8 MiB/s   173.3 MiB/s
> root@fireball / #

Phew, this looks vry slow. As you can clearly see, this is not enough to 
even saturate Gbit ethernet. Unfortunately, I don’t have any benchmark data 
left over from the mentioned celeron.
(Perhaps that’s why the industry chose to implement AES in hardware, because 
it was the slowest of the bunch.)

It looks like there is no hardware acceleration involved. But according to 
https://en.wikipedia.org/wiki/List_of_AMD_FX_processors#Piledriver-based and 
https://www.cpu-world.com/CPUs/Bulldozer/AMD-FX-Series%20FX-8350.html it has 
the extension. I’d say something is amiss in your kernel.

Heck, even my ultra-low-end eeepc with its no-AES Atom processor N450 from 
2009 is less than 50 % slower, and for aes-xts 512b it is actually faster! 
And that was a snail even in its day. It is so low-end that its in-order 
architecture is not vulnerable to spectre and meltdown. :D It just scrunched 
several minutes on updating the GPG keyring of its arch linux installation.

eeePC # LC_ALL=C cryptsetup benchmark
# Tests are approximate using memory only (no storage IO).
PBKDF2-sha1   228348 iterations per second for 256-bit key
PBKDF2-sha256 335222 iterations per second for 256-bit key
PBKDF2-sha512 253034 iterations per second for 256-bit key
PBKDF2-ripemd160  172690 iterations per second for 256-bit key
PBKDF2-whirlpool   94705 iterations per second for 256-bit key
argon2i   4 iterations, 71003 memory, 4 parallel threads (CPUs) for 256-bit 
key (requested 2000 ms time)
argon2id  4 iterations, 71506 memory, 4 parallel threads (CPUs) for 256-bit 
key (requested 2000 ms time)
# Algorithm |   Key |  Encryption |  Decryption
aes-cbc128b31.0 MiB/s33.6 MiB/s
serpent-cbc128b28.1 MiB/s62.9 MiB/s
twofish-cbc128b28.6 MiB/s31.0 MiB/s
aes-cbc256b24.0 MiB/s25.6 MiB/s
serpent-cbc256b28.3 MiB/s62.7 MiB/s
twofish-cbc256b28.6 MiB/s31.0 MiB/s
aes-xts256b32.5 MiB/s33.4 MiB/s
serpent-xts256b50.5 MiB/s60.5 MiB/s
twofish-xts256b25.6 MiB/s30.7 MiB/s
aes-xts512b25.0 MiB/s25.6 MiB/s
serpent-xts512b60.2 MiB/s60.4 MiB/s
twofish-xts512b30.2 MiB/s30.7 MiB/s

> root@nas:~# cryptsetup benchmark
> […]
> # Algorithm |   Key |  Encryption |  Decryption
>     aes-cbc    128b   130.6 MiB/s   128.0 MiB/s
>     serpent-cbc    128b    64.7 MiB/s   161.8 MiB/s
>     twofish-cbc    128b   175.4 MiB/s   218.8 MiB/s
>     aes-cbc    256b   120.1 MiB/s   122.2 MiB/s
>     serpent-cbc    256b    84.5 MiB/s   210.8 MiB/s
>     twofish-cbc    256b   189.5 MiB/s   218.6 MiB/s
>     aes-xts    256b   167.0 MiB/s   162.1 MiB/s
>     serpent-xts    256b   173.9 MiB/s   204.5 MiB/s
>     twofish-xts    256b   204.4 MiB/s   213.2 MiB/s
>     aes-xts    512b   127.9 MiB/s   122.9 MiB/s
>     serpent-xts    512b   201.5 MiB/s   204.7 MiB/s

Re: [gentoo-user] Getting output of a program running in background after a crash

[Mark Knecht]

> I'm planning on my new rig having the Ryzen 5900X.  Is the 5950 better?
While I've kinda picked that one, I'm open to ideas if it is faster and I
can afford it.  As it is, I'm looking at between $300 and $350 for the
5900.  My last CPU cost a little over $100.
>

I'm not going to say one is better than the other. The 5950X has more
cores, the 5900X runs at a higher speed. It depends on your workload which
will be better for you. I do a lot of things based around machine learning
where I felt I was better off having more cores - give 12 to the ML job,
keep 4 for my personal use. It's worked out well. However you don't ever
talk much about what you actually use your computers for other than having
250 disk drives and moving data around your network. Depending on how you
are moving data you might be better off with 5900X going faster.

You can use this site to get some comparative data:

https://cpu.userbenchmark.com/Compare/AMD-Ryzen-9-5950X-vs-AMD-Ryzen-9-5900X/4086vs4087

BTW - you probably know both of these CPUs have been superseded by the
7900X and 7950X. THere's also the 3D versions which have faster and larger
cache.

> While at it.  In the past, I always bought the mobo, CPU and memory from
the same place.  Generally if one of those is bad, it's sometimes hard to
know which one is bad.  Sometimes even the BIOS beep codes are no help
because there may be none.  If the mobo doesn't boot up, worst case, send
all three back to the same place.  Given how far things have come, do I
need to worry about a bad one out of the box anymore?  I can save some
money if I buy from different places.

Cannot answer but you need a return policy from every vendor. If it doesn't
boot and you cannot figure it out you send everything back to multiple
vendors I guess.

Until recently I built all my machines myself. My 5900X machine has water
cooling and I had cash so I paid a local storefront here to build it. I
bought right in the middle of the pandemic and the chip shortage cost me
huge dollars. Most expensive machine I've ever owned. Probably could build
it today for less than 50% of what I paid.

Re: [gentoo-user] Getting output of a program running in background after a crash

[Dale]

Mark Knecht wrote:
>
>
> On Fri, Oct 13, 2023 at 10:02 AM Dale  > wrote:
> >
> > Michael wrote:
> >
> > On Friday, 13 October 2023 02:35:21 BST Dale wrote:
> >
> > root@fireball / # cryptsetup benchmark
> > # Tests are approximate using memory only (no storage IO).
> > PBKDF2-sha1       878204 iterations per second for 256-bit key
> > PBKDF2-sha256     911805 iterations per second for 256-bit key
> > PBKDF2-sha512     698119 iterations per second for 256-bit key
> > PBKDF2-ripemd160  548418 iterations per second for 256-bit key
> > PBKDF2-whirlpool  299251 iterations per second for 256-bit key
> > argon2i       4 iterations, 1048576 memory, 4 parallel threads (CPUs)
> > for 256-bit key (requested 2000 ms time)
> > argon2id      4 iterations, 1048576 memory, 4 parallel threads (CPUs)
> > for 256-bit key (requested 2000 ms time)
> > #     Algorithm |       Key |      Encryption |      Decryption
> >         aes-cbc        128b        63.8 MiB/s        51.4 MiB/s
> >     serpent-cbc        128b        90.9 MiB/s       307.6 MiB/s
> >     twofish-cbc        128b       200.4 MiB/s       218.4 MiB/s
> >         aes-cbc        256b        54.6 MiB/s        37.5 MiB/s
> >     serpent-cbc        256b        90.4 MiB/s       302.6 MiB/s
> >     twofish-cbc        256b       198.2 MiB/s       216.7 MiB/s
> >         aes-xts        256b        68.0 MiB/s        45.0 MiB/s
> >     serpent-xts        256b       231.9 MiB/s       227.6 MiB/s
> >     twofish-xts        256b       191.8 MiB/s       163.1 MiB/s
> >         aes-xts        512b        42.4 MiB/s        18.9 MiB/s
> >     serpent-xts        512b       100.9 MiB/s       124.6 MiB/s
> >     twofish-xts        512b       154.8 MiB/s       173.3 MiB/s
> > root@fireball / #
> >
> >
> >
> > root@nas:~# cryptsetup benchmark
> > # Tests are approximate using memory only (no storage IO).
> > PBKDF2-sha1       741567 iterations per second for 256-bit key
> > PBKDF2-sha256     910222 iterations per second for 256-bit key
> > PBKDF2-sha512     781353 iterations per second for 256-bit key
> > PBKDF2-ripemd160  547845 iterations per second for 256-bit key
> > PBKDF2-whirlpool  350929 iterations per second for 256-bit key
> > argon2i       4 iterations, 571787 memory, 4 parallel threads (CPUs) for
> > 256-bit key (requested 2000 ms time)
> > argon2id      4 iterations, 524288 memory, 4 parallel threads (CPUs) for
> > 256-bit key (requested 2000 ms time)
> > #     Algorithm |       Key |      Encryption |      Decryption
> >         aes-cbc        128b       130.6 MiB/s       128.0 MiB/s
> >     serpent-cbc        128b        64.7 MiB/s       161.8 MiB/s
> >     twofish-cbc        128b       175.4 MiB/s       218.8 MiB/s
> >         aes-cbc        256b       120.1 MiB/s       122.2 MiB/s
> >     serpent-cbc        256b        84.5 MiB/s       210.8 MiB/s
> >     twofish-cbc        256b       189.5 MiB/s       218.6 MiB/s
> >         aes-xts        256b       167.0 MiB/s       162.1 MiB/s
> >     serpent-xts        256b       173.9 MiB/s       204.5 MiB/s
> >     twofish-xts        256b       204.4 MiB/s       213.2 MiB/s
> >         aes-xts        512b       127.9 MiB/s       122.9 MiB/s
> >     serpent-xts        512b       201.5 MiB/s       204.7 MiB/s
> >     twofish-xts        512b       215.0 MiB/s       213.0 MiB/s
> > root@nas:~#
> >
> >
> >
> > Is that about what you would expect?  Fireball is on a 970 mobo.  It's
> > slightly newer.  I think the 770T is about 2 years older, maybe 3.
> >
>
> THis was just for kicks because I think somewhere, this thread or some
> other I think you mentioned a Ryzen 5900 and mine is a 5950, now about
> 18 months old:
>
> mark@science2:~$ cryptsetup benchmark
> # Tests are approximate using memory only (no storage IO).
> PBKDF2-sha1      2212185 iterations per second for 256-bit key
> PBKDF2-sha256    4161015 iterations per second for 256-bit key
> PBKDF2-sha512    1798586 iterations per second for 256-bit key
> PBKDF2-ripemd160  841553 iterations per second for 256-bit key
> PBKDF2-whirlpool  675628 iterations per second for 256-bit key
> argon2i      11 iterations, 1048576 memory, 4 parallel threads (CPUs)
> for 256-bit key (requested 2000
> ms time)
> argon2id     11 iterations, 1048576 memory, 4 parallel threads (CPUs)
> for 256-bit key (requested 2000
> ms time)
> #     Algorithm |       Key |      Encryption |      Decryption
>        aes-cbc        128b      1181.2 MiB/s      5132.1 MiB/s
>    serpent-cbc        128b       107.8 MiB/s       426.1 MiB/s
>    twofish-cbc        128b       221.1 MiB/s       418.1 MiB/s
>        aes-cbc        256b       890.1 MiB/s      4167.7 MiB/s
>    serpent-cbc        256b       116.0 MiB/s       428.3 MiB/s
>    twofish-cbc        256b       224.2 MiB/s       417.7 MiB/s
>        aes-xts        256b      4121.7 MiB/s      4115.7 MiB/s
>    serpent-xts        256b       385.9 MiB/s       401.6 MiB/s
>    twofish-xts        256b       394.5 MiB/s       405.0 MiB/s
> 

Re: [gentoo-user] Getting output of a program running in background after a crash

[Mark Knecht]

On Fri, Oct 13, 2023 at 10:02 AM Dale  wrote:
>
> Michael wrote:
>
> On Friday, 13 October 2023 02:35:21 BST Dale wrote:
>
> root@fireball / # cryptsetup benchmark
> # Tests are approximate using memory only (no storage IO).
> PBKDF2-sha1   878204 iterations per second for 256-bit key
> PBKDF2-sha256 911805 iterations per second for 256-bit key
> PBKDF2-sha512 698119 iterations per second for 256-bit key
> PBKDF2-ripemd160  548418 iterations per second for 256-bit key
> PBKDF2-whirlpool  299251 iterations per second for 256-bit key
> argon2i   4 iterations, 1048576 memory, 4 parallel threads (CPUs)
> for 256-bit key (requested 2000 ms time)
> argon2id  4 iterations, 1048576 memory, 4 parallel threads (CPUs)
> for 256-bit key (requested 2000 ms time)
> # Algorithm |   Key |  Encryption |  Decryption
> aes-cbc128b63.8 MiB/s51.4 MiB/s
> serpent-cbc128b90.9 MiB/s   307.6 MiB/s
> twofish-cbc128b   200.4 MiB/s   218.4 MiB/s
> aes-cbc256b54.6 MiB/s37.5 MiB/s
> serpent-cbc256b90.4 MiB/s   302.6 MiB/s
> twofish-cbc256b   198.2 MiB/s   216.7 MiB/s
> aes-xts256b68.0 MiB/s45.0 MiB/s
> serpent-xts256b   231.9 MiB/s   227.6 MiB/s
> twofish-xts256b   191.8 MiB/s   163.1 MiB/s
> aes-xts512b42.4 MiB/s18.9 MiB/s
> serpent-xts512b   100.9 MiB/s   124.6 MiB/s
> twofish-xts512b   154.8 MiB/s   173.3 MiB/s
> root@fireball / #
>
>
>
> root@nas:~# cryptsetup benchmark
> # Tests are approximate using memory only (no storage IO).
> PBKDF2-sha1   741567 iterations per second for 256-bit key
> PBKDF2-sha256 910222 iterations per second for 256-bit key
> PBKDF2-sha512 781353 iterations per second for 256-bit key
> PBKDF2-ripemd160  547845 iterations per second for 256-bit key
> PBKDF2-whirlpool  350929 iterations per second for 256-bit key
> argon2i   4 iterations, 571787 memory, 4 parallel threads (CPUs) for
> 256-bit key (requested 2000 ms time)
> argon2id  4 iterations, 524288 memory, 4 parallel threads (CPUs) for
> 256-bit key (requested 2000 ms time)
> # Algorithm |   Key |  Encryption |  Decryption
> aes-cbc128b   130.6 MiB/s   128.0 MiB/s
> serpent-cbc128b64.7 MiB/s   161.8 MiB/s
> twofish-cbc128b   175.4 MiB/s   218.8 MiB/s
> aes-cbc256b   120.1 MiB/s   122.2 MiB/s
> serpent-cbc256b84.5 MiB/s   210.8 MiB/s
> twofish-cbc256b   189.5 MiB/s   218.6 MiB/s
> aes-xts256b   167.0 MiB/s   162.1 MiB/s
> serpent-xts256b   173.9 MiB/s   204.5 MiB/s
> twofish-xts256b   204.4 MiB/s   213.2 MiB/s
> aes-xts512b   127.9 MiB/s   122.9 MiB/s
> serpent-xts512b   201.5 MiB/s   204.7 MiB/s
> twofish-xts512b   215.0 MiB/s   213.0 MiB/s
> root@nas:~#
>
>
>
> Is that about what you would expect?  Fireball is on a 970 mobo.  It's
> slightly newer.  I think the 770T is about 2 years older, maybe 3.
>

THis was just for kicks because I think somewhere, this thread or some
other I think you mentioned a Ryzen 5900 and mine is a 5950, now about
18 months old:

mark@science2:~$ cryptsetup benchmark
# Tests are approximate using memory only (no storage IO).
PBKDF2-sha1  2212185 iterations per second for 256-bit key
PBKDF2-sha2564161015 iterations per second for 256-bit key
PBKDF2-sha5121798586 iterations per second for 256-bit key
PBKDF2-ripemd160  841553 iterations per second for 256-bit key
PBKDF2-whirlpool  675628 iterations per second for 256-bit key
argon2i  11 iterations, 1048576 memory, 4 parallel threads (CPUs) for
256-bit key (requested 2000
ms time)
argon2id 11 iterations, 1048576 memory, 4 parallel threads (CPUs) for
256-bit key (requested 2000
ms time)
# Algorithm |   Key |  Encryption |  Decryption
   aes-cbc128b  1181.2 MiB/s  5132.1 MiB/s
   serpent-cbc128b   107.8 MiB/s   426.1 MiB/s
   twofish-cbc128b   221.1 MiB/s   418.1 MiB/s
   aes-cbc256b   890.1 MiB/s  4167.7 MiB/s
   serpent-cbc256b   116.0 MiB/s   428.3 MiB/s
   twofish-cbc256b   224.2 MiB/s   417.7 MiB/s
   aes-xts256b  4121.7 MiB/s  4115.7 MiB/s
   serpent-xts256b   385.9 MiB/s   401.6 MiB/s
   twofish-xts256b   394.5 MiB/s   405.0 MiB/s
   aes-xts512b  3480.2 MiB/s  3486.3 MiB/s
   serpent-xts512b   408.9 MiB/s   401.4 MiB/s
   twofish-xts512b   395.9 MiB/s   404.8 MiB/s
mark@science2:~$

Re: [gentoo-user] Getting output of a program running in background after a crash

[Dale]

Michael wrote:
> On Friday, 13 October 2023 02:35:21 BST Dale wrote:
>
>> root@fireball / # cryptsetup benchmark
>> # Tests are approximate using memory only (no storage IO).
>> PBKDF2-sha1   878204 iterations per second for 256-bit key
>> PBKDF2-sha256 911805 iterations per second for 256-bit key
>> PBKDF2-sha512 698119 iterations per second for 256-bit key
>> PBKDF2-ripemd160  548418 iterations per second for 256-bit key
>> PBKDF2-whirlpool  299251 iterations per second for 256-bit key
>> argon2i   4 iterations, 1048576 memory, 4 parallel threads (CPUs)
>> for 256-bit key (requested 2000 ms time)
>> argon2id  4 iterations, 1048576 memory, 4 parallel threads (CPUs)
>> for 256-bit key (requested 2000 ms time)
>> # Algorithm |   Key |  Encryption |  Decryption
>> aes-cbc128b63.8 MiB/s51.4 MiB/s
>> serpent-cbc128b90.9 MiB/s   307.6 MiB/s
>> twofish-cbc128b   200.4 MiB/s   218.4 MiB/s
>> aes-cbc256b54.6 MiB/s37.5 MiB/s
>> serpent-cbc256b90.4 MiB/s   302.6 MiB/s
>> twofish-cbc256b   198.2 MiB/s   216.7 MiB/s
>> aes-xts256b68.0 MiB/s45.0 MiB/s
>> serpent-xts256b   231.9 MiB/s   227.6 MiB/s
>> twofish-xts256b   191.8 MiB/s   163.1 MiB/s
>> aes-xts512b42.4 MiB/s18.9 MiB/s
>> serpent-xts512b   100.9 MiB/s   124.6 MiB/s
>> twofish-xts512b   154.8 MiB/s   173.3 MiB/s
>> root@fireball / #
>>
>>
>>
>> root@nas:~# cryptsetup benchmark
>> # Tests are approximate using memory only (no storage IO).
>> PBKDF2-sha1   741567 iterations per second for 256-bit key
>> PBKDF2-sha256 910222 iterations per second for 256-bit key
>> PBKDF2-sha512 781353 iterations per second for 256-bit key
>> PBKDF2-ripemd160  547845 iterations per second for 256-bit key
>> PBKDF2-whirlpool  350929 iterations per second for 256-bit key
>> argon2i   4 iterations, 571787 memory, 4 parallel threads (CPUs) for
>> 256-bit key (requested 2000 ms time)
>> argon2id  4 iterations, 524288 memory, 4 parallel threads (CPUs) for
>> 256-bit key (requested 2000 ms time)
>> # Algorithm |   Key |  Encryption |  Decryption
>> aes-cbc128b   130.6 MiB/s   128.0 MiB/s
>> serpent-cbc128b64.7 MiB/s   161.8 MiB/s
>> twofish-cbc128b   175.4 MiB/s   218.8 MiB/s
>> aes-cbc256b   120.1 MiB/s   122.2 MiB/s
>> serpent-cbc256b84.5 MiB/s   210.8 MiB/s
>> twofish-cbc256b   189.5 MiB/s   218.6 MiB/s
>> aes-xts256b   167.0 MiB/s   162.1 MiB/s
>> serpent-xts256b   173.9 MiB/s   204.5 MiB/s
>> twofish-xts256b   204.4 MiB/s   213.2 MiB/s
>> aes-xts512b   127.9 MiB/s   122.9 MiB/s
>> serpent-xts512b   201.5 MiB/s   204.7 MiB/s
>> twofish-xts512b   215.0 MiB/s   213.0 MiB/s
>> root@nas:~#
>>
>>
>>
>> Is that about what you would expect?  Fireball is on a 970 mobo.  It's
>> slightly newer.  I think the 770T is about 2 years older, maybe 3. 
> grep AES /usr/src/linux/.config
>
> or,
>
> zgrep AES /proc/config.gz
>
> Or, grep your *current* kernel config wherever it is stored.


I got the idea but assuming you wanted that info from the NAS box, I had
to dig a little.  It's Ubuntu.  It doesn't have kernel sources, no
config.gz in /proc either.  I found this.  I assume it is accurate. 
Hopefully. 


root@nas:~# cat /boot/config-5.15.0-86-generic | grep -i aes
CONFIG_SND_MAESTRO3=m
CONFIG_SND_MAESTRO3_INPUT=y
CONFIG_CRYPTO_AEGIS128_AESNI_SSE2=m
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_TI=m
CONFIG_CRYPTO_AES_NI_INTEL=m
CONFIG_CRYPTO_CAMELLIA_AESNI_AVX_X86_64=m
CONFIG_CRYPTO_CAMELLIA_AESNI_AVX2_X86_64=m
CONFIG_CRYPTO_SM4_AESNI_AVX_X86_64=m
CONFIG_CRYPTO_SM4_AESNI_AVX2_X86_64=m
CONFIG_CRYPTO_DEV_PADLOCK_AES=m
CONFIG_CRYPTO_LIB_AES=y
root@nas:~#


I don't usually use modules.  So, this is not something I run into
much.  I'm adding this info since I think it will help as well. 


root@nas:~# lsmod | grep -i aes
root@nas:~#


I see the main aes option is built in so it shouldn't be listed above if
I recall correctly.  The other two options are modules but not loaded. 
That said, I don't know if they are needed either.  On my main rig, I
have AES_TI built in.  Anyway, I thought I would include that in case it
helps. 

I was thinking about later on upgrading the CPU to a 6 core version.  I
may research and see if it includes the aes instruction set.  It may
help.  It may not.  Right now, I don't know if the 770T is even going to
be a NAS box and need encryption. 

It could be that given that mobo and CPUs age, it's doing the best it
can.  After all, the Dell box was also fairly 

[gentoo-user] Re: Video card. Will this work for me?

[Grant Edwards]

On 2023-10-13, Dale  wrote:

> As most likely know, I'm in the process of building a new rig and
> putting a couple older systems to use.  Most of my mobos support
> PCIe-x16 2.0 for video cards.  I found a Nvidia NVS 510 that has four
> mini HDMI outputs.  Research claims those are for multiple monitors, in
> other words not cloned.  I can use mini HDMI to regular HDMI adapters
> easy enough.  I found a website that lists Nvidia cards and I think this
> will suite my needs rather well.  I currently have a GeForce GTX 650 and
> it works just fine but it is older.  While this 510 isn't a spring
> chicken by any means, it seems to be a little younger.  On my newer rig,
> it will likely be PCI 3.0.  Will this card work in it as well?  In other
> words, are they backward compatible?  I think I've read that mobos are
> but want to be sure.

Yes, PCIe cards are supposed to be backwards compatible with older
PCIe implementations on motherboards and vice-versa.

Be warned: I went through a couple generations of NVS-3xx cards. I had
to recycle both of them because NVidea driver support stopped long
before I had any real reason to replace either of the boards. [I could
never get the open-source driver to work.]  After being forced to
replace a second perfectly servicable NVidia card, I swore never to by
NVidia again.

--
Grant

[gentoo-user] Video card. Will this work for me?

[Dale]

Howdy,

As most likely know, I'm in the process of building a new rig and
putting a couple older systems to use.  Most of my mobos support
PCIe-x16 2.0 for video cards.  I found a Nvidia NVS 510 that has four
mini HDMI outputs.  Research claims those are for multiple monitors, in
other words not cloned.  I can use mini HDMI to regular HDMI adapters
easy enough.  I found a website that lists Nvidia cards and I think this
will suite my needs rather well.  I currently have a GeForce GTX 650 and
it works just fine but it is older.  While this 510 isn't a spring
chicken by any means, it seems to be a little younger.  On my newer rig,
it will likely be PCI 3.0.  Will this card work in it as well?  In other
words, are they backward compatible?  I think I've read that mobos are
but want to be sure. 

My plan, one output for my monitor and then have either one or two
outputs that are identical for my TV, I have one TV in bedroom and one
in living room.  Same picture on both TVs and audio is sent through the
HDMI cable.  I currently use one card output for TV and run it through a
splitter.  I don't think that is anything complicated and I'm pretty
sure that card will support that easily.  It never hurts to be sure. 

Does anyone know of anything that would make it not work for my needs? 
I plan to buy 3 cards; one maybe for new build, one or two as a backup
in case one fails.  Just want to be sure before I dive in. 

Dale

:-)  :-) 

Re: [gentoo-user] Getting output of a program running in background after a crash

[Michael]

On Friday, 13 October 2023 02:35:21 BST Dale wrote:

> root@fireball / # cryptsetup benchmark
> # Tests are approximate using memory only (no storage IO).
> PBKDF2-sha1   878204 iterations per second for 256-bit key
> PBKDF2-sha256 911805 iterations per second for 256-bit key
> PBKDF2-sha512 698119 iterations per second for 256-bit key
> PBKDF2-ripemd160  548418 iterations per second for 256-bit key
> PBKDF2-whirlpool  299251 iterations per second for 256-bit key
> argon2i   4 iterations, 1048576 memory, 4 parallel threads (CPUs)
> for 256-bit key (requested 2000 ms time)
> argon2id  4 iterations, 1048576 memory, 4 parallel threads (CPUs)
> for 256-bit key (requested 2000 ms time)
> # Algorithm |   Key |  Encryption |  Decryption
> aes-cbc128b63.8 MiB/s51.4 MiB/s
> serpent-cbc128b90.9 MiB/s   307.6 MiB/s
> twofish-cbc128b   200.4 MiB/s   218.4 MiB/s
> aes-cbc256b54.6 MiB/s37.5 MiB/s
> serpent-cbc256b90.4 MiB/s   302.6 MiB/s
> twofish-cbc256b   198.2 MiB/s   216.7 MiB/s
> aes-xts256b68.0 MiB/s45.0 MiB/s
> serpent-xts256b   231.9 MiB/s   227.6 MiB/s
> twofish-xts256b   191.8 MiB/s   163.1 MiB/s
> aes-xts512b42.4 MiB/s18.9 MiB/s
> serpent-xts512b   100.9 MiB/s   124.6 MiB/s
> twofish-xts512b   154.8 MiB/s   173.3 MiB/s
> root@fireball / #
> 
> 
> 
> root@nas:~# cryptsetup benchmark
> # Tests are approximate using memory only (no storage IO).
> PBKDF2-sha1   741567 iterations per second for 256-bit key
> PBKDF2-sha256 910222 iterations per second for 256-bit key
> PBKDF2-sha512 781353 iterations per second for 256-bit key
> PBKDF2-ripemd160  547845 iterations per second for 256-bit key
> PBKDF2-whirlpool  350929 iterations per second for 256-bit key
> argon2i   4 iterations, 571787 memory, 4 parallel threads (CPUs) for
> 256-bit key (requested 2000 ms time)
> argon2id  4 iterations, 524288 memory, 4 parallel threads (CPUs) for
> 256-bit key (requested 2000 ms time)
> # Algorithm |   Key |  Encryption |  Decryption
> aes-cbc128b   130.6 MiB/s   128.0 MiB/s
> serpent-cbc128b64.7 MiB/s   161.8 MiB/s
> twofish-cbc128b   175.4 MiB/s   218.8 MiB/s
> aes-cbc256b   120.1 MiB/s   122.2 MiB/s
> serpent-cbc256b84.5 MiB/s   210.8 MiB/s
> twofish-cbc256b   189.5 MiB/s   218.6 MiB/s
> aes-xts256b   167.0 MiB/s   162.1 MiB/s
> serpent-xts256b   173.9 MiB/s   204.5 MiB/s
> twofish-xts256b   204.4 MiB/s   213.2 MiB/s
> aes-xts512b   127.9 MiB/s   122.9 MiB/s
> serpent-xts512b   201.5 MiB/s   204.7 MiB/s
> twofish-xts512b   215.0 MiB/s   213.0 MiB/s
> root@nas:~#
> 
> 
> 
> Is that about what you would expect?  Fireball is on a 970 mobo.  It's
> slightly newer.  I think the 770T is about 2 years older, maybe 3. 

grep AES /usr/src/linux/.config

or,

zgrep AES /proc/config.gz

Or, grep your *current* kernel config wherever it is stored.

signature.asc
Description: This is a digitally signed message part.