- ripe-list - mailman.ripe.net

2010 Worldwide Infrastructure Security Report available for download.
by Roland Dobbins 01 Feb '11

01 Feb '11

[Apologies for any duplication if you've seen this notification on other lists.] We've just posted the 2010 Worldwide Infrastructure Security Report for download at this URL: <http://www.arbornetworks.com/report> This year's WWISR contains responses and data from the broadest cross-section of SPs to date, including mobile operators and IDC operators in all major geographical regions. The WWISR is based upon input from the global operational community, and as such, is unique in its focus on the operational security aspects of public-facing networks. Many of you contributed to the survey which forms the foundation of the report; as always, we're grateful for your insight and participation, and welcome your feedback and comments. Thanks much! ------------------------------------------------------------------------ Roland Dobbins <rdobbins(a)arbor.net> // <http://www.arbornetworks.com>

1 0

IANA Allocates Two /8s of IPv4 Space to APNIC
by Axel Pawlik 31 Jan '11

31 Jan '11

[Apologies for duplicate emails] Dear colleagues, On 1 February 2011, the IANA allocated two /8s of IPv4 address space to APNIC, the Regional Internet Registry (RIR) for the Asia Pacific region. This means that only five /8s of IPv4 address space are left in the IANA free pool and the "Global Policy for the Allocation of the Remaining IPv4 Address Space" will be triggered. This policy can be found online at: http://www.icann.org/en/general/allocation-remaining-ipv4-space.htm When this policy comes into effect, the five RIRs will each receive one of the five remaining /8s and the global IPv4 pool will be exhausted. We expect IANA to allocate these final /8s within the next few days. For further information please see: http://www.ripe.net/v4exhaustion/ Regards, Axel Pawlik Managing Director RIPE NCC

1 0

[members-discuss] Re: NCC#2011014211 NCC Registration Help - Please
by RIPE NCC Customer Services 26 Jan '11

26 Jan '11

Dear Paul, Please be aware that if your company has legally changed its name, a new Standard Service Agreement with the RIPE NCC is required. The current Standard Service Agreement can be found online (for you to view) via the following link: http://www.ripe.net/ripe/docs/service-agreement.html Before we send the new Service Agreement, we need the following three things: 1. A copy of your organisation's legal registration papers (please send by email in a pdf) Official registration papers are the trade register documents that prove your organisation is a registered legal entity, authorised to carry out business activities in your country. Your local Chamber of Commerce usually issues these. 2. A proof of company namechange (Please send by email in a pdf) Please provide some proof that *COMPANY X* is now *COMPANY Y*. We prefer a certificate from the chamber of commerce, if this is not possible; a letter on company letterhead paper of the old company will do. The letter should be signed by both managing directors (Old and new company). 3. Please fill in the fields below In order for RIPE NCC to be able to send you the service agreements with the correct information, please make sure that the fields below are correct: =========================== Name of organisation: [your organisation's new legal name and type of business entity] [Must match with the name on your company registration papers] Your organisation's legal address (No PO box please): legal-addr-street: legal-addr-zip: legal-addr-city: legal-addr-country: Your organisation's postal address to where the contracts will be sent: post-addr-company: post-addr-person: post-addr-street: post-addr-zip: post-addr-city: post-addr-country: Your organisation's billing details: bill-addr-company: bill-addr-person: bill-addr-street: bill-addr-postcode: bill-addr-city: bill-addr-country: bill-mail: bill-ref: bill-vatno: ==================== When we have received all the information and documents, we will send you two copies of the new Standard Service Agreement. Please sign both copies and return one to our offices in Amsterdam. We will let you know when we will post the Service Agreements. -- If you have any questions, please feel free to contact us. Best regards, Smahena Amakran Customer Services RIPE NCC ============================================================ Visit www.IPv6ActNow.org, the one-stop website that explains eveerything you need to know about IPv6. ============================================================ On Tue, 25 Jan 2011 11:15:56 +0000, Hodges Paul wrote: > Hello > > I have am trying to update the Hiscox Group Company name and Postal Address information, but it is requesting that I enter: > > Field 'NCC members discussion' is required. > > So when I then go to the info button and follow the link (http://www.ripe.net/membership/lists.html.) through to create a NCC email address, it then re directs me to > > IPE NCC members can subscribe to this list through the RIPE NCC LIR Portal. More information on how to change or add subscriptions is available at: http://www.ripe.net/membership/subscribe-membership.html > > Which I then click on and it tells me to do: > > Change or Add Subscription Addresses > > To change or add subscription e-mail addresses, please follow these steps: > > 1. Log in to the LIR Portal<https://lirportal.ripe.net/> > 2. Click the "General" link at the top-left of the screen > 3. Click the "edit" button at the top of the screen > 4. Scroll down to the section "Subscribed Mailing Lists" > 5. Change the e-mail address in the box, or click the "Add" button to add another e-mail address > 6. Click "Update" to save your changes > So I seem to be stuck in this loop, please can you direct me to the exact URL, so that I can register a NCC email address and then in turn update the Company profile information, so that when RIPE are trying to contact Hiscox, you get directed to the correct person other than someone who has left. > Please feel free to contact me if you wish, > Regards > Paul > > > Paul Hodges > Networks and Security Technology Lead > IT Infrastructure > Hiscox plc > T +44 (0)1206 773840 > M +44 (0)7826523789 > www.hiscox.com<http://www.hiscox.com/> > > > ________________________________ > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. No one else is authorised to distribute, forward, print, copy or act upon any information contained in this email. If you have received this email in error, please notify the sender. > > Hiscox Syndicates Limited, Hiscox Insurance Company Limited, Hiscox Underwriting Limited and Hiscox ASM Limited are authorised and regulated by the Financial Services Authority. Hiscox plc is a company registered in England and Wales under company registration number 2837811 and registered office at 1 Great St Helen's, London EC3A 6HX. ---- If you don't want to receive mails from the RIPE NCC Members Discuss list, please log in to your LIR Portal account at: http://lirportal.ripe.net/ First click on General and then click on Edit. At the bottom of the Page you can add or remove addresses.

2 1

Issues with openssl while installing ripe whoisserver-3.10.1
by Christian Muhirwa 24 Jan '11

24 Jan '11

Hi, Sorry if this is not the right list .... Ive been trying to install the latest ripe whois server on Ubuntu 10.04 server and got these errors below related to openssl ... Am trying to get a feel of it so I can get it to run our TLD whois server. sysadmin@whois:~/whoisserver$ sudo perl Install.PL --verbose --debug --for-development --all --prefix=/usr/local/whois --sqlpass=xxxxxx Use of uninitialized value in string eq at Install.PL line 80. Running './autogen.sh'=============================== Automake v1.5 is used for building. Your version is 1.11.1. If configuration fails, keep this in mind :) =============================== Running libtoolize libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. libtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT' Running aclocal m4/ripe_opl_only.m4:4: warning: underquoted definition of RIPE_OPL_ONLY m4/ripe_opl_only.m4:4: run info '(automake)Extending aclocal' m4/ripe_opl_only.m4:4: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal Running autoheader Running automake src/defs/Makefile.am:16: `%'-style pattern rules are a GNU make extension Running autoconf ....done Running './build.sh' *** *** Compiling c-client *** ~/whoisserver/third-party/imap-2004g ~/whoisserver make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox' EXTRAAUTHENTICATORS='' PASSWDTYPE=std SSLTYPE=nopwd IP=4 EXTRASPECIALS='' BUILDTYPE=slx \ SPECIALS="GSSDIR=/usr SSLDIR=/usr SSLINCLUDE=/usr/include/openssl SSLCERTS=/etc/ssl/certs SSLKEYS=/etc/ssl/private" make[1]: Entering directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g' Building c-client for slx... echo `cat SPECIALS` > c-client/SPECIALS cd c-client;make slx EXTRACFLAGS=''\ EXTRALDFLAGS=''\ EXTRADRIVERS='mbox'\ EXTRAAUTHENTICATORS=''\ PASSWDTYPE=std SSLTYPE=nopwd IP=4\ GSSDIR=/usr SSLDIR=/usr SSLINCLUDE=/usr/include/openssl SSLCERTS=/etc/ssl/certs SSLKEYS=/etc/ssl/private make[2]: Entering directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g/c-client' You are building for libc6/glibc versions of Secure Linux If you want libc5 versions you must use sl5 instead! If you want libc4 versions you must use sl4 instead! make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox' EXTRAAUTHENTICATORS='' PASSWDTYPE=std SSLTYPE=nopwd IP=4 `cat SPECIALS` OS=slx \ SIGTYPE=psx CHECKPW=psx CRXTYPE=nfs \ SPOOLDIR=/var/spool \ ACTIVEFILE=/var/lib/news/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -fno-omit-frame-pointer -O2" \ BASELDFLAGS="-lcrypt" make[3]: Entering directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g/c-client' sh -c 'rm -rf auths.c crexcl.c nfstest.c linkage.[ch] siglocal.c osdep*.[ch] *.o ARCHIVE *FLAGS *TYPE c-client.a || true' Once-only environment setup... echo cc > CCTYPE echo -g -fno-omit-frame-pointer -O2 '' > CFLAGS echo -DCREATEPROTO=unixproto -DEMPTYPROTO=unixproto \ -DMAILSPOOL=\"/var/spool/mail\" \ -DANONYMOUSHOME=\"/var/spool/mail/anonymous\" \ -DACTIVEFILE=\"/var/lib/news/active\" -DNEWSSPOOL=\"/var/spool/news\" \ -DRSHPATH=\"/usr/bin/rsh\" -DLOCKPGM=\"/etc/mlock\" > OSCFLAGS echo -lcrypt > LDFLAGS echo "ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;ranlib c-client.a" > ARCHIVE echo slx > OSTYPE ./drivers mbox imap nntp pop3 mh mx mbx tenex mtx mmdf unix news phile dummy ./mkauths md5 pla log make[4]: Entering directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g/c-client' echo -DMD5ENABLE=\"/etc/cram-md5.pwd\" >> OSCFLAGS make[4]: Leaving directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g/c-client' ln -s os_slx.h osdep.h ln -s os_slx.c osdepbas.c ln -s log_std.c osdeplog.c ln -s sig_psx.c siglocal.c ln -s crx_nfs.c crexcl.c ln -s ip4_unix.c ip_unix.c sh -c '(test -f /usr/include/sys/statvfs.h -a slx != sc5 -a slx != sco) && ln -s nfstnew.c nfstest.c || ln -s nfstold.c nfstest.c' Standard password authentication ln -s ckp_psx.c osdepckp.c Building with SSL ln -s ssl_unix.c osdepssl.c echo -I/usr/include/openssl -I/usr/include/openssl/openssl -DSSL_CERT_DIRECTORY=\"/etc/ssl/certs\" -DSSL_KEY_DIRECTORY=\"/etc/ssl/private\" >> OSCFLAGS echo " ssl_onceonlyinit ();" >> linkage.c echo -L/usr/lib -lssl -lcrypto >> LDFLAGS Building with SSL and plaintext passwords disabled unless SSL/TLS echo " mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >> linkage.c cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c Building OS-dependent module If you get No such file error messages for files x509.h, ssl.h, pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL is not installed on your system. Either install OpenSSL first or build with command: make slx SSLTYPE=none `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c In file included from auths.c:1, from env_unix.c:141, from osdep.c:42: auth_md5.c: In function âauth_md5_pwdâ: auth_md5.c:186: warning: ignoring return value of âreadâ, declared with attribute warn_unused_result In file included from osdep.c:42: env_unix.c: In function âpw_loginâ: env_unix.c:644: warning: ignoring return value of âchdirâ, declared with attribute warn_unused_result In file included from osdep.c:47: flocklnx.c: In function âsafe_flockâ: flocklnx.c:52: warning: format not a string literal and no format arguments osdep.c:198:18: error: x509.h: No such file or directory osdep.c:199:17: error: ssl.h: No such file or directory osdep.c:201:17: error: pem.h: No such file or directory osdep.c:202:20: error: buffer.h: No such file or directory osdep.c:203:17: error: bio.h: No such file or directory osdep.c:204:20: error: crypto.h: No such file or directory osdep.c:205:18: error: rand.h: No such file or directory osdep.c: At top level: osdep.c:216: error: expected specifier-qualifier-list before âSSL_CTXâ osdep.c:229: error: expected declaration specifiers or â...â before âX509_STORE_CTXâ osdep.c:233: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â*â token osdep.c: In function âssl_start_workâ: osdep.c:379: error: âBIOâ undeclared (first use in this function) osdep.c:379: error: (Each undeclared identifier is reported only once osdep.c:379: error: for each function it appears in.) osdep.c:379: error: âbioâ undeclared (first use in this function) osdep.c:380: error: âX509â undeclared (first use in this function) osdep.c:380: error: âcertâ undeclared (first use in this function) osdep.c:386: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:390: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:393: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:393: error: âSSL_VERIFY_NONEâ undeclared (first use in this function) osdep.c:394: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:394: error: âSSL_VERIFY_PEERâ undeclared (first use in this function) osdep.c:396: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:398: error: âSSLSTREAMâ has no member named âconâ osdep.c:398: error: âSSLâ undeclared (first use in this function) osdep.c:398: error: expected expression before â)â token osdep.c:400: error: âBIO_NOCLOSEâ undeclared (first use in this function) osdep.c:401: error: âSSLSTREAMâ has no member named âconâ osdep.c:402: error: âSSLSTREAMâ has no member named âconâ osdep.c:403: error: âSSLSTREAMâ has no member named âconâ osdep.c:403: error: âSSLSTREAMâ has no member named âconâ osdep.c:405: error: âSSLSTREAMâ has no member named âconâ osdep.c:410: error: âSSLSTREAMâ has no member named âconâ osdep.c: At top level: osdep.c:435: error: expected declaration specifiers or â...â before âX509_STORE_CTXâ osdep.c: In function âssl_open_verifyâ: osdep.c:442: error: âctxâ undeclared (first use in this function) osdep.c: In function âssl_getlineâ: osdep.c:504: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:506: error: âSSLSTREAMâ has no member named âictrâ osdep.c:507: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:522: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:523: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:524: error: âSSLSTREAMâ has no member named âictrâ osdep.c: In function âssl_getbufferâ: osdep.c:551: error: âSSLSTREAMâ has no member named âictrâ osdep.c:553: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:555: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:557: error: âSSLSTREAMâ has no member named âictrâ osdep.c: In function âssl_getdataâ: osdep.c:577: error: âSSLSTREAMâ has no member named âconâ osdep.c:577: error: âSSLSTREAMâ has no member named âconâ osdep.c:579: error: âSSLSTREAMâ has no member named âictrâ osdep.c:580: error: âSSLSTREAMâ has no member named âconâ osdep.c:602: error: âSSLSTREAMâ has no member named âconâ osdep.c:602: error: âSSLSTREAMâ has no member named âibufâ osdep.c:604: error: âSSLSTREAMâ has no member named âconâ osdep.c:604: error: âSSL_ERROR_WANT_READâ undeclared (first use in this function) osdep.c:606: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:606: error: âSSLSTREAMâ has no member named âibufâ osdep.c:607: error: âSSLSTREAMâ has no member named âictrâ osdep.c: In function âssl_soutâ: osdep.c:636: error: âSSLSTREAMâ has no member named âconâ osdep.c:641: error: âSSLSTREAMâ has no member named âconâ osdep.c: In function âssl_abortâ: osdep.c:666: error: âSSLSTREAMâ has no member named âconâ osdep.c:667: error: âSSLSTREAMâ has no member named âconâ osdep.c:668: error: âSSLSTREAMâ has no member named âconâ osdep.c:669: error: âSSLSTREAMâ has no member named âconâ osdep.c:671: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:672: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:673: error: âSSLSTREAMâ has no member named âcontextâ osdep.c: In function âssl_server_initâ: osdep.c:773: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:779: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:779: error: âSSL_OP_ALLâ undeclared (first use in this function) osdep.c:781: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:785: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:789: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:790: error: âSSL_FILETYPE_PEMâ undeclared (first use in this function) osdep.c:795: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:796: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:796: error: âssl_genkeyâ undeclared (first use in this function) osdep.c:798: error: âSSLSTREAMâ has no member named âconâ osdep.c:798: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:802: error: âSSLSTREAMâ has no member named âconâ osdep.c:804: error: âSSLSTREAMâ has no member named âconâ osdep.c:825: warning: format â%.80sâ expects type âchar *â, but argument 3 has type âintâ osdep.c: At top level: osdep.c:837: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â*â token osdep.c: In function âssl_server_input_waitâ: osdep.c:867: error: âSSLSTREAMâ has no member named âictrâ osdep.c:868: error: âSSLSTREAMâ has no member named âconâ osdep.c:868: error: âSSLSTREAMâ has no member named âconâ osdep.c:870: error: âSSLSTREAMâ has no member named âconâ osdep.c:871: error: âSSLSTREAMâ has no member named âconâ osdep.c:871: error: âSSLSTREAMâ has no member named âibufâ osdep.c:872: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:872: error: âSSLSTREAMâ has no member named âibufâ osdep.c:873: error: âSSLSTREAMâ has no member named âictrâ In file included from osdep.c:885: sslstdio.c: In function âPBINâ: sslstdio.c:30: error: âSSLSTREAMâ has no member named âictrâ sslstdio.c:31: error: âSSLSTREAMâ has no member named âiptrâ sslstdio.c: In function âPSINâ: sslstdio.c:49: error: âSSLSTREAMâ has no member named âictrâ sslstdio.c:50: error: âSSLSTREAMâ has no member named âictrâ sslstdio.c:52: error: âSSLSTREAMâ has no member named âiptrâ make[3]: *** [osdep.o] Error 1 make[3]: Leaving directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g/c-client' make[2]: *** [slx] Error 2 make[2]: Leaving directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g/c-client' make[1]: *** [OSTYPE] Error 2 make[1]: Leaving directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g' make: *** [slx] Error 2 512 at Install.PL line 413 I have compiled and installed openssl-1.0.0c in /usr/local/ssl. Please help me. Thanks Christian

1 0

Issues with openssl while installing ripe whoisserver-3.10.1
by Christian Muhirwa 24 Jan '11

24 Jan '11

Hi, Sorry if this is not the right list .... Ive been trying to install the latest ripe whois server on Ubuntu 10.04 server and got these errors below related to openssl ... Am trying to get a feel of it so I can get it to run our TLD whois server. sysadmin@whois:~/whoisserver$ sudo perl Install.PL --verbose --debug --for-development --all --prefix=/usr/local/whois --sqlpass=xxxxxx Use of uninitialized value in string eq at Install.PL line 80. Running './autogen.sh'=============================== Automake v1.5 is used for building. Your version is 1.11.1. If configuration fails, keep this in mind :) =============================== Running libtoolize libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. libtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT' Running aclocal m4/ripe_opl_only.m4:4: warning: underquoted definition of RIPE_OPL_ONLY m4/ripe_opl_only.m4:4: run info '(automake)Extending aclocal' m4/ripe_opl_only.m4:4: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal Running autoheader Running automake src/defs/Makefile.am:16: `%'-style pattern rules are a GNU make extension Running autoconf ....done Running './build.sh' *** *** Compiling c-client *** ~/whoisserver/third-party/imap-2004g ~/whoisserver make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox' EXTRAAUTHENTICATORS='' PASSWDTYPE=std SSLTYPE=nopwd IP=4 EXTRASPECIALS='' BUILDTYPE=slx \ SPECIALS="GSSDIR=/usr SSLDIR=/usr SSLINCLUDE=/usr/include/openssl SSLCERTS=/etc/ssl/certs SSLKEYS=/etc/ssl/private" make[1]: Entering directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g' Building c-client for slx... echo `cat SPECIALS` > c-client/SPECIALS cd c-client;make slx EXTRACFLAGS=''\ EXTRALDFLAGS=''\ EXTRADRIVERS='mbox'\ EXTRAAUTHENTICATORS=''\ PASSWDTYPE=std SSLTYPE=nopwd IP=4\ GSSDIR=/usr SSLDIR=/usr SSLINCLUDE=/usr/include/openssl SSLCERTS=/etc/ssl/certs SSLKEYS=/etc/ssl/private make[2]: Entering directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g/c-client' You are building for libc6/glibc versions of Secure Linux If you want libc5 versions you must use sl5 instead! If you want libc4 versions you must use sl4 instead! make build EXTRACFLAGS='' EXTRALDFLAGS='' EXTRADRIVERS='mbox' EXTRAAUTHENTICATORS='' PASSWDTYPE=std SSLTYPE=nopwd IP=4 `cat SPECIALS` OS=slx \ SIGTYPE=psx CHECKPW=psx CRXTYPE=nfs \ SPOOLDIR=/var/spool \ ACTIVEFILE=/var/lib/news/active \ RSHPATH=/usr/bin/rsh \ BASECFLAGS="-g -fno-omit-frame-pointer -O2" \ BASELDFLAGS="-lcrypt" make[3]: Entering directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g/c-client' sh -c 'rm -rf auths.c crexcl.c nfstest.c linkage.[ch] siglocal.c osdep*.[ch] *.o ARCHIVE *FLAGS *TYPE c-client.a || true' Once-only environment setup... echo cc > CCTYPE echo -g -fno-omit-frame-pointer -O2 '' > CFLAGS echo -DCREATEPROTO=unixproto -DEMPTYPROTO=unixproto \ -DMAILSPOOL=\"/var/spool/mail\" \ -DANONYMOUSHOME=\"/var/spool/mail/anonymous\" \ -DACTIVEFILE=\"/var/lib/news/active\" -DNEWSSPOOL=\"/var/spool/news\" \ -DRSHPATH=\"/usr/bin/rsh\" -DLOCKPGM=\"/etc/mlock\" > OSCFLAGS echo -lcrypt > LDFLAGS echo "ar rc c-client.a osdep.o mail.o misc.o newsrc.o smanager.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;ranlib c-client.a" > ARCHIVE echo slx > OSTYPE ./drivers mbox imap nntp pop3 mh mx mbx tenex mtx mmdf unix news phile dummy ./mkauths md5 pla log make[4]: Entering directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g/c-client' echo -DMD5ENABLE=\"/etc/cram-md5.pwd\" >> OSCFLAGS make[4]: Leaving directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g/c-client' ln -s os_slx.h osdep.h ln -s os_slx.c osdepbas.c ln -s log_std.c osdeplog.c ln -s sig_psx.c siglocal.c ln -s crx_nfs.c crexcl.c ln -s ip4_unix.c ip_unix.c sh -c '(test -f /usr/include/sys/statvfs.h -a slx != sc5 -a slx != sco) && ln -s nfstnew.c nfstest.c || ln -s nfstold.c nfstest.c' Standard password authentication ln -s ckp_psx.c osdepckp.c Building with SSL ln -s ssl_unix.c osdepssl.c echo -I/usr/include/openssl -I/usr/include/openssl/openssl -DSSL_CERT_DIRECTORY=\"/etc/ssl/certs\" -DSSL_KEY_DIRECTORY=\"/etc/ssl/private\" >> OSCFLAGS echo " ssl_onceonlyinit ();" >> linkage.c echo -L/usr/lib -lssl -lcrypto >> LDFLAGS Building with SSL and plaintext passwords disabled unless SSL/TLS echo " mail_parameters (NIL,SET_DISABLEPLAINTEXT,(void *) 2);" >> linkage.c cat osdepbas.c osdepckp.c osdeplog.c osdepssl.c > osdep.c Building OS-dependent module If you get No such file error messages for files x509.h, ssl.h, pem.h, buffer.h, bio.h, and crypto.h, that means that OpenSSL is not installed on your system. Either install OpenSSL first or build with command: make slx SSLTYPE=none `cat CCTYPE` -c `cat CFLAGS` `cat OSCFLAGS` -c osdep.c In file included from auths.c:1, from env_unix.c:141, from osdep.c:42: auth_md5.c: In function âauth_md5_pwdâ: auth_md5.c:186: warning: ignoring return value of âreadâ, declared with attribute warn_unused_result In file included from osdep.c:42: env_unix.c: In function âpw_loginâ: env_unix.c:644: warning: ignoring return value of âchdirâ, declared with attribute warn_unused_result In file included from osdep.c:47: flocklnx.c: In function âsafe_flockâ: flocklnx.c:52: warning: format not a string literal and no format arguments osdep.c:198:18: error: x509.h: No such file or directory osdep.c:199:17: error: ssl.h: No such file or directory osdep.c:201:17: error: pem.h: No such file or directory osdep.c:202:20: error: buffer.h: No such file or directory osdep.c:203:17: error: bio.h: No such file or directory osdep.c:204:20: error: crypto.h: No such file or directory osdep.c:205:18: error: rand.h: No such file or directory osdep.c: At top level: osdep.c:216: error: expected specifier-qualifier-list before âSSL_CTXâ osdep.c:229: error: expected declaration specifiers or â...â before âX509_STORE_CTXâ osdep.c:233: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â*â token osdep.c: In function âssl_start_workâ: osdep.c:379: error: âBIOâ undeclared (first use in this function) osdep.c:379: error: (Each undeclared identifier is reported only once osdep.c:379: error: for each function it appears in.) osdep.c:379: error: âbioâ undeclared (first use in this function) osdep.c:380: error: âX509â undeclared (first use in this function) osdep.c:380: error: âcertâ undeclared (first use in this function) osdep.c:386: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:390: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:393: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:393: error: âSSL_VERIFY_NONEâ undeclared (first use in this function) osdep.c:394: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:394: error: âSSL_VERIFY_PEERâ undeclared (first use in this function) osdep.c:396: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:398: error: âSSLSTREAMâ has no member named âconâ osdep.c:398: error: âSSLâ undeclared (first use in this function) osdep.c:398: error: expected expression before â)â token osdep.c:400: error: âBIO_NOCLOSEâ undeclared (first use in this function) osdep.c:401: error: âSSLSTREAMâ has no member named âconâ osdep.c:402: error: âSSLSTREAMâ has no member named âconâ osdep.c:403: error: âSSLSTREAMâ has no member named âconâ osdep.c:403: error: âSSLSTREAMâ has no member named âconâ osdep.c:405: error: âSSLSTREAMâ has no member named âconâ osdep.c:410: error: âSSLSTREAMâ has no member named âconâ osdep.c: At top level: osdep.c:435: error: expected declaration specifiers or â...â before âX509_STORE_CTXâ osdep.c: In function âssl_open_verifyâ: osdep.c:442: error: âctxâ undeclared (first use in this function) osdep.c: In function âssl_getlineâ: osdep.c:504: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:506: error: âSSLSTREAMâ has no member named âictrâ osdep.c:507: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:522: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:523: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:524: error: âSSLSTREAMâ has no member named âictrâ osdep.c: In function âssl_getbufferâ: osdep.c:551: error: âSSLSTREAMâ has no member named âictrâ osdep.c:553: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:555: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:557: error: âSSLSTREAMâ has no member named âictrâ osdep.c: In function âssl_getdataâ: osdep.c:577: error: âSSLSTREAMâ has no member named âconâ osdep.c:577: error: âSSLSTREAMâ has no member named âconâ osdep.c:579: error: âSSLSTREAMâ has no member named âictrâ osdep.c:580: error: âSSLSTREAMâ has no member named âconâ osdep.c:602: error: âSSLSTREAMâ has no member named âconâ osdep.c:602: error: âSSLSTREAMâ has no member named âibufâ osdep.c:604: error: âSSLSTREAMâ has no member named âconâ osdep.c:604: error: âSSL_ERROR_WANT_READâ undeclared (first use in this function) osdep.c:606: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:606: error: âSSLSTREAMâ has no member named âibufâ osdep.c:607: error: âSSLSTREAMâ has no member named âictrâ osdep.c: In function âssl_soutâ: osdep.c:636: error: âSSLSTREAMâ has no member named âconâ osdep.c:641: error: âSSLSTREAMâ has no member named âconâ osdep.c: In function âssl_abortâ: osdep.c:666: error: âSSLSTREAMâ has no member named âconâ osdep.c:667: error: âSSLSTREAMâ has no member named âconâ osdep.c:668: error: âSSLSTREAMâ has no member named âconâ osdep.c:669: error: âSSLSTREAMâ has no member named âconâ osdep.c:671: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:672: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:673: error: âSSLSTREAMâ has no member named âcontextâ osdep.c: In function âssl_server_initâ: osdep.c:773: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:779: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:779: error: âSSL_OP_ALLâ undeclared (first use in this function) osdep.c:781: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:785: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:789: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:790: error: âSSL_FILETYPE_PEMâ undeclared (first use in this function) osdep.c:795: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:796: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:796: error: âssl_genkeyâ undeclared (first use in this function) osdep.c:798: error: âSSLSTREAMâ has no member named âconâ osdep.c:798: error: âSSLSTREAMâ has no member named âcontextâ osdep.c:802: error: âSSLSTREAMâ has no member named âconâ osdep.c:804: error: âSSLSTREAMâ has no member named âconâ osdep.c:825: warning: format â%.80sâ expects type âchar *â, but argument 3 has type âintâ osdep.c: At top level: osdep.c:837: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â*â token osdep.c: In function âssl_server_input_waitâ: osdep.c:867: error: âSSLSTREAMâ has no member named âictrâ osdep.c:868: error: âSSLSTREAMâ has no member named âconâ osdep.c:868: error: âSSLSTREAMâ has no member named âconâ osdep.c:870: error: âSSLSTREAMâ has no member named âconâ osdep.c:871: error: âSSLSTREAMâ has no member named âconâ osdep.c:871: error: âSSLSTREAMâ has no member named âibufâ osdep.c:872: error: âSSLSTREAMâ has no member named âiptrâ osdep.c:872: error: âSSLSTREAMâ has no member named âibufâ osdep.c:873: error: âSSLSTREAMâ has no member named âictrâ In file included from osdep.c:885: sslstdio.c: In function âPBINâ: sslstdio.c:30: error: âSSLSTREAMâ has no member named âictrâ sslstdio.c:31: error: âSSLSTREAMâ has no member named âiptrâ sslstdio.c: In function âPSINâ: sslstdio.c:49: error: âSSLSTREAMâ has no member named âictrâ sslstdio.c:50: error: âSSLSTREAMâ has no member named âictrâ sslstdio.c:52: error: âSSLSTREAMâ has no member named âiptrâ make[3]: *** [osdep.o] Error 1 make[3]: Leaving directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g/c-client' make[2]: *** [slx] Error 2 make[2]: Leaving directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g/c-client' make[1]: *** [OSTYPE] Error 2 make[1]: Leaving directory `/home/sysadmin/whoisserver/third-party/imap-2004g/imap-2004g' make: *** [slx] Error 2 512 at Install.PL line 413 I have compiled and installed openssl-1.0.0c in /usr/local/ssl. Please help me. Thanks Christian

