Project

General

Profile

Bug #1715

Quassel Core does not read quasselCert.pem if it's a symlink

Added by counterpillow over 3 years ago. Updated about 3 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
Quassel Core
Target version:
-
Start date:
05/12/2021
Due date:
% Done:

0%

Estimated time:
Version:
0.13.0
OS:
Linux

Description

I've tried symlinking quasselCert.pem it to my letsencrypt "fullchain.pem" certificate (which in of itself is a symlink), but quassel refuses to read a quasselCert.pem that is a symlink. It does have the necessary read permissions on the file it ultimately points to.

History

#1 Updated by phuzion over 3 years ago

  • Status changed from New to Feedback

Hi there,

I've tested this, and I am unable to reproduce the issue on Fedora 34, built from source.

I've even locally added a small patch to confirm when the core is seeing a symlink, which prints a message to the console when QFileInfo sees that the file is a symlink.

I generated a self-signed certificate, placed it in ~/temp as example.pem, and did ln -s example.pem quasselCert.pem to create a symlink to the file. Launching Quasselcore with the --configdir=/home/phuzion/temp argument, I get my warning message that the file in question is a symlink, and I am able to configure the core as expected. The cert I generated is presented in the UI.

As an extra step, I even tried doing example.pem -> quasselCert2.pem -> quasselCert.pem (two simlinks). It worked fine as well.

Are you absolutely positive that the file permissions are correct on your file? Is it a full .pem file with the correct information inside?

Also available in: Atom PDF