[GH-ISSUE #836] Option to Set Password is Absent #564

New issue

Closed

opened 2026-02-27 15:50:54 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 15:50:54 +03:00

Owner

Originally created by @JacobF-dev on GitHub (Jun 18, 2020).
Original GitHub issue: https://github.com/quasar/Quasar/issues/836

Describe the bug
The option to set a connection password is no longer present in version 1.4.0, although is was present in version 1.3.0.0.

To Reproduce
Steps to reproduce the behavior:

Open 'Quasar.exe'
Click on 'Settings'
Look for a 'Password' box.
The option is nonexistent.
Try the same steps on version 1.3.0.0

System

Server OS: Windows 10
Server installed .NET Framework version: Latest
Quasar Version: 1.4.0

Is the password set somewhere else, or is it completely removed?

Originally created by @JacobF-dev on GitHub (Jun 18, 2020). Original GitHub issue: https://github.com/quasar/Quasar/issues/836 **Describe the bug** The option to set a connection password is no longer present in version 1.4.0, although is was present in version 1.3.0.0. **To Reproduce** Steps to reproduce the behavior: 1. Open 'Quasar.exe' 2. Click on 'Settings' 3. Look for a 'Password' box. 4. The option is nonexistent. 5. Try the same steps on version 1.3.0.0 **System** - Server OS: Windows 10 - Server installed .NET Framework version: Latest - Quasar Version: 1.4.0 Is the password set somewhere else, or is it completely removed?

kerem

2026-02-27 15:50:54 +03:00

closed this issue
added the
invalid
label

kerem commented

2026-02-27 15:50:55 +03:00

Author

Owner

@MaxXor commented on GitHub (Jun 18, 2020):

Hey, it is no longer necessary due to the new way the client and server authenticate each other using X.509 certificates. The only thing you need to store safely now is the server certificate, called quasar.p12.

@MaxXor commented on GitHub (Jun 18, 2020): Hey, it is no longer necessary due to the new way the client and server authenticate each other using X.509 certificates. The only thing you need to store safely now is the server certificate, called `quasar.p12`.

kerem commented

2026-02-27 15:50:55 +03:00

Author

Owner

@JacobF-dev commented on GitHub (Jun 18, 2020):

Okay, just confirming, the connection is still encrypted, but the password is stored in the quasar.p12 file. Right?

@JacobF-dev commented on GitHub (Jun 18, 2020): Okay, just confirming, the connection is still encrypted, but the password is stored in the quasar.p12 file. Right?

kerem commented

2026-02-27 15:50:55 +03:00

Author

Owner

@MaxXor commented on GitHub (Jun 18, 2020):

Yes the connection is still encrypted (stronger than before btw). There is no password in the quasar.p12 file, but a server certificate including a cryptographic key pair which is more secure than a password.

@MaxXor commented on GitHub (Jun 18, 2020): Yes the connection is still encrypted (stronger than before btw). There is no password in the `quasar.p12` file, but a server certificate including a cryptographic key pair which is more secure than a password.

kerem commented

2026-02-27 15:50:55 +03:00

Author

Owner

@JacobF-dev commented on GitHub (Jun 18, 2020):

OK! Thank you for your help and commitment!

@JacobF-dev commented on GitHub (Jun 18, 2020): OK! Thank you for your help and commitment!