1 0

[members-discuss] [ncc-announce] Mark Your Calendar: RIPE NCC Regional Meeting/Eurasia Network Operators' Group (ENOG)
by Paul Rendek 20 Jan '11

20 Jan '11

Dear Colleagues, The RIPE NCC Regional Meeting/Eurasia Network Operators' Group (ENOG) will take place in Moscow from 6-8 June 2011. This will be the first ever combined RIPE NCC Regional Meeting/ENOG Meeting. We are also happy to announce that a second meeting is to be scheduled for later this year. At the Moscow RIPE NCC Regional Meeting in September 2010, attendees decided to further their cooperation by proposing the creation of a regional forum in which the region’s Internet experts could collaborate on issues unique to the Russian Federation, the Commonwealth of Independent States (CIS), Eastern Europe and other interested parties. This forum is now established as ENOG, and the RIPE NCC is dedicated to actively support and facilitate this newly formed operators' group. The RIPE NCC Regional Meeting/ENOG is a forum for open dialogue, and it's available for all interested parties to attend. This is where network operators can meet their peers and learn from international and local Internet experts. Operational content will be a central part of the agenda. Topics will cover challenges, tools, experiences and best practices in areas such as DNS, peering, routing, IPv6 and more. For the first time at a RIPE NCC Regional Meeting, a day will be dedicated to RIPE activities, where RIPE Policies will be presented and openly discussed. We're already looking forward to an exciting and productive meeting. We're very much looking forward to welcoming you to participate at the meeting in Moscow in June, together making this another successful event. Regards, Paul Rendek Head of External Relations and Communications RIPE NCC on behalf of the RIPE NCC Regional Meeting/ENOG Organising Committee ---- If you don't want to receive mails from the RIPE NCC Members Discuss list, please log in to your LIR Portal account at: http://lirportal.ripe.net/ First click on General and then click on Edit. At the bottom of the Page you can add or remove addresses.

