fred-users July 2020

fred-users@lists.nic.cz

2 participants
3 discussions

Setting up a CA and signing certificates with it

by Mario Guerra

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>

3 years, 3 months

FRED in Docker perhaps?

by Piotr Przybył

Hello FRED team I've skimmed the FRED docs and AFAICT there's no distribution in form of Docker image(s). Does anyone have plans "dockerizing" FRED? (Please don't get me wrong, I'm not trying to make any sort of pressure that anyone has to do something, I'm just asking and that's it.) Thank you Piotr

6 years, 2 months

help test - GDPR compliance test phase on .mw domains - invitation

by Dr P Nyirenda

.mw Registrar, GDPR compliance test phase on .mw - invitation ======================================== I am pleased to advise that the Malawi .mw ccTLD registry on FRED has started a test phase for compliance on GDPR compliance for all and we would like to invite you to assist us to test. We have now mounted a test server to handle both EPP and WHOIS on ngoli3.sdnp.org.mw that you can test right away. A WHOIS query for any of your existing domains will show that we are now hiding details on the e-mail, phone, fax and other details while showing name, organisation, address, DNS servers. The database on the test server is that of 24 July 2020. You can compare the following: 1. Current WHOIS at: http://www.registrar.mw/whois-intro.php 2. Current command line WHOIS: $whois domains.mw -h ngoli.sdnp.org.mw 3. GDPR compliant test : http://ngoli3.sdnp.org.mw/whois 4. GDPR compliant command line test: $whois domains.mw -h ngoli3.sdnp.org.mw You can also test creating a new contact using EPP and you will find that the default is "hide" on the above details and it is up to the registrar to toggle this to "disclose" as needed. Please make sure that your EPP client is capable of handling the .mw GDPR complaint environment as you continue to conduct your business using the .mw registry. We will have this test phase running for at least two week from 1 August 2020 after which we will make a decision to move this test phase to the production environment. All modifications that you make on the test environment will be deleted and lost from ngoli3 at the end of the test phase, so, you can test as much as you need to without charge. Please let me know if you face any problems using the new GDPR compliant test .mw registry on EPP, WHOIS or any other service. These steps are very important to us. Regards, Dr Paulos B Nyirenda NIC.MW & .mw ccTLD http://www.nic.mw Tel: +265-(0)-882 089 166 Cell: +265-(0)-888-824787 WhatsApp: +265-(0)-887386433 -- This email has been checked for viruses by AVG. https://www.avg.com

6 years, 2 months

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

fred-users July 2020