I have done this, according to http://www.tc.umn.edu/~brams006/selfsign.html, part 1B (generating your own CA):
a) create a CA authority (ca.key and ca.crt)
b) make a certificate request (server.csr)
c) sign the certificate request (server.crt and server.key) with the new CA authority
d) change the server key so it does not ask for a passphrase.
Afterwards, the server.crt and server.key files are included in /usr/share/fred-client/ssl directory, and the fred-client configuration file is modified like this:
ssl_cert = %(dir)s/server.crt
ssl_key = %(dir)s/server.key
Now, if I try to run fred-client this is the result:
ERROR: socket.sslerror: [Errno 1] _ssl.c:480: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca (200.107.82.18:700)
Certificate not signed by verified certificate authority
What should I do for fred-client to identify these certificates as valid?.
Thanks in advance.
Note: the new fred-client is perfectly compatible with FRED 2.2.
--
Mario Guerra <mguerra(a)nic.cr>
Hello,
I have noticed there is an option to set address fields disclosure settings in the contact update command, but there is no such option in the create command.
Is there some reason for the commands to have different disclosure options?
Best regards,
Jiri Kuchta
Je dobré vědět, že tento e-mail a přílohy jsou důvěrné. Pokud spolu jednáme o uzavření obchodu, vyhrazujeme si právo naše jednání kdykoli ukončit. Pro fanoušky právní mluvy - vylučujeme tím ustanovení občanského zákoníku o předsmluvní odpovědnosti. Pravidla o tom, kdo u nás a jak vystupuje za společnost a kdo může co a jak podepsat naleznete zde<https://onas.seznam.cz/cz/podpisovy-rad-cz.html>
You should know that this e-mail and its attachments are confidential. If we are negotiating on the conclusion of a transaction, we reserve the right to terminate the negotiations at any time. For fans of legalese-we hereby exclude the provisions of the Civil Code on pre-contractual liability. The rules about who and how may act for the company and what are the signing procedures can be found here<https://onas.seznam.cz/cz/signature-rules.html>.
Greetings,
I am experiencing a bit of a problem here on daphne, out of nowhere. The
FRED services have never stopped running for two months now but daphne puts
out the following message after hitting login.
Error:
Error: Backend server is not running!
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/fred_webadmin/exposed.py", line 25,
in _wrapper
return view_func(*args, **kwd)
File "/usr/lib/python2.7/dist-packages/fred_webadmin/controller/adif.py",
line 241, in login
self._authenticate(form, admin)
File "/usr/lib/python2.7/dist-packages/fred_webadmin/controller/adif.py",
line 175, in _authenticate
auth.authenticate_user(admin, login, password)
File "/usr/lib/python2.7/dist-packages/fred_webadmin/auth/corba_auth.py",
line 11, in authenticate_user
admin.authenticateUser(recoder.u2c(username), recoder.u2c(password))
File "/tmp/tmprSxSnq", line 6903, in authenticateUser
TRANSIENT: CORBA.TRANSIENT(omniORB.TRANSIENT_ConnectFailed,
CORBA.COMPLETED_NO)
All FRED services are still running. The logs don't show anything
conclusive, what could be happening?
Regards,
Moeketsi Maphoi
Systems Engineer: LsNIC
