Hi,
On 10/5/19 2:17 AM, Roland Hughes wrote:
_ALL_ electronic encryption is security by obscurity.
Take a moment and let that sink in because it is fact.
Okay, out with it! What secret service are you working for and why are
you trying to sell everybody on bullshit that weakens our
Il 07/10/19 07:55, Uwe Rathmann ha scritto:
Ah yes, sorry.
My response was initially more explicit about FUD, before I decided,
that it is not worth the effort.
Huh? It was not my intention to spread FUD. I'm not telling anyone "buy
a license, you never know..." or "stick to LGPL, don't
On 10/7/19 5:00 AM, Konrad Rosenbaum wrote:
Hi,
On 10/5/19 2:17 AM, Roland Hughes wrote:
_ALL_ electronic encryption is security by obscurity.
Take a moment and let that sink in because it is fact.
Okay, out with it! What secret service are you working for and why are
you trying to sell
My hardware was new enough I could install 390. Others will most likely
not be as lucky. I was just sending up a flare making he assumption KDE
developer will try to kick this up the chain. Once I found a work around
I didn't care enough to diff the 340 and 390 APIs. 340 has been around a
very
On Sat, Oct 5, 2019 at 11:22 PM Roland Hughes
wrote:
>
> Just in case this is deeper than the ksplashqml.
>
> https://bugs.kde.org/show_bug.cgi?id=408904
>
> Don't know if it is specific to KDE or deeper within Qt. Appears to
> happen with nvidia-340 driver but doesn't happen with
On 10/7/19 5:00 AM, Thiago Macieira wrote:
You do realise that's not how modern encryption works, right? You do
realise
that SSL/TLS rekeys periodically to avoid even a compromised key from going
further? That's what the "data limit for all ciphersuits" means: rekey after a
while.
yeah.
Yes, I also know about the lizardmen from Phobos who can crack SSL/TLS
keys instantly.
If you can show some code all this would be much more credible. After
all, this is a Qt mailing list, not a science fiction one.
Rgrds Henry
On 2019-10-07 16:06, Roland Hughes wrote:
On 10/7/19 5:00 AM,
Thanks Giuseppe, Jerome, and Uwe. All of this makes sense to me. I will have to
talk to our software and management people and decide what our best route is.
Incidentally, we will also need FDA certification for this product. This is all
a bit preliminary. The product is still in development.
On segunda-feira, 7 de outubro de 2019 05:31:17 PDT Roland Hughes wrote:
> Screaming about the size of the forest one will hide there tree in
> doesn't change the security by obscurity aspect of it. Thumping the desk
> and claiming a forest which is 2^128 * 2^key-bit-width doesn't mean you
>
07.10.2019, 18:00, "Roland Hughes" :
> My hardware was new enough I could install 390. Others will most likely
> not be as lucky.
It may be a good reason to replace their 9 years old GPU to something
up-to-date.
--
Regards,
Konstantin
___
I'm reading up about the state machine stuff and was wondering how I would go
about having X tests with the same Y steps. Unlike parallel states, these are
still sequential:
State / SubState
TEST_1 / PREPARE
TEST_1 / PREPARE_COMPLETE
TEST_1 / EXECUTE
TEST_1 / EXECUTE_COMPLETE
TEST_1 / RESULT
Note that there is (or was?) a restriction in the commercial license.
You are not allowed to use commercial Qt if you previously uses open
source Qt in the project. So you might not even be allowed to switch
from open source to commercial.
Not sure if that (very) weird term has been removed
On 04/10/2019 20.17, Roland Hughes wrote:
> On 10/3/19 5:00 AM, Matthew Woehlke wrote:
>> On 01/10/2019 20.47, Roland Hughes wrote:
>>> To really secure transmitted data, you cannot use an open standard which
>>> has readily identifiable fields. Companies needing great security are
>>> moving to
From the haze of the smoke. And the mescaline. - The Airborne Toxic
Event "Wishing Well"
On 10/7/19 3:46 PM, Matthew Woehlke wrote:
On 04/10/2019 20.17, Roland Hughes wrote:
Even if all of that stuff has been fixed, you have to be absolutely
certain the encryption method you choose doesn't
A lot of people don't have any money. They use a corporate or relative's
cast-off. Still others, like the older computers I have on the workbench
behind me, have been re-purposed to run BOINC. They won't be upgraded.
If a drive dies and I have a spare laying around I'll put that in and
re-load
On segunda-feira, 7 de outubro de 2019 07:06:07 PDT Roland Hughes wrote:
> We now
> have the storage and computing power available to create the database or
> 2^128 database tables if needed.
Do you know how ludicrous this statement is?
Let's say you had 128 bits for each of the 2^128 entries,
On 10/7/19 6:21 PM, Thiago Macieira wrote:
On segunda-feira, 7 de outubro de 2019 07:06:07 PDT Roland Hughes wrote:
We now
have the storage and computing power available to create the database or
2^128 database tables if needed.
Do you know how ludicrous this statement is?
Let's say you had
On Monday, 7 October 2019 15:43:21 PDT Roland Hughes wrote:
> No. This technique is cracking without cracking. You are looking for a
> fingerprint. That fingerprint is the opening string for an xml document
> which must be there per the standard. For JSON it is the quote and colon
> stuff
On 10/7/19 6:21 PM, Thiago Macieira wrote:
On segunda-feira, 7 de outubro de 2019 05:31:17 PDT Roland Hughes wrote:
Let us not forget we are at the end of the x86 era when it comes to what
evil-doers will use to generate a fingerprint database, or brute force
crack.
Nikos,
Actually that is incorrect. You can use commercial if you previously used Open
Source but it’s on a case by case basis and you need to get approval from the
Qt company.
Sent from my iPhone
Regards,
Melinda Seifert
Director of the Americas
melinda.seif...@qt.io
(O) 617-377-7918
(C)
Be a lot easier to do if people would quit badgering me trying to tell
me the Easter Bunny is real, Tinkerbell told them.
The drive arrives tomorrow I think. If I'm not interrupted too often I
can start writing code for the various pieces. When I get it all done
"some" of it will be on the
21 matches
Mail list logo
