Hi I am looking at using the fred-client to communicate zia EPP with
Ausregistry the AU registrar. I am able to get the client to run so I
am assuming that my config is ok and SSL ket files are correct.
Though when I connect and try to do a simple hello statement I get this error:
registry:/var/www/fred# python2.4 ./fred-client --config ./conf/fred-client.conf
FredClient 1.6.1
Type "help", "license" or "credits" for more information.
Using configuration from ./conf/fred-client.conf
> hello
Used socket type: IPv4.
Socket timeout: 10.0 sec.
Connecting to portal-ote.ausregistry.net.au, port 700 ...
Connection established.
Try to open SSL layer...
ERROR: getaddrinfo() socket.error [-8] Servname not supported for ai_socktype
>
This suggests to me that that the error is from a misconfiguration
hosname but I have checked and this looks fine as i is the one from
our existing EPP solution. What else would cause this error.
I was getting an error about EOF but downloaded the latest version of
the fred-client and now I am getting this error. I am now using
version 1.6.1.
Also my config is as bellow, please note that I have used both the the
hostname and the IP address of the server in the host config value. I
have even tried this with the hostname/ip in parenthesize and no
success there.
My config is as follows:
> registry:/var/www/fred# cat conf/fred-client.conf
[connect]
dir=/var/www/fred/fred/certificates
host = portal-ote.ausregistry.net.au
port = 700
ssl_cert = %(dir)s/CHEAPERDOMAINS-OTE-cert.pem
ssl_key = %(dir)s/CHEAPERDOMAINS-key.pem
username = ***************
password = ***************
;; Every XML namespace can have the version independent to others:
schema_version_contact = 1.2
schema_version_nsset = 1.2
schema_version_domain = 1.2
schema_version_enum = 1.1
schema_version_fred = 1.0
schema_version_epp = 1.0
;; socket timeout in sec. In MS Windows MUST be set to 0.0 (timeout bug)
timeout = 10.0
;; turn off automatic login process after start up
nologin = n
[session]
schema = /var/www/fred/fred/schemas/all-1.4.xsd
;; send "poll ack" right after to "poll req"
poll_autoack = off
;; confirm all editable commands
confirm_send_commands = on
;; enable/disable xmllint
validate = on
;; display colors on tty console
colors = yes
;; set verbose level 1,2,3
verbose = 3
Jatomir and all:
Thanks. I've tested the Live CD with the 01/01/2008 date. It works
perfectly. The net effect is that it create zones so easily and, at the
same time, stores in a database the administrative data using EPP.
Moreover it keeps it simple.
The disk installation:
In our case my approach has been installing the Ubuntu hardy (8.04)
.deb packages, fred-*.deb, which install dome dependencies too. I see
that there are no .dev for fred-server (including the Python parts), so
I installed these by hand (in /usr/.local) . Is that correct?. What
about generating .deb packages for these, too?.
For installing the certificates I do this:
1. I use the CA included in the ca-certificates Debian package which, in
my opinion, is adequate (I don't have to generate a CA certificate myself.
2. For the mod-eppd Apache module, I generate the self-signed
certificates using the usual procedures for generating them for
encrypted HTML:
openssl genrsa -des3 -out eppd.key 4096
openssl req -new -key eppd.key -out eppd.csr
openssl x509 -req -days 3650 -in eppd.csr -signkey eppd.key -out eppd.crt
openssl rsa -in eppd.key -out eppd.key.insecure
mv eppd.key eppd.key.secure;mv eppd.key.insecure eppd.key
chmod 600 *.key
/etc/init.d/apache2 force-reload
3. For the fred-client certificate configuration I rather use a method I
prefer, say,, for dovecot SSL configuration:
openssl req -new -x509 -nodes -out eppclient.pem -keyout eppclient.pem
4. After generating both certificates I first configure the mod-eppd
virtualhost:
Listen *:700
<VirtualHost *:700>
CorbaEnable On
CorbaNameservice "localhost"
CorbaObject "EPP" "EPP_alias"
EPPprotocol On
EPPObject "EPP_alias"
EPPschema "/usr/share/fred-mod-eppd/schemas/all-1.4.xsd"
EPPservername "CR.NIC's EPP server"
EPPlog "/var/log/apache2/eppd.log"
EPPloglevel error
EPPvalidResponse Off
SSLEngine off
SSLCipherSuite
ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+
EXP:+eNULL
SSLVerifyClient require
SSLCertificateFile /etc/ssl/fred/eppd.crt
SSLCertificateKeyFile /etc/ssl/fred/eppd.key
SSLCACertificateFile /etc/ssl/certs/ca.pem
SSLVerifyDepth 1
</VirtualHost>
Notice the /etc/ssl/certs/ca.pem CA certificate, which is the standard
Ubuntu CA certificate. This should be adequate, because it expires much
later.
5. /etc/init.d/apache2 force-reload
6. For the epp-client configuration file I have this in
/usr/local/etc/fred/fred-client.conf:
[connect]
;; dir=/usr/local/share/fred-client/ssl
host = localhost
port = 700
ssl_cert = /etc/ssl/fred/eppclient.pem
ssl_key = /etc/ssl/fred/eppclient.pem
username = REG-FRED_A
password = passwd
username2 = REG-FRED_B
password2 = passwd
etc.....
7. When I run fred-client I get this:
root@mguerra:/etc/fred# fred-client
FredClient 1.6.1
Type "help", "license" or "credits" for more information.
Using configuration from /usr/local/etc/fred/fred-client.conf
Connecting to localhost, port 700 ...
ERROR: socket.sslerror: (1, 'error:140770FC:SSL
routines:SSL23_GET_SERVER_HELLO:unknown protocol') (localhost:700)
Certificate not signed by verified certificate authority.
The date gives this:
mié sep 24 11:33:57 CST 2008 (mié means Wednesday).
What can be the reason for this?. Should I use other CA certificate?. Or
perhaps I should use a certificate in ~/fredclient.pem?.
Thank you in advance.
Mario
Jaromír Talír,
I would like to request you or .CZ to index the subject line for this
FRED-USERS discussion list with a list identifier so that we can
separate its mail from the rest and hence avoid its mail being caught
up in the spam filter.
You may just use or include something like [FRED-USERS] in the
subject line like most lists now do, like in my subject above.
I like to read mail from this list but it is becoming difficult to
separate its mail from spam, the message below is such an example.
Regards,
Paulos
======================
Dr Paulos B Nyirenda
.mw ccTLD
http://www.registrar.mw
------- Forwarded message follows -------
From: Marc Manthey <marc(a)let.de>
To: fred-users(a)lists.nic.cz
Subject: Re: Payment solution
Date sent: Sun, 19 Oct 2008 19:39:58 +0200
Send reply to: fred-users(a)lists.nic.cz
<mailto:fred-users-request@lists.nic.cz?subject=unsubscribe>
<mailto:fred-users-request@lists.nic.cz?subject=subscribe>
Keywords:
Am 19.10.2008 um 19:23 schrieb Petur Kirke:
>
> Does FRED contain a payment solution ? Where domain registrars or
> registrants can make payments to the cctld Manager using creditcard ?
i think the developerteam would apriciate to implement such a thing
when you pay for it ;)
Question : Would you share it after you pay for it ? ;)
> This email and its attachments may be confidential
????
Marc
_______________________________________________
Fred-users mailing list
Fred-users(a)lists.nic.cz
https://lists.nic.cz/mailman/listinfo/fred-users
------- End of forwarded message -------
Im trying to use yum to install Fred.
At the download page in the Fred homepage, it says, i should first install this package (repository):
http://fred.nic.cz/attachment/wiki/attachments/fred-repo-1.0-1.noarch.rpm?f…
I so did.
According to Freds homepage, then i should be able to run this command:
yum install fred-*
But when i run it, i get this error:
http://archive.nic.cz/yum/fred/5/i386/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fred. Please verify its path and try again.
I then checked the url: http://archive.nic.cz/yum/fred/5/i386/repodata/repomd.xml
and it is wrong.
So my question is: How can i use yum to install fred ?
regards
Peter
________________________________
This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed.
If you are not the intended recipient or authorized to receive information for the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If the email contains proposals, they are valid for 30 days following the date of email transmission. Finally, the recipient should check this email and any attachment for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by email.
Hello:
I'm working for the NIC in Costa Rica and we consider an excellent
alternative the FRED software made by nic.cz. It's nioe to e-meet you....
We have tested both the Live CD and the Debian/Ubuntu debs on an Ubuntu 8.04
box. For the second, we downloaded the deb packages with apt-get, ussing the
8.04 repository.
In both cases, when executing fred_client we get these results:
-----------------------------------------------------------------
root@nic-laptop:/etc/ssl# /usr/local/bin/fred-client -c /etc/ssl/fred.crt
-k /etc/ssl/fred.key -h localhost
FredClient 1.6.1
Type "help", "license" or "credits" for more information.
Using configuration from /usr/local/etc/fred/fred-client.conf
Connecting to localhost, port 700 ...
ERROR: socket.sslerror: (1, 'error:140770FC:SSL
routines:SSL23_GET_SERVER_HELLO:unknown protocol') (localhost:700)
Certificate not signed by verified certificate authority.
------------------------------------------------------------------
The same happens with the Live CD. Are we overlooking something?.
--
Mario A. Guerra
San José, Costa RIca
Hello!
I try to test the Live CD fred-1.6.iso (FredClient 1.5.1) and when I
execute fred_client I get the following error message:
ERROR: socket.sslerror: (1, 'error:14094415:SSL
routines:SSL3_READ_BYTES:sslv3 alert certificate expired') (localhost:700)
Certificate not signed by verified certificate authority.
Looks like there is an error in the client.pem file which is included
in the CD.
Is there a quick fix for this?
Hello ,
I am trying to install fred on CentOS5 and when I try to install the server
component with the command below
./configure --build=i386 --prefix=/usr
PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/usr/local/lib/pkgconfig: $$ make
I get the error beneath, can anyone help me solve this.
==============================================================
checking whether CORBA ports are unique... yes
checking for /usr/share/idl/fred//ccReg.idl... configure: error: cannot
check for file existence when cross compiling
===========================================================================
regards
Hi,
I setup your fred, but when I log on http://www.mypage.com:18456/ with firefox is ok but with explorer 7 or opera it do not want
:(
is this normal?
I tried to install FRED in a fedora 9 server but without success.
Do you have a stable, tested version for fedora 9, also for 64 bit server?
Please forget about fedora 8 version, develope it for fedora 9, anybody who will want to use your solutions will start with a fresh linux install, with some latest version.
Domain registration business require 100% stable solutions. I spended 2 days with FRED installation now I'm frustrated.
this is the last error
Total size: 8.6 M
Total download size: 8.6 M
Is this ok [y/N]: y
Downloading Packages:
(1/6): omniORB-utils-4.1.1-1.i386.rpm | 33 kB 00:00
(2/6): libomniORB4.1-4.1.1-1.i386.rpm | 6.9 MB 00:12
(3/6): omniORB-servers-4.1.1-1.i386.rpm | 49 kB 00:00
(4/6): omniORB-doc-4.1.1-1.i386.rpm | 1.1 MB 00:02
(5/6): omniORBpy-doc-3.1-1.i386.rpm | 488 kB 00:00
(6/6): omniORB-bootscripts-4.1.1-1.i386.rpm | 5.9 kB 00:00
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Check Error:
file /usr/lib/python2.5/site-packages/CORBA.py from install of omniORBpy-standard-3.1-1.i386 conflicts with file from package pyorbit-2.14.3-2.fc9.i386
file /usr/lib/python2.5/site-packages/CORBA.pyc from install of omniORBpy-standard-3.1-1.i386 conflicts with file from package pyorbit-2.14.3-2.fc9.i386
file /usr/lib/python2.5/site-packages/CORBA.pyo from install of omniORBpy-standard-3.1-1.i386 conflicts with file from package pyorbit-2.14.3-2.fc9.i386
file /usr/lib/python2.5/site-packages/PortableServer.py from install of omniORBpy-standard-3.1-1.i386 conflicts with file from package pyorbit-2.14.3-2.fc9.i386
file /usr/lib/python2.5/site-packages/PortableServer.pyc from install of omniORBpy-standard-3.1-1.i386 conflicts with file from package pyorbit-2.14.3-2.fc9.i386
file /usr/lib/python2.5/site-packages/PortableServer.pyo from install of omniORBpy-standard-3.1-1.i386 conflicts with file from package pyorbit-2.14.3-2.fc9.i386
Hello,
this is probably first message from us to this list after it's creation.
That's not good, but hopefully this will change in near future. I always
waited to some interesting thing to announce and found all changes till
now not so much interesting ;)
Actually we have interesting web pages http://fred.nic.cz full of useful
information. I will try at least announce here new changes on these web
pages such source update, documentation update etc.
Right now with a release of new version 1.10 of our registration system
I found one thing really cool to announce. This is completely rewritten
build system of all components of FRED. It was never so easy to install
FRED from sources. To support this installation I uploaded there little
bash script fred-manager (http://fred.nic.cz/sources/fred-manager).
Everyone should be able to install fred in this few steps:
wget http://fred.nic.cz/sources/fred-manager
chmod a+x fred-manager
./fred-manager download
./fred-manager install
./fred-manager start
This will download and unpack sources, build all compoments in build
subdirectory of your current directory and install all results into root
subdirectory. Command start will run all necessary servers that include
apache and postgres. They don't interfere at all with your system wide
proceses of the same name. All is installed into your current directory,
all is running under privileges of your current user. Servers will
allocate about 10 ports to listen on.
After that you can test client by running script
at ./root/bin/fred-client. You can check zone generation by
calling ./root/bin/genzone-client. You can check web applications by
pointing your browser to localhost:22354.
You can also just check this script instead, to find out how to install
FRED.
One thing will be probably a little bit painful - to satisfy all
dependencies. Configuration script will fail when they find some missing
dependency. Then you have to manually install it. We tried successfuly
to install FRED on Fedora (8,9), Ubuntu (Dapper) and Gentoo. Except from
omniORB all dependencies should be in distribution repositories. We
created a overall schema of this dependencies
http://fred.nic.cz/attachment/wiki/attachments/component_schema.png
Hope that traffic on this lists will arise a little bit since now.
Enjoy our work! ;)
Jaromir
