Re: [Interest] Behavioural change in QFile/QDir rename

2019-06-16 Thread Elvis Stansvik
Den mån 17 juni 2019 07:47Elvis Stansvik skrev: > Den mån 17 juni 2019 kl 01:29 skrev Federico Buti : > > > > Hi Thiago. > > > > Thanks for the feedback. > > I'm on Fedora 29 so definitely not on an old kernel as that. My > colleague is on Ubuntu but I'm pretty sure it is a 16.xx release. I guess

Re: [Interest] Behavioural change in QFile/QDir rename

2019-06-16 Thread Elvis Stansvik
Den mån 17 juni 2019 kl 07:47 skrev Elvis Stansvik : > > Den mån 17 juni 2019 kl 01:29 skrev Federico Buti : > > > > Hi Thiago. > > > > Thanks for the feedback. > > I'm on Fedora 29 so definitely not on an old kernel as that. My colleague > > is on Ubuntu but I'm pretty sure it is a 16.xx release.

Re: [Interest] Behavioural change in QFile/QDir rename

2019-06-16 Thread Elvis Stansvik
Den mån 17 juni 2019 kl 01:29 skrev Federico Buti : > > Hi Thiago. > > Thanks for the feedback. > I'm on Fedora 29 so definitely not on an old kernel as that. My colleague is > on Ubuntu but I'm pretty sure it is a 16.xx release. I guess the usage of > renameat2() is failing for some other reason

Re: [Interest] Question Regarding Porting Gtk To PyQt

2019-06-16 Thread Christoph Feck
On 06/17/19 03:57, Christoph Feck wrote: * https://doc.qt.io/qtforpython/PySide2 * https://doc.qt.io/qtforpython/ ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest

Re: [Interest] Question Regarding Porting Gtk To PyQt

2019-06-16 Thread Christoph Feck
On 06/17/19 03:29, Samuel Banya wrote: Hello everyone, I'm having a bit of difficulty of helping the Lubuntu team port a program called RedShift from Gtk to PyQT. The reason is that the Qt docs are primarily C++ based, and though I know there is a PyQt variant that focuses on Python, its not as

[Interest] Question Regarding Porting Gtk To PyQt

2019-06-16 Thread Samuel Banya
Hello everyone, I'm having a bit of difficulty of helping the Lubuntu team port a program called RedShift from Gtk to PyQT. The reason is that the Qt docs are primarily C++ based, and though I know there is a PyQt variant that focuses on Python, its not as up to date as the ones present for the C

Re: [Interest] Behavioural change in QFile/QDir rename

2019-06-16 Thread Thiago Macieira
On Sunday, 16 June 2019 15:20:28 PDT Federico Buti wrote: > Hi Thiago. > > Thanks for the feedback. > I'm on Fedora 29 so definitely not on an old kernel as that. My colleague > is on Ubuntu but I'm pretty sure it is a 16.xx release. I guess the usage > of renameat2() is failing for some other rea

Re: [Interest] Behavioural change in QFile/QDir rename

2019-06-16 Thread Federico Buti
Hi Thiago. Thanks for the feedback. I'm on Fedora 29 so definitely not on an old kernel as that. My colleague is on Ubuntu but I'm pretty sure it is a 16.xx release. I guess the usage of renameat2() is failing for some other reason. What could that be? Any idea? Just in case, here is the code of

Re: [Interest] Clarification on network security

2019-06-16 Thread Bob Hood
Let me thank everybody for responding, and providing such helpful insights.  Some--like creating Private CA, as Steve pointed out--I wasn't even aware was possible. I certainly have much to consider before beginning this next project. As for what I'm securing, it's certainly not bitcoin transfe

Re: [Interest] Clarification on network security

2019-06-16 Thread Giuseppe D'Angelo via Interest
On 16/06/2019 13:41, Konrad Rosenbaum wrote: Bob, you already have really good answers from Elvis and Thiago - please ignore this thread! In short: use QSslSocket/QSslServer, set the protocol version to 1.2 or newer, deliver the server cert (not key) with your client software, authentication depe

Re: [Interest] Clarification on network security

2019-06-16 Thread Konrad Rosenbaum
Hi, [Congrats Roland: successful flame bait accomplished!] Bob, you already have really good answers from Elvis and Thiago - please ignore this thread! In short: use QSslSocket/QSslServer, set the protocol version to 1.2 or newer, deliver the server cert (not key) with your client software,