1 0

RIPE Document ripe-508 published
by Axel Pawlik 13 Jan '11

13 Jan '11

Dear colleagues, A new RIPE Document defining the history and purpose of the RIPE Registry has been published. RIPE Document ripe-508, "The RIPE Registry", can be found online at: http://www.ripe.net/ripe/docs/ripe-508.html This document establishes a clear definition of the RIPE Registry that can be referenced by the RIPE community. We encourage you to read this document. Kind regards, Axel Pawlik Managing Director RIPE NCC

1 0

RIPE NCC Resource Certification Service Launch
by Alex Band 03 Jan '11

03 Jan '11

Dear colleagues, The RIPE NCC is proud to announce the production launch of the RIPE NCC resource certification service. With the support of the RIPE community, we have worked very hard to create a service that will help to make our registry more robust and provide a vital element in making Internet routing more secure. Now, more than ever, it is important to be sure who is the legitimate holder of a block of IP addresses. As a first step, the RIPE NCC (in coordination with the other four RIRs) has created a hosted platform. This means that all LIRs will be able to generate a certificate of holdership that will be held in a repository maintained by the RIPE NCC. The feature set is, as it stands, very limited: the certificate will only cover Provider Aggregatable address space, and it is not yet possible to run your own Certificate Authority or generate "child" certificates to create a chain of trust. All of these capabilities will be rolled out over the course of 2011, based on the wishes and input of the RIPE community. This brings me to an important point. While the technology is now in place, the policy describing the details of the certification system has not yet passed the RIPE Policy Development Process. We have decided, however, to launch the system with the most limited feature set possible, so that the membership can try it out. Our hope is that this will make resource certification more tangible, and assist the community in making an informed decision about what the system should offer, now and in the future. I invite and encourage you to discuss this on the RIPE NCC Services Working Group mailing list: http://www.ripe.net/ripe/wg/ncc-services/index.html Ongoing development of the RIPE NCC certification service will, of course, be planned in accordance with the certification policy that is agreed on by the RIPE community. For more information, please visit: http://ripe.net/certification If you have any questions or comments, please email <certification(a)ripe.net >. Best regards, Alex Band Product Manager, RIPE NCC

