From bart.smaalders@sun.com Tue Mar 20 21:06:29 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2L46SYC016335 for ; Tue, 20 Mar 2007 21:06:28 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l2L46Pcs026907 for <@sunmail2sca.sfbay.sun.com:PSARC-EXT@Sun.COM>; Wed, 21 Mar 2007 12:06:27 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF800B01JERAQ00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-EXT@Sun.COM (ORCPT PSARC-EXT@Sun.COM); Tue, 20 Mar 2007 21:06:27 -0700 (PDT) Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF800MQMJEQWKE0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-EXT@Sun.COM (ORCPT PSARC-EXT@Sun.COM); Tue, 20 Mar 2007 21:06:26 -0700 (PDT) Received: from zion.eng.sun.com (zion.SFBay.Sun.COM [129.146.17.75]) by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2L46QIj003496; Tue, 20 Mar 2007 21:06:26 -0700 (PDT) Received: from [129.146.228.109] (cyber [129.146.228.109]) by zion.eng.sun.com (8.13.7+Sun/8.13.7) with ESMTP id l2L46Qbo029509; Tue, 20 Mar 2007 21:06:26 -0700 (PDT) Date: Tue, 20 Mar 2007 21:05:35 -0700 From: Bart Smaalders Subject: PSARC/2007/165 Including CURL with Solaris To: PSARC-EXT@sun.com Cc: Stefan Teleman Message-id: <4600AF0F.40204@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_Xk6yv3cqCauGjLOKcXEQgA)" X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 2.0b2 (X11/20070227) Status: RO Content-Length: 14340 This is a multi-part message in MIME format. --Boundary_(ID_Xk6yv3cqCauGjLOKcXEQgA) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT I'm sponsoring the attached fast-track for Stefan Teleman. The requested binding is patch/micro release, and the stability levels are as noted in the document. Materials are in the case directory. This case times out on 3/28/2007. - Bart -- Bart Smaalders Solaris Kernel Performance barts@cyber.eng.sun.com http://blogs.sun.com/barts --Boundary_(ID_Xk6yv3cqCauGjLOKcXEQgA) Content-type: text/plain; name=CURLFastTrack.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=CURLFastTrack.txt Including CURL with Solaris Stefan Teleman 15 March 2007 1. Summary and motivation The Internet has created the necessity for a standardized syntax format for accessing remote object references. In 1994, IETF published the URI [Uniform Resource Identifier] Specification [RFC 1630] [76], followed by the URN [Uniform Resource Name] Specification [RFC 1737] [77] and the URL [Uniform Resource Locator] Specification [RFC 1738] [16]. Since then, the terms URI, URL and URN have been used interchangeably. While subtle distinctions between URI, URL and URN do exist, these differences have become, in practice, largely academic. This evolution has created the need for programmatic and userland facilities supporting remote object referencing and data transfers, compliant to the specifications outlined above. CURL [http://curl.haxx.se/] [1] provides such a collection of facilities in a portable and platform independent implementation. CURL is known to run on most UNIX platforms, as well as Windows. This FastTrack proposes the integration of CURL in Solaris. CURL is Open Source Software, and is developed and maintained outside of SMI. As such, the SFW Consolidation is the natural choice for Solaris integration. This case proposes the most recent stable release of CURL, 7.16.1. CURL stands for 'C-URL' [where 'C' refers to the C Programming Language]. For the purposes of this document, the terms CURL and LibCURL are semantically equivalent. The 'curl' executable is a wrapper around the LibCURL library [libcurl.so.3.0.0], and implements a command-line interface to the facilities provided by LibCURL. This case seeks Micro/Patch Release Binding. 2. Technical issues 2.1. Key objects /usr/bin/curl /usr/bin/curl-config /usr/lib/libcurl.so.3.0.0 /usr/lib/libcurl.so.3 -> /usr/lib/libcurl.so.3.0.0 /usr/lib/libcurl.so -> /usr/lib/libcurl.so.3.0.0 /usr/include/curl/curl.h /usr/include/curl/curlver.h /usr/include/curl/easy.h /usr/include/curl/mprintf.h /usr/include/curl/multi.h /usr/include/curl/stdcheaders.h /usr/include/curl/types.h /usr/share/man/man1/curl.1 /usr/share/man/man1/curl-config.1 /usr/share/man/man3/libcurl.3 /usr/share/man/man3/curl_easy_cleanup.3 /usr/share/man/man3/curl_easy_duphandle.3 /usr/share/man/man3/curl_easy_escape.3 /usr/share/man/man3/curl_easy_getinfo.3 /usr/share/man/man3/curl_easy_init.3 /usr/share/man/man3/curl_easy_perform.3 /usr/share/man/man3/curl_easy_reset.3 /usr/share/man/man3/curl_easy_setopt.3 /usr/share/man/man3/curl_easy_strerror.3 /usr/share/man/man3/curl_easy_unescape.3 /usr/share/man/man3/curl_escape.3 /usr/share/man/man3/curl_formadd.3 /usr/share/man/man3/curl_formfree.3 /usr/share/man/man3/curl_formget.3 /usr/share/man/man3/curl_free.3 /usr/share/man/man3/curl_getdate.3 /usr/share/man/man3/curl_getenv.3 /usr/share/man/man3/curl_global_cleanup.3 /usr/share/man/man3/curl_global_init.3 /usr/share/man/man3/curl_global_init_mem.3 /usr/share/man/man3/curl_mprintf.3 /usr/share/man/man3/curl_multi_add_handle.3 /usr/share/man/man3/curl_multi_assign.3 /usr/share/man/man3/curl_multi_cleanup.3 /usr/share/man/man3/curl_multi_fdset.3 /usr/share/man/man3/curl_multi_info_read.3 /usr/share/man/man3/curl_multi_init.3 /usr/share/man/man3/curl_multi_perform.3 /usr/share/man/man3/curl_multi_remove_handle.3 /usr/share/man/man3/curl_multi_setopt.3 /usr/share/man/man3/curl_multi_socket.3 /usr/share/man/man3/curl_multi_strerror.3 /usr/share/man/man3/curl_multi_timeout.3 /usr/share/man/man3/curl_share_cleanup.3 /usr/share/man/man3/curl_share_init.3 /usr/share/man/man3/curl_share_setopt.3 /usr/share/man/man3/curl_share_strerror.3 /usr/share/man/man3/curl_slist_append.3 /usr/share/man/man3/curl_slist_free_all.3 /usr/share/man/man3/curl_strequal.3 /usr/share/man/man3/curl_unescape.3 /usr/share/man/man3/curl_version.3 /usr/share/man/man3/curl_version_info.3 /usr/share/man/man3/libcurl-easy.3 /usr/share/man/man3/libcurl-errors.3 /usr/share/man/man3/libcurl-multi.3 /usr/share/man/man3/libcurl-share.3 /usr/share/man/man3/libcurl-tutorial.3 /usr/share/doc/curl/index.html /usr/share/doc/curl/curl.html /usr/share/doc/curl/curl-config.html LibCURL's functionality is provided by one executable [curl], and one shared library [libcurl.so.3.0.0]. LibCURL implements a very large number of Internet-related protocols, authentication mechanisms, and data transfer facilities. Key aspects of the specifications implemented, and facilities provided, by, LibCURL are listed below. CURL is largefile aware and is 64-bit clean. CURL is not thread-safe, and its functions are not reentrant. Calls to public functions within the LibCURL library, from different threads, must be serialized. The private LibCURL interfaces use static data structures [for internal consumption only]. 2.2. Specifications LibCURL implements the following Specifications: NAME DESCRIPTION NOTES RFC 0822 Standard for ARPA Internet Text Messages [8] RFC 0850 Standard for Interchange of USENET Messages [9] RFC 0959 File Transfer Protocol [FTP] [10] RFC 1036 Standard for Interchange of USENET Messages [11] RFC 1123 Requirements for Internet Hosts -- Application and Support [12] RFC 1350 Trivial File Transfer Protocol [TFTP] [13] RFC 1635 Anonymous FTP [14] RFC 1639 FTP Operation Over Big Address Records [FOOBAR] [15] RFC 1738 Uniform Resource Locators [URL] [16] RFC 1777 Lightweight Directory Access Protocol [LDAP] [17] RFC 1808 Relative Uniform Resource Locators [18] RFC 1867 Form-based File Upload in HTML [19] RFC 1884 IPv6 [20] RFC 1928 SOCKS Protocol [21] RFC 1945 HTTP/1.0 [22] RFC 1950 Z-LIB [23] RFC 1951 DEFLATE [24] RFC 1952 GZip [25] RFC 1959 LDAP URL RFC 2045 MIME Part 1: Format of Internet Message Bodies [26] RFC 2046 MIME Part 2: Media Types [27] RFC 2047 MIME Part 3: Message Header Extensions for Non-ASCII Text [28] RFC 2048 MIME Part 4: Registration Procedures [29] RFC 2049 MIME Part 5: Conformance Criteria and Examples [30] RFC 2068 HTTP/1.1 [31] RFC 2109 HTTP Session and State Management [32] RFC 2133 IPv6 Sockets [33] RFC 2183 Content-Disposition Header [34] RFC 2184 MIME Parameter Value and Encoded Word Extensions [35] RFC 2228 FTP Security Extensions [36] RFC 2229 Dictionary Server Protocol [37] RFC 2231 MIME Parameter Value and Encoded Word Extensions [38] RFC 2246 TLS Protocol 1.0 [39] RFC 2255 New LDAP URL [40] RFC 2326 Real Time Streaming Protocol [RTSP] [41] RFC 2373 IP Version 6 Addressing Architecture [42] RFC 2388 Returning Values from Forms: multipart/form-data [43] RFC 2389 Feature negotiation mechanism for the File Transfer Protocol [44] RFC 2396 Uniform Resource Identifiers [URI]: Generic Syntax [45] RFC 2428 FTP Extensions for IPv6 and NATs [46] RFC 2459 Internet X.509 Public Key Infrastructure: Certificate and CRL Profile [47] RFC 2518 HTTP Extensions for Distributed Authoring: WebDAV [48] RFC 2553 Basic Socket Interface Extensions for IPv6 [49] RFC 2577 FTP Security Considerations [50] RFC 2616 HTTP/1.1 [Obsoletes RFC 2068] [51] RFC 2617 HTTP Authentication: Basic and Digest Access Authentication [52] RFC 2640 Internationalization of the File Transfer Protocol [53] RFC 2718 Guidelines for new URL Schemes [54] RFC 2732 Format for Literal IPv6 Addresses in URL's [55] RFC 2817 Upgrading to TLS Within HTTP/1.1 [56] RFC 2818 HTTP Over TLS [57] RFC 2854 The 'text/html' Media Type [58] RFC 2936 HTTP MIME Type Handler Detection [59] RFC 2964 Use of HTTP State Management [60] RFC 2965 HTTP State Management Mechanism [61] RFC 3280 Internet X.509 Public Key Infrastructure [62] RFC 3493 Basic Socket Interface Extensions for IPv6 [63] RFC 3513 Internet Protocol Version 6 [IPv6] Addressing Architecture [64] RFC 3617 Uniform Resource Identifier [URI] Scheme and Applicability Statement for TFTP [65] RFC 3986 Uniform Resource Identifier [URI]: Generic Syntax [66] RFC 4217 Securing FTP with TLS [67] RFC 4248 The telnet URI Scheme [68] RFC 4346 The Transport Layer Security [TLS] Protocol Version 1.1 [69] RFC 4366 Transport Layer Security [TLS] Extensions [70] Cookie Spec Persistent Client State - HTTP Cookies [71] Draft SPNEGO HTTP Authentication: SPNEGO Access Authentication As implemented in Microsoft Windows 2000 [72] Draft SecSH/SCP/SFTP/SSH/URI-04 Uniform Resource Identifier [URI] Scheme for Secure File Transfer Protocol [SFTP] and Secure Shell [SSH] [73] Draft Web Proxy TCP Tunneling Tunneling TCP based protocols through Web proxy servers [74] NTLM The NTLM Authentication Protocol [75] 2.3. Language bindings CURL is written in C. No other language bindings are provided by the canonical distribution. 2.4. Documentation CURL provides an extensive and complete documentation set in UNIX manual format, as well as HTML. We propose that the full documentation set be included with the Solaris integration. 3. Interfaces 3.1. Interface Stability CURL is an Open Source project, and its design, development and release schedule are external to SMI. CURL makes no implicit or explicit promises or guarantees of API or ABI compatibility between releases. 3.2. Imported interfaces In addition to the Standard C Library and Network Services Library Interfaces, CURL depends on, and imports interfaces, from: NAME STABILITY NOTES OpenSSL External/Volatile PSARC/2003/500 [2] Z-Lib Committed PSARC/2006/537 [3] LDAP [OpenLDAP] Evolving PSARC/1997/276 [4] Kerberos [MIT] External PSARC/1999/617 et seq. [5] LibIDN Uncommitted PSARC/2007/000 [6] GNU TLS Volatile PSARC/2002/621 [7] The LDAP, Kerberos and GNU TLS bindings are optional. The OpenSSL, Z-Lib and LibIDN bindings are mandatory. 3.3. Exported interfaces NAME STABILITY NOTES SUNWcurl Uncommitted Package name /usr/bin/curl Uncommitted Executable location /usr/bin/curl-config Uncommitted Shell script location /usr/lib/libcurl.so.3.0.0 Uncommitted Library location /usr/lib/libcurl.so.3 Uncommitted Symbolic link /usr/lib/libcurl.so Uncommitted Symbolic link /usr/include/curl/ Uncommitted Include files 4. References [1] http://curl.haxx.se/ [2] http://www.openssl.org/ [3] http://www.gzip.org/zlib/ [4] http://www.openldap.org/ [5] http://web.mit.edu/kerberos/dist/index.html [6] http://www.gnu.org/software/libidn/ [7] http://www.gnu.org/software/gnutls/ [8] http://www.ietf.org/rfc/rfc0822.txt [9] http://www.ietf.org/rfc/rfc0850.txt [10] http://www.ietf.org/rfc/rfc0959.txt [11] http://www.ietf.org/rfc/rfc1036.txt [12] http://www.ietf.org/rfc/rfc1123.txt [13] http://www.ietf.org/rfc/rfc1350.txt [14] http://www.ietf.org/rfc/rfc1635.txt [15] http://www.ietf.org/rfc/rfc1639.txt [16] http://www.ietf.org/rfc/rfc1738.txt [17] http://www.ietf.org/rfc/rfc1777.txt [18] http://www.ietf.org/rfc/rfc1808.txt [19] http://www.ietf.org/rfc/rfc1867.txt [20] http://www.ietf.org/rfc/rfc1884.txt [21] http://www.ietf.org/rfc/rfc1928.txt [22] http://www.ietf.org/rfc/rfc1945.txt [23] http://www.ietf.org/rfc/rfc1945.txt [24] http://www.ietf.org/rfc/rfc1951.txt [25] http://www.ietf.org/rfc/rfc1952.txt [26] http://www.ietf.org/rfc/rfc1959.txt [27] http://www.ietf.org/rfc/rfc2045.txt [28] http://www.ietf.org/rfc/rfc2046.txt [29] http://www.ietf.org/rfc/rfc2047.txt [30] http://www.ietf.org/rfc/rfc2048.txt [31] http://www.ietf.org/rfc/rfc2049.txt [32] http://www.ietf.org/rfc/rfc2068.txt [33] http://www.ietf.org/rfc/rfc2109.txt [34] http://www.ietf.org/rfc/rfc2133.txt [35] http://www.ietf.org/rfc/rfc2183.txt [36] http://www.ietf.org/rfc/rfc2184.txt [37] http://www.ietf.org/rfc/rfc2228.txt [38] http://www.ietf.org/rfc/rfc2229.txt [39] http://www.ietf.org/rfc/rfc2231.txt [40] http://www.ietf.org/rfc/rfc2246.txt [41] http://www.ietf.org/rfc/rfc2255.txt [41] http://www.ietf.org/rfc/rfc2326.txt [42] http://www.ietf.org/rfc/rfc2373.txt [43] http://www.ietf.org/rfc/rfc2388.txt [44] http://www.ietf.org/rfc/rfc2389.txt [45] http://www.ietf.org/rfc/rfc2396.txt [46] http://www.ietf.org/rfc/rfc2428.txt [47] http://www.ietf.org/rfc/rfc2459.txt [48] http://www.ietf.org/rfc/rfc2518.txt [49] http://www.ietf.org/rfc/rfc2553.txt [50] http://www.ietf.org/rfc/rfc2577.txt [51] http://www.ietf.org/rfc/rfc2616.txt [52] http://www.ietf.org/rfc/rfc2617.txt [53] http://www.ietf.org/rfc/rfc2640.txt [54] http://www.ietf.org/rfc/rfc2718.txt [55] http://www.ietf.org/rfc/rfc2732.txt [56] http://www.ietf.org/rfc/rfc2817.txt [57] http://www.ietf.org/rfc/rfc2818.txt [58] http://www.ietf.org/rfc/rfc2854.txt [59] http://www.ietf.org/rfc/rfc2936.txt [60] http://www.ietf.org/rfc/rfc2964.txt [61] http://www.ietf.org/rfc/rfc2965.txt [62] http://www.ietf.org/rfc/rfc3280.txt [63] http://www.ietf.org/rfc/rfc3493.txt [64] http://www.ietf.org/rfc/rfc3513.txt [65] http://www.ietf.org/rfc/rfc3617.txt [66] http://www.ietf.org/rfc/rfc3986.txt [67] http://www.ietf.org/rfc/rfc4217.txt [68] http://www.ietf.org/rfc/rfc4248.txt [69] http://www.ietf.org/rfc/rfc4346.txt [70] http://www.ietf.org/rfc/rfc4366.txt [71] http://curl.haxx.se/rfc/cookie_spec.html [72] http://curl.haxx.se/rfc/draft-brezak-spnego-http-04.txt [73] http://curl.haxx.se/rfc/draft-ietf-secsh-scp-sftp-ssh-uri-04.txt [74] http://curl.haxx.se/rfc/draft-luotonen-web-proxy-tunneling-01.txt [75] http://curl.haxx.se/rfc/ntlm.html [76] http://tools.ietf.org/html/rfc1630 [77] http://www.ietf.org/rfc/rfc1737.txt --Boundary_(ID_Xk6yv3cqCauGjLOKcXEQgA)-- From carlsonj@phorcys.east.sun.com Wed Mar 21 06:48:41 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LDmecV024729 for ; Wed, 21 Mar 2007 06:48:40 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LDmVja013292; Wed, 21 Mar 2007 13:48:38 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900L03ACZP000@brm-avmta-1.central.sun.com>; Wed, 21 Mar 2007 07:48:35 -0600 (MDT) Received: from phorcys.east.sun.com ([129.148.174.143]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900JXQACYSK20@brm-avmta-1.central.sun.com>; Wed, 21 Mar 2007 07:48:34 -0600 (MDT) Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.0+Sun/8.14.0) with ESMTP id l2LDmYQV009087; Wed, 21 Mar 2007 09:48:34 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.0+Sun/8.14.0/Submit) id l2LDmYVM009084; Wed, 21 Mar 2007 09:48:34 -0400 (EDT) Date: Wed, 21 Mar 2007 09:48:33 -0400 From: James Carlson Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <4600AF0F.40204@Sun.COM> To: Bart Smaalders Cc: PSARC-EXT@sun.com, Stefan Teleman Message-id: <17921.14257.920536.504061@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <4600AF0F.40204@Sun.COM> Status: RO Content-Length: 798 Bart Smaalders writes: > This FastTrack proposes the integration of CURL in Solaris. > CURL is Open Source Software, and is developed and maintained > outside of SMI. As such, the SFW Consolidation is the natural choice > for Solaris integration. Does this mean that we can now get rid of the $SRC/common/net/wanboot/ stuff (and its bugs)? I think making a higher commitment to CURL would be of benefit to Solaris, given how pervasive the need for URL handling is. > LibIDN Uncommitted PSARC/2007/000 [6] That might be 2007/167, on which this case depends. ;-} -- James Carlson, Solaris Networking Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From unixconsole@yahoo.com Wed Mar 21 06:55:42 2007 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LDtgkV025226 for ; Wed, 21 Mar 2007 06:55:42 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LDtbVP048434 for <@sunmail1brm.central.sun.com:PSARC-EXT@sun.com>; Wed, 21 Mar 2007 07:55:38 -0600 (MDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900L09AOPWC00@brm-avmta-1.central.sun.com> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Wed, 21 Mar 2007 07:55:37 -0600 (MDT) Received: from sca-ea-mail-1.sun.com ([192.18.43.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900JM7AOPSH30@brm-avmta-1.central.sun.com> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Wed, 21 Mar 2007 07:55:37 -0600 (MDT) Received: from relay42i.sun.com ([192.5.209.72]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l2LDoC9U018047 for ; Wed, 21 Mar 2007 13:55:36 +0000 (GMT) Received: from mms48es.sun.com ([160.41.221.231] [160.41.221.231]) by relay42i.sun.com with ESMTP for PSARC-EXT@sun.com; Wed, 21 Mar 2007 13:55:36 +0000 (Z) Received: from relay41i.sun.com ([192.5.209.70] [192.5.209.70]) by mms48es.sun.com with ESMTP for PSARC-EXT@sun.com; Wed, 21 Mar 2007 13:55:36 +0000 (Z) Received: from web30805.mail.mud.yahoo.com ([68.142.200.148] [68.142.200.148]) by relay4i.sun.com for PSARC-EXT@sun.com; Wed, 21 Mar 2007 13:55:35 +0000 (Z) Received: (qmail 38593 invoked by uid 60001); Wed, 21 Mar 2007 13:55:35 +0000 Received: from [71.2.179.191] by web30805.mail.mud.yahoo.com via HTTP; Wed, 21 Mar 2007 06:55:35 -0700 (PDT) Date: Wed, 21 Mar 2007 06:55:35 -0700 (PDT) From: Octave Orgeron Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <4600AF0F.40204@Sun.COM> To: Bart Smaalders , PSARC-EXT@sun.com Cc: Stefan Teleman Message-id: <458064.38586.qm@web30805.mail.mud.yahoo.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=CLsLfGzD5wyp5CAMwyHSuyu5k5AvztkHbV0/tfxM/Qc/+hTAF9o/bx/wVSz3ILRZSBPMz3RJwrll4b3klhjCcMZ1ot/EVY9I49RrhAE+4CWTiLICWjrGbOB9ZWwsY/MzeUt8Vd6edGZ8lN0UmaiG6/atQZszWzTxNbrakDJvSv4=; X-PMX-Version: 5.2.0.264296 X-YMail-OSG: tbRNHcsVM1nVHWln2iUyrQ_glL9COmt26_kH9TuYBcODFHLz21x1e6uCe7edLPiJZaISuYYC6SgYCl3Nv8o1ar95KlUecgrhkwfUiHHKWGm3wy.y8Om0Dng6LciCKalo_gZPPtnnQWsWpWmFy70loVwnd65rk8IAK8pKgRK6yAX6Z6S_4J4AXfqKEg-- Status: RO Content-Length: 9734 Hi, Looks good. In the section that shows its dependencies, I had a question. Are we going to include LDAP, Kerberos, etc support or just the minimum support? If the components are in the OS, I think we should enable the features. Otherwise, we'll be giving customers a reason to go an compile their own version, which I think we are trying to avoid. Octave --- Bart Smaalders wrote: > I'm sponsoring the attached fast-track for Stefan Teleman. > The requested binding is patch/micro release, and the > stability levels are as noted in the document. > > Materials are in the case directory. > > This case times out on 3/28/2007. > > - Bart > > -- > Bart Smaalders Solaris Kernel Performance > barts@cyber.eng.sun.com http://blogs.sun.com/barts > > Including CURL with Solaris > > Stefan Teleman > 15 March 2007 > > 1. Summary and motivation > > The Internet has created the necessity for a standardized > syntax format for accessing remote object references. In 1994, > IETF published the URI [Uniform Resource Identifier] Specification > [RFC 1630] [76], followed by the URN [Uniform Resource Name] > Specification [RFC 1737] [77] and the URL [Uniform Resource Locator] > Specification [RFC 1738] [16]. Since then, the terms URI, URL and > URN have been used interchangeably. While subtle distinctions > between URI, URL and URN do exist, these differences have become, > in practice, largely academic. > > This evolution has created the need for programmatic and userland > facilities supporting remote object referencing and data transfers, > compliant to the specifications outlined above. > > CURL [http://curl.haxx.se/] [1] provides such a collection of > facilities in a portable and platform independent implementation. > CURL is known to run on most UNIX platforms, as well as Windows. > > This FastTrack proposes the integration of CURL in Solaris. > CURL is Open Source Software, and is developed and maintained > outside of SMI. As such, the SFW Consolidation is the natural choice > for Solaris integration. > > This case proposes the most recent stable release of CURL, 7.16.1. > > CURL stands for 'C-URL' [where 'C' refers to the C Programming > Language]. For the purposes of this document, the terms CURL and > LibCURL are semantically equivalent. The 'curl' executable is a > wrapper around the LibCURL library [libcurl.so.3.0.0], and > implements > a command-line interface to the facilities provided by LibCURL. > > This case seeks Micro/Patch Release Binding. > > 2. Technical issues > > 2.1. Key objects > > /usr/bin/curl > /usr/bin/curl-config > > /usr/lib/libcurl.so.3.0.0 > /usr/lib/libcurl.so.3 -> /usr/lib/libcurl.so.3.0.0 > /usr/lib/libcurl.so -> /usr/lib/libcurl.so.3.0.0 > > /usr/include/curl/curl.h > /usr/include/curl/curlver.h > /usr/include/curl/easy.h > /usr/include/curl/mprintf.h > /usr/include/curl/multi.h > /usr/include/curl/stdcheaders.h > /usr/include/curl/types.h > > /usr/share/man/man1/curl.1 > /usr/share/man/man1/curl-config.1 > > /usr/share/man/man3/libcurl.3 > /usr/share/man/man3/curl_easy_cleanup.3 > /usr/share/man/man3/curl_easy_duphandle.3 > /usr/share/man/man3/curl_easy_escape.3 > /usr/share/man/man3/curl_easy_getinfo.3 > /usr/share/man/man3/curl_easy_init.3 > /usr/share/man/man3/curl_easy_perform.3 > /usr/share/man/man3/curl_easy_reset.3 > /usr/share/man/man3/curl_easy_setopt.3 > /usr/share/man/man3/curl_easy_strerror.3 > /usr/share/man/man3/curl_easy_unescape.3 > /usr/share/man/man3/curl_escape.3 > /usr/share/man/man3/curl_formadd.3 > /usr/share/man/man3/curl_formfree.3 > /usr/share/man/man3/curl_formget.3 > /usr/share/man/man3/curl_free.3 > /usr/share/man/man3/curl_getdate.3 > /usr/share/man/man3/curl_getenv.3 > /usr/share/man/man3/curl_global_cleanup.3 > /usr/share/man/man3/curl_global_init.3 > /usr/share/man/man3/curl_global_init_mem.3 > /usr/share/man/man3/curl_mprintf.3 > /usr/share/man/man3/curl_multi_add_handle.3 > /usr/share/man/man3/curl_multi_assign.3 > /usr/share/man/man3/curl_multi_cleanup.3 > /usr/share/man/man3/curl_multi_fdset.3 > /usr/share/man/man3/curl_multi_info_read.3 > /usr/share/man/man3/curl_multi_init.3 > /usr/share/man/man3/curl_multi_perform.3 > /usr/share/man/man3/curl_multi_remove_handle.3 > /usr/share/man/man3/curl_multi_setopt.3 > /usr/share/man/man3/curl_multi_socket.3 > /usr/share/man/man3/curl_multi_strerror.3 > /usr/share/man/man3/curl_multi_timeout.3 > /usr/share/man/man3/curl_share_cleanup.3 > /usr/share/man/man3/curl_share_init.3 > /usr/share/man/man3/curl_share_setopt.3 > /usr/share/man/man3/curl_share_strerror.3 > /usr/share/man/man3/curl_slist_append.3 > /usr/share/man/man3/curl_slist_free_all.3 > /usr/share/man/man3/curl_strequal.3 > /usr/share/man/man3/curl_unescape.3 > /usr/share/man/man3/curl_version.3 > /usr/share/man/man3/curl_version_info.3 > /usr/share/man/man3/libcurl-easy.3 > /usr/share/man/man3/libcurl-errors.3 > /usr/share/man/man3/libcurl-multi.3 > /usr/share/man/man3/libcurl-share.3 > /usr/share/man/man3/libcurl-tutorial.3 > > /usr/share/doc/curl/index.html > /usr/share/doc/curl/curl.html > /usr/share/doc/curl/curl-config.html > > LibCURL's functionality is provided by one executable [curl], and > one shared library [libcurl.so.3.0.0]. LibCURL implements a very > large number of Internet-related protocols, authentication > mechanisms, > and data transfer facilities. Key aspects of the specifications > implemented, and facilities provided, by, LibCURL are listed below. > > CURL is largefile aware and is 64-bit clean. CURL is not > thread-safe, > and its functions are not reentrant. Calls to public functions > within > the LibCURL library, from different threads, must be serialized. The > private LibCURL interfaces use static data structures [for internal > consumption only]. > > 2.2. Specifications > > LibCURL implements the following Specifications: > > NAME DESCRIPTION NOTES > > RFC 0822 Standard for ARPA Internet Text Messages [8] > RFC 0850 Standard for Interchange of USENET Messages [9] > RFC 0959 File Transfer Protocol [FTP] [10] > RFC 1036 Standard for Interchange of USENET Messages [11] > RFC 1123 Requirements for Internet Hosts -- Application and Support > [12] > RFC 1350 Trivial File Transfer Protocol [TFTP] [13] > RFC 1635 Anonymous FTP [14] > RFC 1639 FTP Operation Over Big Address Records [FOOBAR] [15] > RFC 1738 Uniform Resource Locators [URL] [16] > RFC 1777 Lightweight Directory Access Protocol [LDAP] [17] > RFC 1808 Relative Uniform Resource Locators [18] > RFC 1867 Form-based File Upload in HTML [19] > RFC 1884 IPv6 [20] > RFC 1928 SOCKS Protocol [21] > RFC 1945 HTTP/1.0 [22] > RFC 1950 Z-LIB [23] > RFC 1951 DEFLATE [24] > RFC 1952 GZip [25] > RFC 1959 LDAP URL > RFC 2045 MIME Part 1: Format of Internet Message Bodies [26] > RFC 2046 MIME Part 2: Media Types [27] > RFC 2047 MIME Part 3: Message Header Extensions for Non-ASCII Text > [28] > RFC 2048 MIME Part 4: Registration Procedures [29] > RFC 2049 MIME Part 5: Conformance Criteria and Examples [30] > RFC 2068 HTTP/1.1 [31] > RFC 2109 HTTP Session and State Management [32] > RFC 2133 IPv6 Sockets [33] > RFC 2183 Content-Disposition Header [34] > RFC 2184 MIME Parameter Value and Encoded Word Extensions [35] > RFC 2228 FTP Security Extensions [36] > RFC 2229 Dictionary Server Protocol [37] > RFC 2231 MIME Parameter Value and Encoded Word Extensions [38] > RFC 2246 TLS Protocol 1.0 [39] > RFC 2255 New LDAP URL [40] > RFC 2326 Real Time Streaming Protocol [RTSP] [41] > RFC 2373 IP Version 6 Addressing Architecture [42] > RFC 2388 Returning Values from Forms: multipart/form-data [43] > RFC 2389 Feature negotiation mechanism for the File Transfer > Protocol [44] > RFC 2396 Uniform Resource Identifiers [URI]: Generic Syntax [45] > RFC 2428 FTP Extensions for IPv6 and NATs [46] > RFC 2459 Internet X.509 Public Key Infrastructure: Certificate and > CRL Profile [47] > RFC 2518 HTTP Extensions for Distributed Authoring: WebDAV [48] > RFC 2553 Basic Socket Interface Extensions for IPv6 [49] > RFC 2577 FTP Security Considerations [50] > RFC 2616 HTTP/1.1 [Obsoletes RFC 2068] [51] > RFC 2617 HTTP Authentication: Basic and Digest Access Authentication > [52] > RFC 2640 Internationalization of the File Transfer Protocol [53] > RFC 2718 Guidelines for new URL Schemes [54] > RFC 2732 Format for Literal IPv6 Addresses in URL's [55] > RFC 2817 Upgrading to TLS Within HTTP/1.1 [56] > RFC 2818 HTTP Over TLS [57] > RFC 2854 The 'text/html' Media Type [58] > RFC 2936 HTTP MIME Type Handler Detection [59] > RFC 2964 Use of HTTP State Management [60] > RFC 2965 HTTP State Management Mechanism [61] > RFC 3280 Internet X.509 Public Key Infrastructure [62] > RFC 3493 Basic Socket Interface Extensions for IPv6 [63] > RFC 3513 Internet Protocol Version 6 [IPv6] Addressing Architecture > [64] > === message truncated ===> _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc@opensolaris.org *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Octave J. Orgeron Solaris Systems Engineer http://www.opensolaris.org/os/community/sysadmin/ http://unixconsole.blogspot.com unixconsole@yahoo.com *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* ____________________________________________________________________________________ Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html From Mark.Phalan@Sun.COM Wed Mar 21 06:56:29 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LDuSrr025332 for ; Wed, 21 Mar 2007 06:56:28 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l2LDuArn028066; Wed, 21 Mar 2007 21:56:25 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900G0YAPXKG00@nwk-avmta-2.sfbay.sun.com>; Wed, 21 Mar 2007 06:56:21 -0700 (PDT) Received: from gmp-ea-fw-1.sun.com ([129.156.42.5]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900CD2APWFG70@nwk-avmta-2.sfbay.sun.com>; Wed, 21 Mar 2007 06:56:21 -0700 (PDT) Received: from d1-emea-10.sun.com (d1-emea-10.sun.com [192.18.2.120]) by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l2LDuJea017852; Wed, 21 Mar 2007 13:56:20 +0000 (GMT) Received: from conversion-daemon.d1-emea-10.sun.com by d1-emea-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JF900401AKTIX00@d1-emea-10.sun.com> (original mail from Mark.Phalan@Sun.COM); Wed, 21 Mar 2007 13:56:19 +0000 (GMT) Received: from [130.129.23.212] by d1-emea-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JF900LAYAPTI9OB@d1-emea-10.sun.com>; Wed, 21 Mar 2007 13:56:17 +0000 (GMT) Date: Wed, 21 Mar 2007 14:55:46 +0100 From: Mark Phalan Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <4600AF0F.40204@Sun.COM> Sender: Mark.Phalan@Sun.COM To: Bart Smaalders Cc: PSARC-EXT@Sun.COM, Stefan Teleman Message-id: <1174485346.966.11.camel@unknown> MIME-version: 1.0 X-Mailer: Evolution 2.8.1.1 Content-type: text/plain Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <4600AF0F.40204@Sun.COM> Status: RO Content-Length: 702 On Tue, 2007-03-20 at 21:05 -0700, Bart Smaalders wrote: > > In addition to the Standard C Library and Network Services Library > Interfaces, CURL depends on, and imports interfaces, from: > > NAME STABILITY NOTES > > OpenSSL External/Volatile PSARC/2003/500 [2] > Z-Lib Committed PSARC/2006/537 [3] > LDAP [OpenLDAP] Evolving PSARC/1997/276 [4] > Kerberos [MIT] External PSARC/1999/617 et seq. [5] > LibIDN Uncommitted PSARC/2007/000 [6] > GNU TLS Volatile PSARC/2002/621 [7] > > The LDAP, Kerberos and GNU TLS bindings are optional. The OpenSSL, > Z-Lib and LibIDN bindings are mandatory. > Will CURL be linked against our libgss/libkrb5 when delivered? -Mark From Stefan.Teleman@Sun.COM Wed Mar 21 07:50:25 2007 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LEoPU7025873 for ; Wed, 21 Mar 2007 07:50:25 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LEoE9H027275; Wed, 21 Mar 2007 07:50:23 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF90000FD7YF600@brm-avmta-1.central.sun.com>; Wed, 21 Mar 2007 08:50:22 -0600 (MDT) Received: from jurassic.eng.sun.com ([129.146.104.45]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900JXFD7YSD50@brm-avmta-1.central.sun.com>; Wed, 21 Mar 2007 08:50:22 -0600 (MDT) Received: from [192.9.61.55] (punchin-client-192-9-61-55.SFBay.Sun.COM [192.9.61.55]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l2LEoIEH340306; Wed, 21 Mar 2007 07:50:18 -0700 (PDT) Date: Wed, 21 Mar 2007 10:49:26 -0400 From: Stefan Teleman Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <1174485346.966.11.camel@unknown> To: Mark Phalan Cc: Bart Smaalders , PSARC-EXT@Sun.COM Reply-to: Stefan Teleman Message-id: <460145F6.2080607@Sun.COM> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <4600AF0F.40204@Sun.COM> <1174485346.966.11.camel@unknown> User-Agent: Thunderbird 1.5.0.7 (X11/20060915) Status: RO Content-Length: 930 Mark Phalan wrote: > On Tue, 2007-03-20 at 21:05 -0700, Bart Smaalders wrote: >> In addition to the Standard C Library and Network Services Library >> Interfaces, CURL depends on, and imports interfaces, from: >> >> NAME STABILITY NOTES >> >> OpenSSL External/Volatile PSARC/2003/500 [2] >> Z-Lib Committed PSARC/2006/537 [3] >> LDAP [OpenLDAP] Evolving PSARC/1997/276 [4] >> Kerberos [MIT] External PSARC/1999/617 et seq. [5] >> LibIDN Uncommitted PSARC/2007/000 [6] >> GNU TLS Volatile PSARC/2002/621 [7] >> >> The LDAP, Kerberos and GNU TLS bindings are optional. The OpenSSL, >> Z-Lib and LibIDN bindings are mandatory. >> > > Will CURL be linked against our libgss/libkrb5 when delivered? Yes, the plan is to patch CURL when it can link against our libgss/libkrb5. CURL assumes MIT Kerberos 5 API and nothing else. --Stefan -- Stefan Teleman Sun Microsystems, Inc. Stefan.Teleman@Sun.COM From Stefan.Teleman@sun.com Wed Mar 21 07:53:57 2007 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LErvE2026114 for ; Wed, 21 Mar 2007 07:53:57 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LErtv7028454; Wed, 21 Mar 2007 07:53:56 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900I19DDWUD00@nwk-avmta-2.sfbay.sun.com>; Wed, 21 Mar 2007 07:53:56 -0700 (PDT) Received: from jurassic.eng.sun.com ([129.146.17.57]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900C1ODDVFDB0@nwk-avmta-2.sfbay.sun.com>; Wed, 21 Mar 2007 07:53:55 -0700 (PDT) Received: from [192.9.61.55] (punchin-client-192-9-61-55.SFBay.Sun.COM [192.9.61.55]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l2LErrtB340589; Wed, 21 Mar 2007 07:53:54 -0700 (PDT) Date: Wed, 21 Mar 2007 10:53:01 -0400 From: Stefan Teleman Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <458064.38586.qm@web30805.mail.mud.yahoo.com> To: Octave Orgeron Cc: Bart Smaalders , PSARC-EXT@sun.com Reply-to: Stefan Teleman Message-id: <460146CD.90306@Sun.COM> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <458064.38586.qm@web30805.mail.mud.yahoo.com> User-Agent: Thunderbird 1.5.0.7 (X11/20060915) Status: RO Content-Length: 849 Octave Orgeron wrote: > Hi, > > Looks good. In the section that shows its dependencies, I had a > question. Are we going to include LDAP, Kerberos, etc support or just > the minimum support? If the components are in the OS, I think we should > enable the features. Otherwise, we'll be giving customers a reason to > go an compile their own version, which I think we are trying to avoid. > > Octave The plan definitely includes LDAP and Kerberos bindings. The problem is that CURL assumes the OpenLDAP and MIT Kerberos 5 API's and refuses anything else (modulo some patching which will not be accepted upstream). I know that the Kerberos 5 team is working on the MIT API Compatibility Layer, and that it will become available in Nevada. I don't yet know about LDAP. --Stefan -- Stefan Teleman Sun Microsystems, Inc. Stefan.Teleman@Sun.COM From Mark.Phalan@sun.com Wed Mar 21 08:09:48 2007 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LF9mff027202 for ; Wed, 21 Mar 2007 08:09:48 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LF9kUO001079; Wed, 21 Mar 2007 09:09:47 -0600 (MDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF90000VE48WY00@brm-avmta-1.central.sun.com>; Wed, 21 Mar 2007 09:09:44 -0600 (MDT) Received: from gmp-ea-fw-1.sun.com ([129.156.42.6]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900JZRE46SH80@brm-avmta-1.central.sun.com>; Wed, 21 Mar 2007 09:09:44 -0600 (MDT) Received: from d1-emea-09.sun.com ([192.18.2.119]) by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l2LF9fBO000240; Wed, 21 Mar 2007 15:09:42 +0000 (GMT) Received: from conversion-daemon.d1-emea-09.sun.com by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JF900401DZT7S00@d1-emea-09.sun.com> (original mail from Mark.Phalan@Sun.COM); Wed, 21 Mar 2007 15:09:42 +0000 (GMT) Received: from [129.150.120.216] by d1-emea-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JF900HONE4317BT@d1-emea-09.sun.com>; Wed, 21 Mar 2007 15:09:41 +0000 (GMT) Date: Wed, 21 Mar 2007 16:09:07 +0100 From: Mark Phalan Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <460146CD.90306@Sun.COM> Sender: Mark.Phalan@sun.com To: Stefan Teleman Cc: Octave Orgeron , Bart Smaalders , PSARC-EXT@sun.com Message-id: <1174489748.964.2.camel@unknown> MIME-version: 1.0 X-Mailer: Evolution 2.8.1.1 Content-type: text/plain Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <458064.38586.qm@web30805.mail.mud.yahoo.com> <460146CD.90306@Sun.COM> Status: RO Content-Length: 1046 On Wed, 2007-03-21 at 10:53 -0400, Stefan Teleman wrote: > Octave Orgeron wrote: > > Hi, > > > > Looks good. In the section that shows its dependencies, I had a > > question. Are we going to include LDAP, Kerberos, etc support or just > > the minimum support? If the components are in the OS, I think we should > > enable the features. Otherwise, we'll be giving customers a reason to > > go an compile their own version, which I think we are trying to avoid. > > > > Octave > > The plan definitely includes LDAP and Kerberos bindings. > > The problem is that CURL assumes the OpenLDAP and MIT Kerberos 5 API's and > refuses anything else (modulo some patching which will not be accepted upstream). > > I know that the Kerberos 5 team is working on the MIT API Compatibility Layer, > and that it will become available in Nevada. I don't yet know about LDAP. > libkrb5 was introduced in build 38 (PSARC 2006/027). It should be (basically) compatible with the MIT API. Our Kerberos implementation is based on MIT's. -Mark > --Stefan > From sacadmin Wed Mar 21 08:59:57 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LFxuh1028833 for ; Wed, 21 Mar 2007 08:59:57 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LFxr7q028079 for <@sunmail1brm.central.sun.com:lsarc-members@sun.com>; Wed, 21 Mar 2007 15:59:55 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900209GFRGQ00@brm-avmta-1.central.sun.com> for lsarc-members@sun.com (ORCPT lsarc-members@sun.com); Wed, 21 Mar 2007 09:59:51 -0600 (MDT) Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900JM5GFRSGA0@brm-avmta-1.central.sun.com> for lsarc-members@sun.com (ORCPT lsarc-members@sun.com); Wed, 21 Mar 2007 09:59:51 -0600 (MDT) Received: from [192.168.0.101] (vpn-129-150-16-146.SFBay.Sun.COM [129.150.16.146]) by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2LFxn6W023477 for ; Wed, 21 Mar 2007 08:59:50 -0700 (PDT) Date: Wed, 21 Mar 2007 08:58:42 -0700 From: Alan Coopersmith Subject: [Fwd: PSARC/2007/165 Including CURL with Solaris] To: lsarc-members@Sun.COM Message-id: <46015632.4050905@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_RRQ8GEUV/g2qB8q6xW9QkA)" X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 1.5.0.4 (X11/20060602) Status: RO Content-Length: 14872 This is a multi-part message in MIME format. --Boundary_(ID_RRQ8GEUV/g2qB8q6xW9QkA) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT Just for our information, since we've had several projects come through which used curl and we gave advice that someone should step up and provide a common curl for all of them - now we can point to a common curl, though only in new Solaris releases. -alan- -------- Original Message -------- Subject: PSARC/2007/165 Including CURL with Solaris Date: Tue, 20 Mar 2007 21:05:35 -0700 From: Bart Smaalders Organization: Sun Microsystems To: PSARC-EXT@sun.com CC: Stefan Teleman I'm sponsoring the attached fast-track for Stefan Teleman. The requested binding is patch/micro release, and the stability levels are as noted in the document. Materials are in the case directory. This case times out on 3/28/2007. - Bart -- Bart Smaalders Solaris Kernel Performance barts@cyber.eng.sun.com http://blogs.sun.com/barts --Boundary_(ID_RRQ8GEUV/g2qB8q6xW9QkA) Content-type: text/plain; name=CURLFastTrack.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=CURLFastTrack.txt Including CURL with Solaris Stefan Teleman 15 March 2007 1. Summary and motivation The Internet has created the necessity for a standardized syntax format for accessing remote object references. In 1994, IETF published the URI [Uniform Resource Identifier] Specification [RFC 1630] [76], followed by the URN [Uniform Resource Name] Specification [RFC 1737] [77] and the URL [Uniform Resource Locator] Specification [RFC 1738] [16]. Since then, the terms URI, URL and URN have been used interchangeably. While subtle distinctions between URI, URL and URN do exist, these differences have become, in practice, largely academic. This evolution has created the need for programmatic and userland facilities supporting remote object referencing and data transfers, compliant to the specifications outlined above. CURL [http://curl.haxx.se/] [1] provides such a collection of facilities in a portable and platform independent implementation. CURL is known to run on most UNIX platforms, as well as Windows. This FastTrack proposes the integration of CURL in Solaris. CURL is Open Source Software, and is developed and maintained outside of SMI. As such, the SFW Consolidation is the natural choice for Solaris integration. This case proposes the most recent stable release of CURL, 7.16.1. CURL stands for 'C-URL' [where 'C' refers to the C Programming Language]. For the purposes of this document, the terms CURL and LibCURL are semantically equivalent. The 'curl' executable is a wrapper around the LibCURL library [libcurl.so.3.0.0], and implements a command-line interface to the facilities provided by LibCURL. This case seeks Micro/Patch Release Binding. 2. Technical issues 2.1. Key objects /usr/bin/curl /usr/bin/curl-config /usr/lib/libcurl.so.3.0.0 /usr/lib/libcurl.so.3 -> /usr/lib/libcurl.so.3.0.0 /usr/lib/libcurl.so -> /usr/lib/libcurl.so.3.0.0 /usr/include/curl/curl.h /usr/include/curl/curlver.h /usr/include/curl/easy.h /usr/include/curl/mprintf.h /usr/include/curl/multi.h /usr/include/curl/stdcheaders.h /usr/include/curl/types.h /usr/share/man/man1/curl.1 /usr/share/man/man1/curl-config.1 /usr/share/man/man3/libcurl.3 /usr/share/man/man3/curl_easy_cleanup.3 /usr/share/man/man3/curl_easy_duphandle.3 /usr/share/man/man3/curl_easy_escape.3 /usr/share/man/man3/curl_easy_getinfo.3 /usr/share/man/man3/curl_easy_init.3 /usr/share/man/man3/curl_easy_perform.3 /usr/share/man/man3/curl_easy_reset.3 /usr/share/man/man3/curl_easy_setopt.3 /usr/share/man/man3/curl_easy_strerror.3 /usr/share/man/man3/curl_easy_unescape.3 /usr/share/man/man3/curl_escape.3 /usr/share/man/man3/curl_formadd.3 /usr/share/man/man3/curl_formfree.3 /usr/share/man/man3/curl_formget.3 /usr/share/man/man3/curl_free.3 /usr/share/man/man3/curl_getdate.3 /usr/share/man/man3/curl_getenv.3 /usr/share/man/man3/curl_global_cleanup.3 /usr/share/man/man3/curl_global_init.3 /usr/share/man/man3/curl_global_init_mem.3 /usr/share/man/man3/curl_mprintf.3 /usr/share/man/man3/curl_multi_add_handle.3 /usr/share/man/man3/curl_multi_assign.3 /usr/share/man/man3/curl_multi_cleanup.3 /usr/share/man/man3/curl_multi_fdset.3 /usr/share/man/man3/curl_multi_info_read.3 /usr/share/man/man3/curl_multi_init.3 /usr/share/man/man3/curl_multi_perform.3 /usr/share/man/man3/curl_multi_remove_handle.3 /usr/share/man/man3/curl_multi_setopt.3 /usr/share/man/man3/curl_multi_socket.3 /usr/share/man/man3/curl_multi_strerror.3 /usr/share/man/man3/curl_multi_timeout.3 /usr/share/man/man3/curl_share_cleanup.3 /usr/share/man/man3/curl_share_init.3 /usr/share/man/man3/curl_share_setopt.3 /usr/share/man/man3/curl_share_strerror.3 /usr/share/man/man3/curl_slist_append.3 /usr/share/man/man3/curl_slist_free_all.3 /usr/share/man/man3/curl_strequal.3 /usr/share/man/man3/curl_unescape.3 /usr/share/man/man3/curl_version.3 /usr/share/man/man3/curl_version_info.3 /usr/share/man/man3/libcurl-easy.3 /usr/share/man/man3/libcurl-errors.3 /usr/share/man/man3/libcurl-multi.3 /usr/share/man/man3/libcurl-share.3 /usr/share/man/man3/libcurl-tutorial.3 /usr/share/doc/curl/index.html /usr/share/doc/curl/curl.html /usr/share/doc/curl/curl-config.html LibCURL's functionality is provided by one executable [curl], and one shared library [libcurl.so.3.0.0]. LibCURL implements a very large number of Internet-related protocols, authentication mechanisms, and data transfer facilities. Key aspects of the specifications implemented, and facilities provided, by, LibCURL are listed below. CURL is largefile aware and is 64-bit clean. CURL is not thread-safe, and its functions are not reentrant. Calls to public functions within the LibCURL library, from different threads, must be serialized. The private LibCURL interfaces use static data structures [for internal consumption only]. 2.2. Specifications LibCURL implements the following Specifications: NAME DESCRIPTION NOTES RFC 0822 Standard for ARPA Internet Text Messages [8] RFC 0850 Standard for Interchange of USENET Messages [9] RFC 0959 File Transfer Protocol [FTP] [10] RFC 1036 Standard for Interchange of USENET Messages [11] RFC 1123 Requirements for Internet Hosts -- Application and Support [12] RFC 1350 Trivial File Transfer Protocol [TFTP] [13] RFC 1635 Anonymous FTP [14] RFC 1639 FTP Operation Over Big Address Records [FOOBAR] [15] RFC 1738 Uniform Resource Locators [URL] [16] RFC 1777 Lightweight Directory Access Protocol [LDAP] [17] RFC 1808 Relative Uniform Resource Locators [18] RFC 1867 Form-based File Upload in HTML [19] RFC 1884 IPv6 [20] RFC 1928 SOCKS Protocol [21] RFC 1945 HTTP/1.0 [22] RFC 1950 Z-LIB [23] RFC 1951 DEFLATE [24] RFC 1952 GZip [25] RFC 1959 LDAP URL RFC 2045 MIME Part 1: Format of Internet Message Bodies [26] RFC 2046 MIME Part 2: Media Types [27] RFC 2047 MIME Part 3: Message Header Extensions for Non-ASCII Text [28] RFC 2048 MIME Part 4: Registration Procedures [29] RFC 2049 MIME Part 5: Conformance Criteria and Examples [30] RFC 2068 HTTP/1.1 [31] RFC 2109 HTTP Session and State Management [32] RFC 2133 IPv6 Sockets [33] RFC 2183 Content-Disposition Header [34] RFC 2184 MIME Parameter Value and Encoded Word Extensions [35] RFC 2228 FTP Security Extensions [36] RFC 2229 Dictionary Server Protocol [37] RFC 2231 MIME Parameter Value and Encoded Word Extensions [38] RFC 2246 TLS Protocol 1.0 [39] RFC 2255 New LDAP URL [40] RFC 2326 Real Time Streaming Protocol [RTSP] [41] RFC 2373 IP Version 6 Addressing Architecture [42] RFC 2388 Returning Values from Forms: multipart/form-data [43] RFC 2389 Feature negotiation mechanism for the File Transfer Protocol [44] RFC 2396 Uniform Resource Identifiers [URI]: Generic Syntax [45] RFC 2428 FTP Extensions for IPv6 and NATs [46] RFC 2459 Internet X.509 Public Key Infrastructure: Certificate and CRL Profile [47] RFC 2518 HTTP Extensions for Distributed Authoring: WebDAV [48] RFC 2553 Basic Socket Interface Extensions for IPv6 [49] RFC 2577 FTP Security Considerations [50] RFC 2616 HTTP/1.1 [Obsoletes RFC 2068] [51] RFC 2617 HTTP Authentication: Basic and Digest Access Authentication [52] RFC 2640 Internationalization of the File Transfer Protocol [53] RFC 2718 Guidelines for new URL Schemes [54] RFC 2732 Format for Literal IPv6 Addresses in URL's [55] RFC 2817 Upgrading to TLS Within HTTP/1.1 [56] RFC 2818 HTTP Over TLS [57] RFC 2854 The 'text/html' Media Type [58] RFC 2936 HTTP MIME Type Handler Detection [59] RFC 2964 Use of HTTP State Management [60] RFC 2965 HTTP State Management Mechanism [61] RFC 3280 Internet X.509 Public Key Infrastructure [62] RFC 3493 Basic Socket Interface Extensions for IPv6 [63] RFC 3513 Internet Protocol Version 6 [IPv6] Addressing Architecture [64] RFC 3617 Uniform Resource Identifier [URI] Scheme and Applicability Statement for TFTP [65] RFC 3986 Uniform Resource Identifier [URI]: Generic Syntax [66] RFC 4217 Securing FTP with TLS [67] RFC 4248 The telnet URI Scheme [68] RFC 4346 The Transport Layer Security [TLS] Protocol Version 1.1 [69] RFC 4366 Transport Layer Security [TLS] Extensions [70] Cookie Spec Persistent Client State - HTTP Cookies [71] Draft SPNEGO HTTP Authentication: SPNEGO Access Authentication As implemented in Microsoft Windows 2000 [72] Draft SecSH/SCP/SFTP/SSH/URI-04 Uniform Resource Identifier [URI] Scheme for Secure File Transfer Protocol [SFTP] and Secure Shell [SSH] [73] Draft Web Proxy TCP Tunneling Tunneling TCP based protocols through Web proxy servers [74] NTLM The NTLM Authentication Protocol [75] 2.3. Language bindings CURL is written in C. No other language bindings are provided by the canonical distribution. 2.4. Documentation CURL provides an extensive and complete documentation set in UNIX manual format, as well as HTML. We propose that the full documentation set be included with the Solaris integration. 3. Interfaces 3.1. Interface Stability CURL is an Open Source project, and its design, development and release schedule are external to SMI. CURL makes no implicit or explicit promises or guarantees of API or ABI compatibility between releases. 3.2. Imported interfaces In addition to the Standard C Library and Network Services Library Interfaces, CURL depends on, and imports interfaces, from: NAME STABILITY NOTES OpenSSL External/Volatile PSARC/2003/500 [2] Z-Lib Committed PSARC/2006/537 [3] LDAP [OpenLDAP] Evolving PSARC/1997/276 [4] Kerberos [MIT] External PSARC/1999/617 et seq. [5] LibIDN Uncommitted PSARC/2007/000 [6] GNU TLS Volatile PSARC/2002/621 [7] The LDAP, Kerberos and GNU TLS bindings are optional. The OpenSSL, Z-Lib and LibIDN bindings are mandatory. 3.3. Exported interfaces NAME STABILITY NOTES SUNWcurl Uncommitted Package name /usr/bin/curl Uncommitted Executable location /usr/bin/curl-config Uncommitted Shell script location /usr/lib/libcurl.so.3.0.0 Uncommitted Library location /usr/lib/libcurl.so.3 Uncommitted Symbolic link /usr/lib/libcurl.so Uncommitted Symbolic link /usr/include/curl/ Uncommitted Include files 4. References [1] http://curl.haxx.se/ [2] http://www.openssl.org/ [3] http://www.gzip.org/zlib/ [4] http://www.openldap.org/ [5] http://web.mit.edu/kerberos/dist/index.html [6] http://www.gnu.org/software/libidn/ [7] http://www.gnu.org/software/gnutls/ [8] http://www.ietf.org/rfc/rfc0822.txt [9] http://www.ietf.org/rfc/rfc0850.txt [10] http://www.ietf.org/rfc/rfc0959.txt [11] http://www.ietf.org/rfc/rfc1036.txt [12] http://www.ietf.org/rfc/rfc1123.txt [13] http://www.ietf.org/rfc/rfc1350.txt [14] http://www.ietf.org/rfc/rfc1635.txt [15] http://www.ietf.org/rfc/rfc1639.txt [16] http://www.ietf.org/rfc/rfc1738.txt [17] http://www.ietf.org/rfc/rfc1777.txt [18] http://www.ietf.org/rfc/rfc1808.txt [19] http://www.ietf.org/rfc/rfc1867.txt [20] http://www.ietf.org/rfc/rfc1884.txt [21] http://www.ietf.org/rfc/rfc1928.txt [22] http://www.ietf.org/rfc/rfc1945.txt [23] http://www.ietf.org/rfc/rfc1945.txt [24] http://www.ietf.org/rfc/rfc1951.txt [25] http://www.ietf.org/rfc/rfc1952.txt [26] http://www.ietf.org/rfc/rfc1959.txt [27] http://www.ietf.org/rfc/rfc2045.txt [28] http://www.ietf.org/rfc/rfc2046.txt [29] http://www.ietf.org/rfc/rfc2047.txt [30] http://www.ietf.org/rfc/rfc2048.txt [31] http://www.ietf.org/rfc/rfc2049.txt [32] http://www.ietf.org/rfc/rfc2068.txt [33] http://www.ietf.org/rfc/rfc2109.txt [34] http://www.ietf.org/rfc/rfc2133.txt [35] http://www.ietf.org/rfc/rfc2183.txt [36] http://www.ietf.org/rfc/rfc2184.txt [37] http://www.ietf.org/rfc/rfc2228.txt [38] http://www.ietf.org/rfc/rfc2229.txt [39] http://www.ietf.org/rfc/rfc2231.txt [40] http://www.ietf.org/rfc/rfc2246.txt [41] http://www.ietf.org/rfc/rfc2255.txt [41] http://www.ietf.org/rfc/rfc2326.txt [42] http://www.ietf.org/rfc/rfc2373.txt [43] http://www.ietf.org/rfc/rfc2388.txt [44] http://www.ietf.org/rfc/rfc2389.txt [45] http://www.ietf.org/rfc/rfc2396.txt [46] http://www.ietf.org/rfc/rfc2428.txt [47] http://www.ietf.org/rfc/rfc2459.txt [48] http://www.ietf.org/rfc/rfc2518.txt [49] http://www.ietf.org/rfc/rfc2553.txt [50] http://www.ietf.org/rfc/rfc2577.txt [51] http://www.ietf.org/rfc/rfc2616.txt [52] http://www.ietf.org/rfc/rfc2617.txt [53] http://www.ietf.org/rfc/rfc2640.txt [54] http://www.ietf.org/rfc/rfc2718.txt [55] http://www.ietf.org/rfc/rfc2732.txt [56] http://www.ietf.org/rfc/rfc2817.txt [57] http://www.ietf.org/rfc/rfc2818.txt [58] http://www.ietf.org/rfc/rfc2854.txt [59] http://www.ietf.org/rfc/rfc2936.txt [60] http://www.ietf.org/rfc/rfc2964.txt [61] http://www.ietf.org/rfc/rfc2965.txt [62] http://www.ietf.org/rfc/rfc3280.txt [63] http://www.ietf.org/rfc/rfc3493.txt [64] http://www.ietf.org/rfc/rfc3513.txt [65] http://www.ietf.org/rfc/rfc3617.txt [66] http://www.ietf.org/rfc/rfc3986.txt [67] http://www.ietf.org/rfc/rfc4217.txt [68] http://www.ietf.org/rfc/rfc4248.txt [69] http://www.ietf.org/rfc/rfc4346.txt [70] http://www.ietf.org/rfc/rfc4366.txt [71] http://curl.haxx.se/rfc/cookie_spec.html [72] http://curl.haxx.se/rfc/draft-brezak-spnego-http-04.txt [73] http://curl.haxx.se/rfc/draft-ietf-secsh-scp-sftp-ssh-uri-04.txt [74] http://curl.haxx.se/rfc/draft-luotonen-web-proxy-tunneling-01.txt [75] http://curl.haxx.se/rfc/ntlm.html [76] http://tools.ietf.org/html/rfc1630 [77] http://www.ietf.org/rfc/rfc1737.txt --Boundary_(ID_RRQ8GEUV/g2qB8q6xW9QkA)-- From gww@eng.sun.com Wed Mar 21 13:21:47 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LKLkRD007902 for ; Wed, 21 Mar 2007 13:21:47 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LKLbMV026093; Wed, 21 Mar 2007 20:21:45 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900E0LSK63E00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 21 Mar 2007 13:21:42 -0700 (PDT) Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900A47SK6GU20@nwk-avmta-1.sfbay.Sun.COM>; Wed, 21 Mar 2007 13:21:42 -0700 (PDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2LKLfYV029851; Wed, 21 Mar 2007 13:21:41 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id l2LLLd9C024768; Wed, 21 Mar 2007 13:21:39 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id l2LLLdgF024766; Wed, 21 Mar 2007 13:21:39 -0800 (PST) Date: Wed, 21 Mar 2007 13:21:39 -0800 (PST) From: Gary Winiger Subject: Re: PSARC/2007/165 Including CURL with Solaris To: PSARC-EXT@sun.com, bart.smaalders@sun.com Cc: Stefan.Teleman@sun.com, lsarc-members@sun.com Message-id: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 645 > 3.2. Imported interfaces > > In addition to the Standard C Library and Network Services Library > Interfaces, CURL depends on, and imports interfaces, from: > > NAME STABILITY NOTES > > OpenSSL External/Volatile PSARC/2003/500 [2] > Z-Lib Committed PSARC/2006/537 [3] > LDAP [OpenLDAP] Evolving PSARC/1997/276 [4] > Kerberos [MIT] External PSARC/1999/617 et seq. [5] > LibIDN Uncommitted PSARC/2007/000 [6] > GNU TLS Volatile PSARC/2002/621 [7] How is the change managed for the "unstable" public interfaces? Will contracts be in place? Any such contracts should have prototypes as case materials. Gary.. From sacadmin Wed Mar 21 13:21:49 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LKLmqH007906 for ; Wed, 21 Mar 2007 13:21:48 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LKLbMV026093; Wed, 21 Mar 2007 20:21:45 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900E0LSK63E00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 21 Mar 2007 13:21:42 -0700 (PDT) Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900A47SK6GU20@nwk-avmta-1.sfbay.Sun.COM>; Wed, 21 Mar 2007 13:21:42 -0700 (PDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2LKLfYV029851; Wed, 21 Mar 2007 13:21:41 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id l2LLLd9C024768; Wed, 21 Mar 2007 13:21:39 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id l2LLLdgF024766; Wed, 21 Mar 2007 13:21:39 -0800 (PST) Date: Wed, 21 Mar 2007 13:21:39 -0800 (PST) From: Gary Winiger Subject: Re: PSARC/2007/165 Including CURL with Solaris To: PSARC-EXT@sun.com, bart.smaalders@sun.com Cc: Stefan.Teleman@sun.com, lsarc-members@sun.com Message-id: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 645 > 3.2. Imported interfaces > > In addition to the Standard C Library and Network Services Library > Interfaces, CURL depends on, and imports interfaces, from: > > NAME STABILITY NOTES > > OpenSSL External/Volatile PSARC/2003/500 [2] > Z-Lib Committed PSARC/2006/537 [3] > LDAP [OpenLDAP] Evolving PSARC/1997/276 [4] > Kerberos [MIT] External PSARC/1999/617 et seq. [5] > LibIDN Uncommitted PSARC/2007/000 [6] > GNU TLS Volatile PSARC/2002/621 [7] How is the change managed for the "unstable" public interfaces? Will contracts be in place? Any such contracts should have prototypes as case materials. Gary.. From Stefan.Teleman@Sun.COM Wed Mar 21 13:25:19 2007 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LKPJoe007951 for ; Wed, 21 Mar 2007 13:25:19 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LKPGhg006521; Wed, 21 Mar 2007 14:25:18 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900E0NSQ5F500@nwk-avmta-1.sfbay.Sun.COM>; Wed, 21 Mar 2007 13:25:17 -0700 (PDT) Received: from jurassic.eng.sun.com ([129.146.56.144]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900ACHSQ4GM20@nwk-avmta-1.sfbay.Sun.COM>; Wed, 21 Mar 2007 13:25:16 -0700 (PDT) Received: from [192.9.61.55] (punchin-client-192-9-61-55.SFBay.Sun.COM [192.9.61.55]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l2LKPFWm385855; Wed, 21 Mar 2007 13:25:15 -0700 (PDT) Date: Wed, 21 Mar 2007 16:24:23 -0400 From: Stefan Teleman Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> To: Gary Winiger Cc: PSARC-EXT@Sun.COM, bart.smaalders@Sun.COM, lsarc-members@Sun.COM Reply-to: Stefan Teleman Message-id: <46019477.5050507@Sun.COM> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> User-Agent: Thunderbird 1.5.0.7 (X11/20060915) Status: RO Content-Length: 822 Gary Winiger wrote: >> 3.2. Imported interfaces >> >> In addition to the Standard C Library and Network Services Library >> Interfaces, CURL depends on, and imports interfaces, from: >> >> NAME STABILITY NOTES >> >> OpenSSL External/Volatile PSARC/2003/500 [2] >> Z-Lib Committed PSARC/2006/537 [3] >> LDAP [OpenLDAP] Evolving PSARC/1997/276 [4] >> Kerberos [MIT] External PSARC/1999/617 et seq. [5] >> LibIDN Uncommitted PSARC/2007/000 [6] >> GNU TLS Volatile PSARC/2002/621 [7] > > How is the change managed for the "unstable" public interfaces? > Will contracts be in place? Any such contracts should have prototypes > as case materials. Yes, they will have contracts -- i just haven't finished them yet. --Stefan -- Stefan Teleman Sun Microsystems, Inc. Stefan.Teleman@Sun.COM From sacadmin Wed Mar 21 13:25:19 2007 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LKPJJO007954 for ; Wed, 21 Mar 2007 13:25:19 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LKPGhg006521; Wed, 21 Mar 2007 14:25:18 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900E0NSQ5F500@nwk-avmta-1.sfbay.Sun.COM>; Wed, 21 Mar 2007 13:25:17 -0700 (PDT) Received: from jurassic.eng.sun.com ([129.146.56.144]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF900ACHSQ4GM20@nwk-avmta-1.sfbay.Sun.COM>; Wed, 21 Mar 2007 13:25:16 -0700 (PDT) Received: from [192.9.61.55] (punchin-client-192-9-61-55.SFBay.Sun.COM [192.9.61.55]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l2LKPFWm385855; Wed, 21 Mar 2007 13:25:15 -0700 (PDT) Date: Wed, 21 Mar 2007 16:24:23 -0400 From: Stefan Teleman Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> To: Gary Winiger Cc: PSARC-EXT@Sun.COM, bart.smaalders@Sun.COM, lsarc-members@Sun.COM Reply-to: Stefan Teleman Message-id: <46019477.5050507@Sun.COM> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> User-Agent: Thunderbird 1.5.0.7 (X11/20060915) Status: RO Content-Length: 822 Gary Winiger wrote: >> 3.2. Imported interfaces >> >> In addition to the Standard C Library and Network Services Library >> Interfaces, CURL depends on, and imports interfaces, from: >> >> NAME STABILITY NOTES >> >> OpenSSL External/Volatile PSARC/2003/500 [2] >> Z-Lib Committed PSARC/2006/537 [3] >> LDAP [OpenLDAP] Evolving PSARC/1997/276 [4] >> Kerberos [MIT] External PSARC/1999/617 et seq. [5] >> LibIDN Uncommitted PSARC/2007/000 [6] >> GNU TLS Volatile PSARC/2002/621 [7] > > How is the change managed for the "unstable" public interfaces? > Will contracts be in place? Any such contracts should have prototypes > as case materials. Yes, they will have contracts -- i just haven't finished them yet. --Stefan -- Stefan Teleman Sun Microsystems, Inc. Stefan.Teleman@Sun.COM From jek3@sun.com Wed Mar 21 14:10:59 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2LLAwFi008895 for ; Wed, 21 Mar 2007 14:10:58 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2LLAfEL010044; Wed, 21 Mar 2007 21:10:56 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JF900C01UU68K00@nwk-avmta-2.sfbay.sun.com>; Wed, 21 Mar 2007 14:10:54 -0700 (PDT) Received: from jurassic-x4600.Eng.Sun.COM ([129.146.17.59]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JF90088MUU6UI40@nwk-avmta-2.sfbay.sun.com>; Wed, 21 Mar 2007 14:10:54 -0700 (PDT) Received: from [129.150.12.53] (vpn-129-150-12-53.SFBay.Sun.COM [129.150.12.53]) by jurassic-x4600.Eng.Sun.COM (8.14.0+Sun/8.14.0) with ESMTP id l2LLArr5410854; Wed, 21 Mar 2007 14:10:53 -0700 (PDT) Date: Wed, 21 Mar 2007 11:10:47 -1000 From: Joseph Kowalski Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <4600AF0F.40204@Sun.COM> To: Bart Smaalders Cc: PSARC-EXT@sun.com, Stefan Teleman Message-id: <46019F57.1030201@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <4600AF0F.40204@Sun.COM> User-Agent: Thunderbird 1.5.0.5 (X11/20060925) Status: RO Content-Length: 802 Bart Smaalders wrote: > The Internet has created the necessity for a standardized > syntax format for accessing remote object references. In 1994, > IETF published the URI [Uniform Resource Identifier] Specification > [RFC 1630] [76], followed by the URN [Uniform Resource Name] > Specification [RFC 1737] [77] and the URL [Uniform Resource Locator] > Specification [RFC 1738] [16]. Since then, the terms URI, URL and > URN have been used interchangeably. While subtle distinctions > between URI, URL and URN do exist, these differences have become, > in practice, largely academic. > Clearly you haven't programmed in Java, where the API make painful distinctions between URI and URL. 8^) Otherwise, same comments about library versioning an manpage naming as on 2004/164. - jek3 From Stefan.Teleman@sun.com Mon Mar 26 16:47:19 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2QNlIbK000664 for ; Mon, 26 Mar 2007 16:47:19 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l2QNlCMv000088; Tue, 27 Mar 2007 07:47:16 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFJ00K0FBEO1C00@brm-avmta-1.central.sun.com>; Mon, 26 Mar 2007 17:47:12 -0600 (MDT) Received: from jurassic.eng.sun.com ([129.146.68.130]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFJ00F3TBEOPPF0@brm-avmta-1.central.sun.com>; Mon, 26 Mar 2007 17:47:12 -0600 (MDT) Received: from [192.9.61.113] (punchin-client-192-9-61-113.SFBay.Sun.COM [192.9.61.113]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l2QNl0FS209233; Mon, 26 Mar 2007 16:47:01 -0700 (PDT) Date: Mon, 26 Mar 2007 18:46:07 -0400 From: Stefan Teleman Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> To: Gary Winiger Cc: PSARC-EXT@sun.com, bart.smaalders@sun.com, lsarc-members@sun.com Reply-to: Stefan Teleman Message-id: <46084D2F.6000502@Sun.COM> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> User-Agent: Thunderbird 1.5.0.7 (X11/20060915) Status: RO Content-Length: 291 It looks like LSARC 2006/202 which integrated GNU TLS only did so for the 32-bit builds. This will affect the 64-bit CURL (which can either be delivered in 64-bit without GNU TLS, or cannot be delivered at all). --Stefan -- Stefan Teleman Sun Microsystems, Inc. Stefan.Teleman@Sun.COM From sacadmin Mon Mar 26 16:47:21 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2QNlKYu000668 for ; Mon, 26 Mar 2007 16:47:21 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l2QNlCMv000088; Tue, 27 Mar 2007 07:47:16 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFJ00K0FBEO1C00@brm-avmta-1.central.sun.com>; Mon, 26 Mar 2007 17:47:12 -0600 (MDT) Received: from jurassic.eng.sun.com ([129.146.68.130]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFJ00F3TBEOPPF0@brm-avmta-1.central.sun.com>; Mon, 26 Mar 2007 17:47:12 -0600 (MDT) Received: from [192.9.61.113] (punchin-client-192-9-61-113.SFBay.Sun.COM [192.9.61.113]) by jurassic.eng.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l2QNl0FS209233; Mon, 26 Mar 2007 16:47:01 -0700 (PDT) Date: Mon, 26 Mar 2007 18:46:07 -0400 From: Stefan Teleman Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> To: Gary Winiger Cc: PSARC-EXT@sun.com, bart.smaalders@sun.com, lsarc-members@sun.com Reply-to: Stefan Teleman Message-id: <46084D2F.6000502@Sun.COM> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> User-Agent: Thunderbird 1.5.0.7 (X11/20060915) Status: RO Content-Length: 291 It looks like LSARC 2006/202 which integrated GNU TLS only did so for the 32-bit builds. This will affect the 64-bit CURL (which can either be delivered in 64-bit without GNU TLS, or cannot be delivered at all). --Stefan -- Stefan Teleman Sun Microsystems, Inc. Stefan.Teleman@Sun.COM From gww@eng.sun.com Mon Mar 26 16:55:16 2007 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2QNtG9L001267 for ; Mon, 26 Mar 2007 16:55:16 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2QNtGeA022884; Mon, 26 Mar 2007 16:55:16 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFJ00A0VBS1UW00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 26 Mar 2007 16:55:13 -0700 (PDT) Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFJ008O6BS1SO60@nwk-avmta-1.sfbay.Sun.COM>; Mon, 26 Mar 2007 16:55:13 -0700 (PDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2QNtCFe007876; Mon, 26 Mar 2007 16:55:12 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id l2R0saNj002634; Mon, 26 Mar 2007 16:54:36 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id l2R0saMP002633; Mon, 26 Mar 2007 16:54:36 -0800 (PST) Date: Mon, 26 Mar 2007 16:54:36 -0800 (PST) From: Gary Winiger Subject: Re: PSARC/2007/165 Including CURL with Solaris To: gww@eng.sun.com, Stefan.Teleman@sun.com Cc: PSARC-EXT@sun.com, bart.smaalders@sun.com, lsarc-members@sun.com Message-id: <200703270054.l2R0saMP002633@marduk.eng.sun.com> Content-transfer-encoding: 7BIT X-Sun-Charset: US-ASCII X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 324 > It looks like LSARC 2006/202 which integrated GNU TLS only did so for the 32-bit > builds. This will affect the 64-bit CURL (which can either be delivered in > 64-bit without GNU TLS, or cannot be delivered at all). Perhaps I'm missing something. This seems like a bug in 2006/202. What can't be fixed here? Gary.. From sacadmin Mon Mar 26 16:55:16 2007 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2QNtGeP001269 for ; Mon, 26 Mar 2007 16:55:16 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2QNtGeA022884; Mon, 26 Mar 2007 16:55:16 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFJ00A0VBS1UW00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 26 Mar 2007 16:55:13 -0700 (PDT) Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFJ008O6BS1SO60@nwk-avmta-1.sfbay.Sun.COM>; Mon, 26 Mar 2007 16:55:13 -0700 (PDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2QNtCFe007876; Mon, 26 Mar 2007 16:55:12 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id l2R0saNj002634; Mon, 26 Mar 2007 16:54:36 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id l2R0saMP002633; Mon, 26 Mar 2007 16:54:36 -0800 (PST) Date: Mon, 26 Mar 2007 16:54:36 -0800 (PST) From: Gary Winiger Subject: Re: PSARC/2007/165 Including CURL with Solaris To: gww@eng.sun.com, Stefan.Teleman@sun.com Cc: PSARC-EXT@sun.com, bart.smaalders@sun.com, lsarc-members@sun.com Message-id: <200703270054.l2R0saMP002633@marduk.eng.sun.com> Content-transfer-encoding: 7BIT X-Sun-Charset: US-ASCII X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 324 > It looks like LSARC 2006/202 which integrated GNU TLS only did so for the 32-bit > builds. This will affect the 64-bit CURL (which can either be delivered in > 64-bit without GNU TLS, or cannot be delivered at all). Perhaps I'm missing something. This seems like a bug in 2006/202. What can't be fixed here? Gary.. From alan.coopersmith@sun.com Mon Mar 26 16:55:36 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2QNtZ0w001289 for ; Mon, 26 Mar 2007 16:55:35 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l2QNtWkZ002580; Tue, 27 Mar 2007 07:55:34 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFJ00607BSJFG00@nwk-avmta-2.sfbay.sun.com>; Mon, 26 Mar 2007 16:55:31 -0700 (PDT) Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFJ0057YBSJ8L10@nwk-avmta-2.sfbay.sun.com>; Mon, 26 Mar 2007 16:55:31 -0700 (PDT) Received: from [129.146.108.211] (almas.SFBay.Sun.COM [129.146.108.211]) by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2QNtUcg019814; Mon, 26 Mar 2007 16:55:30 -0700 (PDT) Date: Mon, 26 Mar 2007 16:55:30 -0700 From: Alan Coopersmith Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <46084D2F.6000502@Sun.COM> To: Stefan Teleman Cc: Gary Winiger , PSARC-EXT@sun.com, bart.smaalders@sun.com, lsarc-members@sun.com Message-id: <46085D72.8040700@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> <46084D2F.6000502@Sun.COM> User-Agent: Thunderbird 2.0pre (X11/20070214) Status: RO Content-Length: 433 Stefan Teleman wrote: > It looks like LSARC 2006/202 which integrated GNU TLS only did so for > the 32-bit builds. Which was allowed because it did so as a private library for GNOME's use only, not intended for use by anyone else. If it's being raised to public, then that should include adding a 64-bit version. -- -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - X Window System Engineering From sacadmin Mon Mar 26 16:55:37 2007 Received: from sunmail4.Singapore.Sun.COM (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2QNtaiC001293 for ; Mon, 26 Mar 2007 16:55:37 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.Singapore.Sun.COM (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l2QNtWkZ002580; Tue, 27 Mar 2007 07:55:34 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFJ00607BSJFG00@nwk-avmta-2.sfbay.sun.com>; Mon, 26 Mar 2007 16:55:31 -0700 (PDT) Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFJ0057YBSJ8L10@nwk-avmta-2.sfbay.sun.com>; Mon, 26 Mar 2007 16:55:31 -0700 (PDT) Received: from [129.146.108.211] (almas.SFBay.Sun.COM [129.146.108.211]) by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2QNtUcg019814; Mon, 26 Mar 2007 16:55:30 -0700 (PDT) Date: Mon, 26 Mar 2007 16:55:30 -0700 From: Alan Coopersmith Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <46084D2F.6000502@Sun.COM> To: Stefan Teleman Cc: Gary Winiger , PSARC-EXT@sun.com, bart.smaalders@sun.com, lsarc-members@sun.com Message-id: <46085D72.8040700@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> <46084D2F.6000502@Sun.COM> User-Agent: Thunderbird 2.0pre (X11/20070214) Status: RO Content-Length: 433 Stefan Teleman wrote: > It looks like LSARC 2006/202 which integrated GNU TLS only did so for > the 32-bit builds. Which was allowed because it did so as a private library for GNOME's use only, not intended for use by anyone else. If it's being raised to public, then that should include adding a 64-bit version. -- -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - X Window System Engineering From John.Plocher@sun.com Mon Mar 26 16:57:59 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2QNvwun001318 for ; Mon, 26 Mar 2007 16:57:58 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2QNvsWP016465; Tue, 27 Mar 2007 00:57:56 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFJ00B07BWJ6H00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 26 Mar 2007 16:57:55 -0700 (PDT) Received: from nwk-ea-fw-1.sun.com ([10.4.134.5]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFJ008A6BWISO70@nwk-avmta-1.sfbay.Sun.COM>; Mon, 26 Mar 2007 16:57:54 -0700 (PDT) Received: from d1-sfbay-09.sun.com ([192.18.39.119]) by nwk-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l2QNvskP028241; Mon, 26 Mar 2007 15:57:54 -0800 (PST) Received: from conversion-daemon.d1-sfbay-09.sun.com by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JFJ00L01BU6Y300@d1-sfbay-09.sun.com> (original mail from John.Plocher@Sun.COM); Mon, 26 Mar 2007 16:57:54 -0700 (PDT) Received: from [129.146.58.87] by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JFJ007MFBWI27F0@d1-sfbay-09.sun.com>; Mon, 26 Mar 2007 16:57:54 -0700 (PDT) Date: Mon, 26 Mar 2007 16:57:51 -0700 From: John Plocher Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <46084D2F.6000502@Sun.COM> Sender: John.Plocher@sun.com To: Stefan Teleman Cc: Gary Winiger , PSARC-EXT@sun.com, lsarc-members@sun.com Message-id: <46085DFF.2060705@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> <46084D2F.6000502@Sun.COM> User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) Status: RO Content-Length: 419 Stefan Teleman wrote: > It looks like LSARC 2006/202 which integrated GNU TLS only did so for > the 32-bit builds. This will affect the 64-bit CURL (which can either be > delivered in 64-bit without GNU TLS, or cannot be delivered at all). Why can't it generate a dependency on a followon to 2006/202 to deliver a 64bit TLS? Nothing says you can't be the one to do the work, since you need the result... -John From sacadmin Mon Mar 26 16:58:00 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2QNvxDI001322 for ; Mon, 26 Mar 2007 16:58:00 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2QNvsWP016465; Tue, 27 Mar 2007 00:57:56 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFJ00B07BWJ6H00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 26 Mar 2007 16:57:55 -0700 (PDT) Received: from nwk-ea-fw-1.sun.com ([10.4.134.5]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFJ008A6BWISO70@nwk-avmta-1.sfbay.Sun.COM>; Mon, 26 Mar 2007 16:57:54 -0700 (PDT) Received: from d1-sfbay-09.sun.com ([192.18.39.119]) by nwk-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l2QNvskP028241; Mon, 26 Mar 2007 15:57:54 -0800 (PST) Received: from conversion-daemon.d1-sfbay-09.sun.com by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JFJ00L01BU6Y300@d1-sfbay-09.sun.com> (original mail from John.Plocher@Sun.COM); Mon, 26 Mar 2007 16:57:54 -0700 (PDT) Received: from [129.146.58.87] by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JFJ007MFBWI27F0@d1-sfbay-09.sun.com>; Mon, 26 Mar 2007 16:57:54 -0700 (PDT) Date: Mon, 26 Mar 2007 16:57:51 -0700 From: John Plocher Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <46084D2F.6000502@Sun.COM> Sender: John.Plocher@sun.com To: Stefan Teleman Cc: Gary Winiger , PSARC-EXT@sun.com, lsarc-members@sun.com Message-id: <46085DFF.2060705@Sun.Com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> <46084D2F.6000502@Sun.COM> User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) Status: RO Content-Length: 419 Stefan Teleman wrote: > It looks like LSARC 2006/202 which integrated GNU TLS only did so for > the 32-bit builds. This will affect the 64-bit CURL (which can either be > delivered in 64-bit without GNU TLS, or cannot be delivered at all). Why can't it generate a dependency on a followon to 2006/202 to deliver a 64bit TLS? Nothing says you can't be the one to do the work, since you need the result... -John From jek3@sun.com Mon Mar 26 20:21:19 2007 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2R3LIAg007543 for ; Mon, 26 Mar 2007 20:21:18 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2R3LDL8034769; Mon, 26 Mar 2007 21:21:14 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFJ00H03LBDD500@nwk-avmta-2.sfbay.sun.com>; Mon, 26 Mar 2007 20:21:13 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFJ005ONLBD8O70@nwk-avmta-2.sfbay.sun.com>; Mon, 26 Mar 2007 20:21:13 -0700 (PDT) Received: from [129.150.12.53] (vpn-129-150-12-53.SFBay.Sun.COM [129.150.12.53]) by jurassic-x4600.sfbay.sun.com (8.14.0+Sun/8.14.0) with ESMTP id l2R3LCtX300455; Mon, 26 Mar 2007 20:21:12 -0700 (PDT) Date: Mon, 26 Mar 2007 17:20:57 -1000 From: Joseph Kowalski Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <46084D2F.6000502@Sun.COM> To: Stefan Teleman Cc: Gary Winiger , PSARC-EXT@sun.com, bart.smaalders@sun.com, lsarc-members@sun.com Message-id: <46088D99.3090206@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> <46084D2F.6000502@Sun.COM> User-Agent: Thunderbird 1.5.0.5 (X11/20060925) Status: RO Content-Length: 445 Stefan Teleman wrote: > It looks like LSARC 2006/202 which integrated GNU TLS only did so for > the 32-bit builds. This will affect the 64-bit CURL (which can either > be delivered in 64-bit without GNU TLS, or cannot be delivered at all). Or, contact the 2006/202 project team and case owner and see if this situation can be fixed. Having 32-bit TLS come in from one place and 64-bit TLS come from another, certainly seems wrong. - jek3 From sacadmin Mon Mar 26 20:21:19 2007 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2R3LJPo007546 for ; Mon, 26 Mar 2007 20:21:19 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2R3LDL8034769; Mon, 26 Mar 2007 21:21:14 -0600 (MDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFJ00H03LBDD500@nwk-avmta-2.sfbay.sun.com>; Mon, 26 Mar 2007 20:21:13 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFJ005ONLBD8O70@nwk-avmta-2.sfbay.sun.com>; Mon, 26 Mar 2007 20:21:13 -0700 (PDT) Received: from [129.150.12.53] (vpn-129-150-12-53.SFBay.Sun.COM [129.150.12.53]) by jurassic-x4600.sfbay.sun.com (8.14.0+Sun/8.14.0) with ESMTP id l2R3LCtX300455; Mon, 26 Mar 2007 20:21:12 -0700 (PDT) Date: Mon, 26 Mar 2007 17:20:57 -1000 From: Joseph Kowalski Subject: Re: PSARC/2007/165 Including CURL with Solaris In-reply-to: <46084D2F.6000502@Sun.COM> To: Stefan Teleman Cc: Gary Winiger , PSARC-EXT@sun.com, bart.smaalders@sun.com, lsarc-members@sun.com Message-id: <46088D99.3090206@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <200703212121.l2LLLdgF024766@marduk.eng.sun.com> <46084D2F.6000502@Sun.COM> User-Agent: Thunderbird 1.5.0.5 (X11/20060925) Status: RO Content-Length: 445 Stefan Teleman wrote: > It looks like LSARC 2006/202 which integrated GNU TLS only did so for > the 32-bit builds. This will affect the 64-bit CURL (which can either > be delivered in 64-bit without GNU TLS, or cannot be delivered at all). Or, contact the 2006/202 project team and case owner and see if this situation can be fixed. Having 32-bit TLS come in from one place and 64-bit TLS come from another, certainly seems wrong. - jek3 From gww@eng.sun.com Tue Mar 27 15:50:47 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.6+Sun/8.13.6) with ESMTP id l2RMokW3004581 for ; Tue, 27 Mar 2007 15:50:47 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2RMof1Q029944 for <@sunmail3mpk.sfbay.sun.com:PSARC-EXT@sun.com>; Tue, 27 Mar 2007 23:50:46 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFL0040B3GL1P00@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Tue, 27 Mar 2007 15:50:45 -0700 (PDT) Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFL000LX3GKE030@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@sun.com (ORCPT PSARC-EXT@sun.com); Tue, 27 Mar 2007 15:50:44 -0700 (PDT) Received: from marduk.eng.sun.com (marduk.SFBay.Sun.COM [129.146.108.224]) by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2RMogOk012446; Tue, 27 Mar 2007 15:50:42 -0700 (PDT) Received: from marduk.eng.sun.com (localhost [127.0.0.1]) by marduk.eng.sun.com (8.13.6+Sun/8.12.11) with ESMTP id l2RNo3LB004801; Tue, 27 Mar 2007 15:50:03 -0800 (PST) Received: (from gww@localhost) by marduk.eng.sun.com (8.13.6+Sun/8.12.11/Submit) id l2RNo3f7004800; Tue, 27 Mar 2007 15:50:03 -0800 (PST) Date: Tue, 27 Mar 2007 15:50:03 -0800 (PST) From: Gary Winiger Subject: Re: PSARC/2007/165 Including CURL with Solaris To: Mark.Phalan@sun.com, Stefan.Teleman@sun.com Cc: PSARC-EXT@sun.com, bart.smaalders@sun.com, unixconsole@yahoo.com Message-id: <200703272350.l2RNo3f7004800@marduk.eng.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 Status: RO Content-Length: 210 > libkrb5 was introduced in build 38 (PSARC 2006/027). It should be > (basically) compatible with the MIT API. Our Kerberos implementation is > based on MIT's. I think this also will need a contract. Gary.. From bart.smaalders@Sun.COM Fri Mar 30 16:35:10 2007 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.eng.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l2UNZAO9023236 for ; Fri, 30 Mar 2007 16:35:10 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id l2U1OR9t000983 for <@sunmail3mpk.sfbay.sun.com:PSARC-EXT@Sun.COM>; Thu, 29 Mar 2007 18:24:27 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JFO00B03ZWRAH00@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@Sun.COM (ORCPT PSARC-EXT@Sun.COM); Thu, 29 Mar 2007 18:24:27 -0700 (PDT) Received: from engmail3mpk.sfbay.Sun.COM ([129.146.11.26]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JFO003MYZWQ9860@nwk-avmta-2.sfbay.sun.com> for PSARC-EXT@Sun.COM (ORCPT PSARC-EXT@Sun.COM); Thu, 29 Mar 2007 18:24:26 -0700 (PDT) Received: from zion.eng.sun.com (zion.SFBay.Sun.COM [129.146.17.75]) by engmail3mpk.sfbay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l2U1OQxK022968; Thu, 29 Mar 2007 18:24:26 -0700 (PDT) Received: from [129.146.228.109] (cyber [129.146.228.109]) by zion.eng.sun.com (8.13.7+Sun/8.13.7) with ESMTP id l2U1OQ9v018668; Thu, 29 Mar 2007 18:24:26 -0700 (PDT) Date: Thu, 29 Mar 2007 18:23:29 -0700 From: Bart Smaalders Subject: Re: PSARC/2007/165 Including CURL with Solaris To: PSARC-EXT@Sun.COM Cc: Stefan Teleman Message-id: <460C6691.5070407@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 2.0b2 (X11/20070227) Status: RO Content-Length: 289 An updated copy of the fast track with corrections (case numbers, 64 bit paths, etc) has been placed in the materials subdirectory. This case was approved at yesterday's meeting. - Bart -- Bart Smaalders Solaris Kernel Performance barts@cyber.eng.sun.com http://blogs.sun.com/barts