1 0

RIPE NCC closed on Friday 24 December 2010
by Saskia van Gorp 23 Dec '10

23 Dec '10

Dear Colleagues, Our offices will be closed on Friday 24 December 2010 due to Christmas Eve. Normal office hours will resume on Monday, 27 December 2010. The RIPE NCC wishes you Happy Holidays and all the best for 2011. Regards, Saskia van Gorp Facilities, Administration and Reception Manager RIPE NCC

1 0

RIPE NCC Resource Certification System: Initial Deployment 1 January 2011
by Alex Band 01 Dec '10

01 Dec '10

Dear colleagues, With just seven IPv4 address blocks available in the IANA pool, we are hurtling towards the end of an era. With this prospect, the registry function of the five Regional Internet Registries (RIRs) is going to be crucial to the Internet community. More than ever, it is important to know who is the legitimate holder of a block of IP addresses. With this as a primary driver, the RIPE NCC (in coordination with the other four RIRs) is planning to deploy a system that attaches digital certificates to Internet number resources (IP address blocks and Autonomous System (AS) Numbers). A more complete description of the benefits of resource certification can be found at: http://www.ripe.net/certification/ The RIPE NCC has had a beta platform for certification up and running for several months now. More than 100 RIPE NCC members have enabled certification under this pilot program, providing the RIPE NCC with valuable feedback. On 1 January 2011, the RIPE NCC will launch a hosted production system, which will allow all LIRs to generate a certificate of holdership, which will be held in a repository maintained by the RIPE NCC. Network operators will also be able to start making routing decisions based on the system as of this date. Further iterations of this system will be deployed over the coming 12 months, including the option for LIRs to host their own Certificate Authority and generate certificates for their own customers. Digital certificates have helped make business on the Internet more secure. Now we are using resource certificates to make the Internet itself more secure. For more information, please visit: http://ripe.net/certification If you have any questions or comments, please email <ncc(a)ripe.net>. Best regards, Alex Band Product Manager, RIPE NCC

3 2