From jw137282@sac.sfbay.sun.com Wed Jun 3 03:14:03 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n53AE2R7008287 for ; Wed, 3 Jun 2009 03:14:03 -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.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n53ADqA4016239; Wed, 3 Jun 2009 11:14:01 +0100 (BST) 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 <0KKN00D0LR3BZK00@brm-avmta-1.central.sun.com>; Wed, 03 Jun 2009 04:13:59 -0600 (MDT) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KKN00CFHR3AZ520@brm-avmta-1.central.sun.com>; Wed, 03 Jun 2009 04:13:58 -0600 (MDT) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n53ADv2K006355; Wed, 03 Jun 2009 03:13:57 -0700 (PDT) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n53ADuqa008281; Wed, 03 Jun 2009 03:13:56 -0700 (PDT) Received: (from jw137282@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n53ADuDq008277; Wed, 03 Jun 2009 03:13:56 -0700 (PDT) Date: Wed, 03 Jun 2009 03:13:56 -0700 (PDT) From: James Walker Subject: rtorrent & libtorrent [PSARC/2009/336 FastTrack timeout 06/10/2009] To: PSARC-ext@sun.com Cc: Huawei.Zhang@sun.com Message-id: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 13009 I'm sponsoring this familiarity case for Alex Zhang. The requested release binding is minor. The man pages have been posted in the materials directory. The OpenSSL contract link will be posted after it is approved. Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: rtorrent & libtorent 1.2. Name of Document Author/Supplier: Author: Alex Zhang 1.3 Date of This Document: 03 June, 2009 4. Technical Description libtorent & rtorrent Check List 1.0 Project Information 1.1 Name of project/component libtorrent & rtorrent 1.2 Author of document Huawei.Zhang@Sun.COM 2.0 Project Summary 2.1 Project Description libtorrent is a BitTorrent library written in C++ for *nix, with a focus on high performance and good code. rtorrent is a BitTorrent client for ncurses, using the libtorrent library. 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [ ] Major [*] Minor [ ] Patch or Micro [ ] Unknown -- ARC review required 2.3 Type of project Is this case a Linux Familiarity project? [*] Yes [ ] No 2.4 Originating Community 2.4.1 Community Name libtorrent - Jari Sundell [1] rtorrent - Jari Sundell [1] 2.4.2 Community Involvement Indicate Sun's involvement in the community [ ] Maintainer [ ] Contributor [*] Monitoring Will the project team work with the upstream community to resolve architectural issues of interest to Sun? [*] Yes [ ] No - briefly explain Will we or are we forking from the community? [ ] Yes - ARC review required prior to forking [*] No 3.0 Technical Description 3.1 Installation & Sharable 3.1.1S Solaris Installation - section only required for Solaris Software (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) Does this project follow the Install Locations best practice? [*] Yes [ ] No - ARC review required Does this project install into /usr under [sbin|bin|lib|include|man|share]? [*] Yes [ ] No or N/A Does this project install into /opt? [ ] Yes - explain below [*] No or N/A Does this project install into a different directory structure? [ ] Yes - ARC review required [*] No or N/A Do any of the components of this project conflict with anything under /usr? (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) [ ] Yes - explain below [*] No If conflicts exist then will this project install under /usr/gnu? [ ] Yes [ ] No - ARC review required [*] N/A Is this project installing into /usr/sfw? [ ] Yes - ARC review required [*] No 3.1.1W Windows Installation - section only required for Windows Software (see http://sac.sfbay/WSARC/2002/494 for details) Does this project install software into a :\Program Files\Sun\ or :\Sun\ directory? [ ] Yes [ ] No - ARC review required Does the project use the Windows registry? [ ] Yes [ ] No - ARC review required Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ for the registry key? [ ] Yes [ ] No - ARC review required Is the project's stored location HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? [ ] Yes [ ] No - ARC review required 3.1.2 Share and Sharable Does the module include any components that are used or shared by other projects? [*] Yes [ ] No If yes are these components packaged to be shared with the other FOSS? [*] Yes [ ] No - ARC review required [ ] N/A Are these components already in the Solaris WOS? [ ] Yes [*] No - continue with next section (section 3.2) If yes are these newer versions being delivered? [ ] Yes [ ] No - ARC review required If yes are the newer versions replacing the existing versions? [ ] Yes [ ] No - ARC review required 3.2 Exported Libraries Are libraries being delivered by this project? [*] Yes [ ] No - continue with next section (section 3.3) Are 64-bit versions of the libraries being delivered? [*] Yes [ ] No - ARC review required Are static versions of the libraries being delivered? [ ] Yes - ARC review required [*] No 3.3 Services and the /etc Directory (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) Does the project integrate anything into /etc/init.d or /etc/rc?.d? [ ] Yes - ARC review required [*] No Does the project integrate any new entries into /etc/inittab or /etc/inetd.conf? [ ] Yes - ARC review required [*] No Does the project integrate any private non-public files into /etc/default or /etc/ configuration files? [ ] Yes - ARC review required [*] No Does the service manifests method context grant rights above that of the noaccess user and basic privilege set? [ ] Yes - ARC review required [*] No 3.4 Security 3.4.1 Secure By Default (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for addtional details) Are there any network services provided by this project? [ ] Yes [*] No - continue with the next section (section 3.4.2) Are network services enabled by default? [ ] Yes - ARC review required [ ] No [ ] N/A Are network services automatically enabled by the project during installation? [ ] Yes - ARC review required [ ] No [ ] N/A Are inbound network communications denied by default? [ ] Yes [ ] No - ARC review required [ ] N/A Is inbound data checked to prevent content-based attacks? [ ] Yes [ ] No - ARC review required [ ] N/A Is the outbound receiver authenticated? [ ] Yes [ ] No - ARC review required [ ] N/A Is the receiver authenticated prior to receiving any sensitive outbound communication? [ ] Yes [ ] No - ARC review required [ ] N/A 3.4.2 Authorization (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ for details) Are there any setuid/setgid privileged binaries in the project? [ ] Yes - ARC review required [*] No - continue with next section (section 3.4.3) If yes then are the setuid/setgid privileges handled by the use of roles? [ ] Yes [ ] No - ARC review required 3.4.3 Auditing (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Does this component contain administrative or security enforcing software? [ ] Yes - ARC review required [*] No - continue to next section (section 3.4.4) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Do the components create audit logs detailing what took place including what event took place, who was involved, when the event took place? [ ] Yes - ARC contract and Audit project team review required [ ] No - ARC review required 3.4.4 Authentication (see http://opensolaris.org/os/community/arc/policies/PAM/) Do the components contain any authentication code? [ ] Yes [*] No - continue to next section (section 3.4.5) If yes do the components use PAM (plugable authentication modules) for authentication? [ ] Yes [ ] No - ARC review required If yes is a single PAM session maintained during authentication? [ ] Yes [ ] No - ARC review required If yes are the components sufficiently privileged to allow the requested operations (authentication, password change, process credential manipulation, audit state initialization)? [ ] Yes - briefly describe below [ ] No - ARC review required 3.4.5 Passwords (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) Do any of the components for the project deal with passwords? [ ] Yes [*] No - continue to next section (section 3.4.6) If yes are these passwords entered via the CLI or environment? [ ] Yes - ARC review required [ ] No Are passwords stored within the file system for the component? [ ] Yes [ ] No - continue to next section (section 3.4.6) If yes are the permissions on the file such to protect exposing the password(s)? [ ] Yes [ ] No - ARC review required 3.4.6 General Security Questions (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) Are there any network protocols used by this project? [*] Yes [ ] No - continue with the next section (section 3.5) Do the components use standard network protocols? [*] Yes [ ] No - ARC review required Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [*] No [ ] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [*] No [ ] N/A 3.5 Networking Do the components access the network? [*] Yes [ ] No - continue with the next section (section 3.6) If yes do the components support IPv6? [*] Yes [ ] No - ARC review required 3.6 Core Solaris Components Do the components of this project compete with or duplicate core Solaris components? [ ] Yes - ARC review required [*] No Examples of Core Solaris Components include but are not limited to: Secure By Default Authorizations PAM -- Plugable Authentication Module Privilege PRM -- Process Rights Management -- Privilege Audit xVm -- Virtualization zones / Solaris Containers PRM -- Process Rights Management RBAC -- Role Based Access Control TX / Trusted Extensions ZFS SMF -- Service Management Facility FMA -- Fault Management Architecture SCF -- Smart Card Facility IPsec 4.0 Interfaces 4.1 Exported Interfaces Interface Name Classification Comments --------------------------- -------------- ------------------- SUNWrtorrent Uncommitted Package /usr/bin/rtorrent Uncommitted rtorrent command SUNWlibtorrent Uncommitted Package /usr/include/torrent/ Uncommitted Header file directory /usr/lib/libtorrent.so Uncommitted libtorrent Library /usr/lib/libtorrent.so.9 Uncommitted libtorrent Library /usr/lib/libtorrent.so.9.2.0 Uncommitted libtorrent Library /usr/lib/64/libtorrent* Uncommitted 64-bit Library and links /usr/lib/pkgconfig/libtorrent.pc Uncommitted pkgconfig script * /64 equals sparcv9 and amd64 4.2 Imported Interfaces Interface Name Classification Comments -------------------- -------------- --------------- SUNWcurl Uncommitted C-URL Wrappers Library SUNWlibC Uncommitted Sun Workshop Compilers Bundled libC SUNWopensslr Volatile PSARC/2003/500 SUNWsigcpp Uncommitted typesafe callback system for C++ SUNWncurses Uncommitted A CRT screen handling package SUNWlibmsr Committed Math & Microtasking Libraries (Root) Appendix A - References [1] http://libtorrent.rakshasa.no/ OSR ID# 11082 11083 RFE ID# 6814041 6814042 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From andras.barna@gmail.com Wed Jun 3 03:25:40 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n53APdl0008407 for ; Wed, 3 Jun 2009 03:25:39 -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.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n53APIRR023692; Wed, 3 Jun 2009 11:25:36 +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 <0KKN00F0NRMM4T00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 03 Jun 2009 03:25:34 -0700 (PDT) Received: from sca-ea-mail-1.sun.com ([192.18.43.24]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KKN00BPIRML3T50@nwk-avmta-1.sfbay.Sun.COM>; Wed, 03 Jun 2009 03:25:33 -0700 (PDT) Received: from relay15i.sun.com (ip125.net129179-4.block1.us.syntegra.com [129.179.4.125]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n53APXDu019372; Wed, 03 Jun 2009 10:25:33 +0000 (GMT) Received: from mmp14es.mmp.us.syntegra.com ([160.41.208.14] [160.41.208.14]) by relay15i.sun.com with ESMTP id BT-MMP-4086254; Wed, 03 Jun 2009 10:25:33 +0000 (Z) Received: from relay13i.sun.com (relay13i.sun.com [129.179.4.123]) by mmp14es.mmp.us.syntegra.com with ESMTP id BT-MMP-144595; Wed, 03 Jun 2009 10:25:32 +0000 (Z) Received: from mail-ew0-f157.google.com ([209.85.219.157] [209.85.219.157]) by relay1i.sun.com with ESMTP id BT-MMP-845494; Wed, 03 Jun 2009 10:25:31 +0000 (Z) Received: by ewy1 with SMTP id 1so10452556ewy.8 for ; Wed, 03 Jun 2009 03:25:25 -0700 (PDT) Received: by 10.216.45.73 with SMTP id o51mr256711web.10.1244024725300; Wed, 03 Jun 2009 03:25:25 -0700 (PDT) Date: Wed, 03 Jun 2009 13:25:25 +0300 From: Andras Barna Subject: Re: rtorrent & libtorrent [PSARC/2009/336 FastTrack timeout 06/10/2009] In-reply-to: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> To: James Walker Cc: PSARC-ext@sun.com, Huawei.Zhang@sun.com Message-id: <56dc2e760906030325v1bac1da8ha099414c951a5ef3@mail.gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=nQQrbDMVsEXPTNx4RgYSb6h+SnYkUjbNS7vX/x9Rpu8=; b=UjZuFo2/xCQC5xW1OPNuQKol8IDvd/1eQa+hPxJYEmNLfGzuCNjTQ55DIeZaEdrTqu i+1edmuxtqwWmfvp5gbxl7MlgtZJOJeBXIh7PWg+0cRGcaOzxaPphvCbic0lXUZmKIC8 uhp/lGN58b5Inneqd5orquTm8sZt/rA4UrvAw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TL/Ka4ahuwvxXdoHH0SoxKS2xE1Llor1jrer7F/PGbdz9damd8PjCsTYfcoIp40eWs RDFwqUJST18rCgths5ec78EJtZUDBM/74n9elZvkP31WaFqzrW8OhZHUvFJb5aJ/xwTx xyl7SSxamuCYtlQ57wc8eApuF7VzlyWpYhzcg= X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Antispam: No, score=-2.6/5.0, scanned in 0.317sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by sac.sfbay.sun.com id n53APdl0008407 Status: RO Content-Length: 14963 i'm not sure if it's a good idea to package rakshasa's libtorrent as SUNWlibtorrent because this may confuse people. see: http://en.wikipedia.org/wiki/Libtorrent * libTorrent (Rakshasa) which powers rTorrent. * Libtorrent (Rasterbar) which powers BTG, Deluge, Free Download Manager, Halite, Linkage, Miro, qBittorrent, SharkTorrent, and many more. + i'm dont know if something uses this libtorrent except rtorrent and would be nice too see SMF stuff for this. On Wed, Jun 3, 2009 at 1:13 PM, James Walker wrote: > I'm sponsoring this familiarity case for Alex Zhang. The requested > release binding is minor. The man pages have been posted in the > materials directory. The OpenSSL contract link will be posted after > it is approved. > > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction >    1.1. Project/Component Working Name: >         rtorrent & libtorent >    1.2. Name of Document Author/Supplier: >         Author:  Alex Zhang >    1.3  Date of This Document: >        03 June, 2009 > 4. Technical Description > libtorent & rtorrent Check List > 1.0 Project Information > 1.1 Name of project/component >    libtorrent & rtorrent > > 1.2 Author of document >    Huawei.Zhang@Sun.COM > > 2.0 Project Summary >  2.1 Project Description >    libtorrent is a BitTorrent library written in C++ for *nix, with a focus on high performance and good code. > >    rtorrent is a BitTorrent client for ncurses, using the libtorrent library. > >  2.2 Release binding >      What is is the release binding? >      (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >      [ ] Major >      [*] Minor >      [ ] Patch or Micro >      [ ] Unknown -- ARC review required > >  2.3 Type of project >      Is this case a Linux Familiarity project? >      [*] Yes >      [ ] No > >  2.4 Originating Community >    2.4.1 Community Name >      libtorrent - Jari Sundell [1] >      rtorrent - Jari Sundell [1] > >    2.4.2 Community Involvement >      Indicate Sun's involvement in the community >      [ ] Maintainer >      [ ] Contributor >      [*] Monitoring > >      Will the project team work with the upstream community to resolve >      architectural issues of interest to Sun? >      [*] Yes >      [ ] No - briefly explain > >      Will we or are we forking from the community? >      [ ] Yes - ARC review required prior to forking >      [*] No > > 3.0 Technical Description >  3.1 Installation & Sharable >    3.1.1S Solaris Installation - section only required for Solaris Software >      (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) >      Does this project follow the Install Locations best practice? >      [*] Yes >      [ ] No - ARC review required > >      Does this project install into /usr under [sbin|bin|lib|include|man|share]? >      [*] Yes >      [ ] No or N/A > >      Does this project install into /opt? >      [ ] Yes - explain below >      [*] No or N/A > >      Does this project install into a different directory structure? >      [ ] Yes - ARC review required >      [*] No or N/A > >      Do any of the components of this project conflict with anything under /usr? >      (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) >      [ ] Yes - explain below >      [*] No > >      If conflicts exist then will this project install under /usr/gnu? >      [ ] Yes >      [ ] No - ARC review required >      [*] N/A > >      Is this project installing into /usr/sfw? >      [ ] Yes - ARC review required >      [*] No > >    3.1.1W Windows Installation - section only required for Windows Software >      (see http://sac.sfbay/WSARC/2002/494 for details) >      Does this project install software into a >      :\Program Files\Sun\ or :\Sun\ >      directory? >      [ ] Yes >      [ ] No - ARC review required > >      Does the project use the Windows registry? >      [ ] Yes >      [ ] No - ARC review required > >      Does the project use >      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ >      for the registry key? >      [ ] Yes >      [ ] No - ARC review required > >      Is the project's stored location >      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? >      [ ] Yes >      [ ] No - ARC review required > >    3.1.2 Share and Sharable >      Does the module include any components that are used or shared by >      other projects? >      [*] Yes >      [ ] No > >      If yes are these components packaged to be shared with the other FOSS? >      [*] Yes >      [ ] No - ARC review required >      [ ] N/A > >      Are these components already in the Solaris WOS? >      [ ] Yes >      [*] No - continue with next section (section 3.2) > >      If yes are these newer versions being delivered? >      [ ] Yes >      [ ] No - ARC review required > >      If yes are the newer versions replacing the existing versions? >      [ ] Yes >      [ ] No - ARC review required > >  3.2 Exported Libraries >      Are libraries being delivered by this project? >      [*] Yes >      [ ] No - continue with next section (section 3.3) > >      Are 64-bit versions of the libraries being delivered? >      [*] Yes >      [ ] No - ARC review required > >      Are static versions of the libraries being delivered? >      [ ] Yes - ARC review required >      [*] No > >  3.3 Services and the /etc Directory >      (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >      Does the project integrate anything into /etc/init.d or /etc/rc?.d? >      [ ] Yes - ARC review required >      [*] No > >      Does the project integrate any new entries into /etc/inittab or >      /etc/inetd.conf? >      [ ] Yes - ARC review required >      [*] No > >      Does the project integrate any private non-public files into /etc/default >      or /etc/ configuration files? >      [ ] Yes - ARC review required >      [*] No > >      Does the service manifests method context grant rights above that >      of the noaccess user and basic privilege set? >      [ ] Yes - ARC review required >      [*] No > >  3.4 Security >    3.4.1 Secure By Default >      (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) >      (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) >      (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >       addtional details) >      Are there any network services provided by this project? >      [ ] Yes >      [*] No - continue with the next section (section 3.4.2) > >      Are network services enabled by default? >      [ ] Yes - ARC review required >      [ ] No >      [ ] N/A > >      Are network services automatically enabled by the project during installation? >      [ ] Yes - ARC review required >      [ ] No >      [ ] N/A > >      Are inbound network communications denied by default? >      [ ] Yes >      [ ] No - ARC review required >      [ ] N/A > >      Is inbound data checked to prevent content-based attacks? >      [ ] Yes >      [ ] No - ARC review required >      [ ] N/A > >      Is the outbound receiver authenticated? >      [ ] Yes >      [ ] No - ARC review required >      [ ] N/A > >      Is the receiver authenticated prior to receiving any sensitive outbound communication? >      [ ] Yes >      [ ] No - ARC review required >      [ ] N/A > >    3.4.2 Authorization >      (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >           http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and >           http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >           for details) >      Are there any setuid/setgid privileged binaries in the project? >      [ ] Yes - ARC review required >      [*] No - continue with next section (section 3.4.3) > >      If yes then are the setuid/setgid privileges handled by the use of roles? >      [ ] Yes >      [ ] No - ARC review required > >    3.4.3 Auditing >      (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) >      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) >      Does this component contain administrative or security enforcing software? >      [ ] Yes - ARC review required >      [*] No - continue to next section (section 3.4.4) > >      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) >      Do the components create audit logs detailing what took place including what event >      took place, who was involved, when the event took place? >      [ ] Yes - ARC contract and Audit project team review required >      [ ] No - ARC review required > > >    3.4.4 Authentication >      (see http://opensolaris.org/os/community/arc/policies/PAM/) >      Do the components contain any authentication code? >      [ ] Yes >      [*] No - continue to next section (section 3.4.5) > >      If yes do the components use PAM (plugable authentication modules) for authentication? >      [ ] Yes >      [ ] No - ARC review required > >      If yes is a single PAM session maintained during authentication? >      [ ] Yes >      [ ] No - ARC review required > >      If yes are the components sufficiently privileged to allow the requested >      operations (authentication, password change, process credential manipulation, >      audit state initialization)? >      [ ] Yes - briefly describe below >      [ ] No - ARC review required > >    3.4.5 Passwords >      (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >           http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) >      Do any of the components for the project deal with passwords? >      [ ] Yes >      [*] No - continue to next section (section 3.4.6) > >      If yes are these passwords entered via the CLI or environment? >      [ ] Yes - ARC review required >      [ ] No > >      Are passwords stored within the file system for the component? >      [ ] Yes >      [ ] No - continue to next section (section 3.4.6) > >      If yes are the permissions on the file such to protect exposing the password(s)? >      [ ] Yes >      [ ] No - ARC review required > >    3.4.6 General Security Questions >      (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) >      Are there any network protocols used by this project? >      [*] Yes >      [ ] No - continue with the next section (section 3.5) > >      Do the components use standard network protocols? >      [*] Yes >      [ ] No - ARC review required > >      Do network services for the project make decisions based upon user, host or >      service identities? >      [ ] Yes - explain below >      [*] No >      [ ] N/A > >      Do the components make use of secret information during authentication and/or >      authorization? >      [ ] Yes - explain below >      [*] No >      [ ] N/A > >  3.5 Networking >      Do the components access the network? >      [*] Yes >      [ ] No - continue with the next section (section 3.6) > >      If yes do the components support IPv6? >      [*] Yes >      [ ] No - ARC review required > >  3.6 Core Solaris Components >      Do the components of this project compete with or duplicate core >      Solaris components? >      [ ] Yes - ARC review required >      [*] No > >      Examples of Core Solaris Components include but are not limited to: > >        Secure By Default >        Authorizations >        PAM -- Plugable Authentication Module >        Privilege >        PRM -- Process Rights Management -- Privilege >        Audit >        xVm -- Virtualization >        zones / Solaris Containers >        PRM -- Process Rights Management >        RBAC -- Role Based Access Control >        TX / Trusted Extensions >        ZFS >        SMF -- Service Management Facility >        FMA -- Fault Management Architecture >        SCF -- Smart Card Facility >        IPsec > > 4.0 Interfaces >  4.1 Exported Interfaces > >    Interface Name               Classification Comments >    ---------------------------  -------------- ------------------- >    SUNWrtorrent                 Uncommitted    Package >    /usr/bin/rtorrent            Uncommitted    rtorrent command >    SUNWlibtorrent               Uncommitted    Package >    /usr/include/torrent/        Uncommitted    Header file directory >    /usr/lib/libtorrent.so       Uncommitted    libtorrent Library >    /usr/lib/libtorrent.so.9     Uncommitted    libtorrent Library >    /usr/lib/libtorrent.so.9.2.0 Uncommitted    libtorrent Library >    /usr/lib/64/libtorrent*      Uncommitted    64-bit Library and links >    /usr/lib/pkgconfig/libtorrent.pc >                                 Uncommitted    pkgconfig script > >    * /64 equals sparcv9 and amd64 > >  4.2 Imported Interfaces > >    Interface Name       Classification Comments >    -------------------- -------------- --------------- >    SUNWcurl             Uncommitted    C-URL Wrappers Library >    SUNWlibC             Uncommitted    Sun Workshop Compilers Bundled libC >    SUNWopensslr         Volatile       PSARC/2003/500 >    SUNWsigcpp           Uncommitted    typesafe callback system for C++ >    SUNWncurses          Uncommitted    A CRT screen handling package >    SUNWlibmsr           Committed      Math & Microtasking Libraries (Root) > > Appendix A - References >  [1] http://libtorrent.rakshasa.no/ > >  OSR ID# 11082 11083 >  RFE ID# 6814041 6814042 > > 6. Resources and Schedule >    6.4. Steering Committee requested information >        6.4.1. Consolidation C-team Name: >                SFW >    6.5. ARC review type: FastTrack >    6.6. ARC Exposure: open > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc@opensolaris.org > -- Andy http://blog.sartek.net From Huawei.Zhang@sun.com Wed Jun 3 19:41:49 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n542fm2j022062 for ; Wed, 3 Jun 2009 19:41:49 -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.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n542fgsu005182 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 4 Jun 2009 03:41:48 +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 <0KKP00G030TNQH00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 03 Jun 2009 19:41:47 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KKP00G620TLI700@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 03 Jun 2009 19:41:46 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n542fjZc016067 for ; Thu, 04 Jun 2009 02:41:45 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KKP00C000RNXS00@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 04 Jun 2009 10:41:45 +0800 (SGT) Received: from [129.158.144.119] ([unknown] [129.158.144.119]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KKP009230TJX0A0@mail-apac.sun.com>; Thu, 04 Jun 2009 10:41:44 +0800 (SGT) Date: Thu, 04 Jun 2009 10:41:42 +0800 From: alex zhang Subject: Re: rtorrent & libtorrent [PSARC/2009/336 FastTrack timeout 06/10/2009] In-reply-to: <56dc2e760906030325v1bac1da8ha099414c951a5ef3@mail.gmail.com> Sender: Huawei.Zhang@sun.com To: Andras Barna Cc: James Walker , PSARC-ext@sun.com Message-id: <381F38E0-FEC4-495D-B7B2-E54102F4682A@Sun.COM> MIME-version: 1.0 X-Mailer: Apple Mail (2.935.3) Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> <56dc2e760906030325v1bac1da8ha099414c951a5ef3@mail.gmail.com> Status: RO Content-Length: 15086 Hi, all Thanks for quick review. As far as my knowledge, now libTorrent (Rakshasa) don't have other client except rtorrent. For this problem, I have two solve suggestion: 1. only export SUNWrtorrent, don't export SUNWlibtorrent, compile it as a static library, which only used by rtorrent. 2. change SUNWlibtorrent to SUNWrlibtorrent. What is your advice? Thanks - Alex On Jun 3, 2009, at 6:25 PM, Andras Barna wrote: > i'm not sure if it's a good idea to package rakshasa's libtorrent as > SUNWlibtorrent because this may confuse people. see: > http://en.wikipedia.org/wiki/Libtorrent > > * libTorrent (Rakshasa) which powers rTorrent. > * Libtorrent (Rasterbar) which powers BTG, Deluge, Free Download > Manager, Halite, Linkage, Miro, qBittorrent, SharkTorrent, and many > more. > > + i'm dont know if something uses this libtorrent except rtorrent > > and would be nice too see SMF stuff for this. > > On Wed, Jun 3, 2009 at 1:13 PM, James Walker > wrote: >> I'm sponsoring this familiarity case for Alex Zhang. The requested >> release binding is minor. The man pages have been posted in the >> materials directory. The OpenSSL contract link will be posted after >> it is approved. >> >> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >> This information is Copyright 2009 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> rtorrent & libtorent >> 1.2. Name of Document Author/Supplier: >> Author: Alex Zhang >> 1.3 Date of This Document: >> 03 June, 2009 >> 4. Technical Description >> libtorent & rtorrent Check List >> 1.0 Project Information >> 1.1 Name of project/component >> libtorrent & rtorrent >> >> 1.2 Author of document >> Huawei.Zhang@Sun.COM >> >> 2.0 Project Summary >> 2.1 Project Description >> libtorrent is a BitTorrent library written in C++ for *nix, with >> a focus on high performance and good code. >> >> rtorrent is a BitTorrent client for ncurses, using the >> libtorrent library. >> >> 2.2 Release binding >> What is is the release binding? >> (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >> [ ] Major >> [*] Minor >> [ ] Patch or Micro >> [ ] Unknown -- ARC review required >> >> 2.3 Type of project >> Is this case a Linux Familiarity project? >> [*] Yes >> [ ] No >> >> 2.4 Originating Community >> 2.4.1 Community Name >> libtorrent - Jari Sundell [1] >> rtorrent - Jari Sundell [1] >> >> 2.4.2 Community Involvement >> Indicate Sun's involvement in the community >> [ ] Maintainer >> [ ] Contributor >> [*] Monitoring >> >> Will the project team work with the upstream community to >> resolve >> architectural issues of interest to Sun? >> [*] Yes >> [ ] No - briefly explain >> >> Will we or are we forking from the community? >> [ ] Yes - ARC review required prior to forking >> [*] No >> >> 3.0 Technical Description >> 3.1 Installation & Sharable >> 3.1.1S Solaris Installation - section only required for Solaris >> Software >> (see http://opensolaris.org/os/community/arc/policies/install-locations/ >> for details) >> Does this project follow the Install Locations best practice? >> [*] Yes >> [ ] No - ARC review required >> >> Does this project install into /usr under [sbin|bin|lib| >> include|man|share]? >> [*] Yes >> [ ] No or N/A >> >> Does this project install into /opt? >> [ ] Yes - explain below >> [*] No or N/A >> >> Does this project install into a different directory structure? >> [ ] Yes - ARC review required >> [*] No or N/A >> >> Do any of the components of this project conflict with >> anything under /usr? >> (see http://opensolaris.org/os/community/arc/caselog/2007/047/ >> for details) >> [ ] Yes - explain below >> [*] No >> >> If conflicts exist then will this project install under /usr/ >> gnu? >> [ ] Yes >> [ ] No - ARC review required >> [*] N/A >> >> Is this project installing into /usr/sfw? >> [ ] Yes - ARC review required >> [*] No >> >> 3.1.1W Windows Installation - section only required for Windows >> Software >> (see http://sac.sfbay/WSARC/2002/494 for details) >> Does this project install software into a >> :\Program Files\Sun\ or : >> \Sun\ >> directory? >> [ ] Yes >> [ ] No - ARC review required >> >> Does the project use the Windows registry? >> [ ] Yes >> [ ] No - ARC review required >> >> Does the project use >> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ >> for the registry key? >> [ ] Yes >> [ ] No - ARC review required >> >> Is the project's stored location >> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\ >> \\Path? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.1.2 Share and Sharable >> Does the module include any components that are used or shared >> by >> other projects? >> [*] Yes >> [ ] No >> >> If yes are these components packaged to be shared with the >> other FOSS? >> [*] Yes >> [ ] No - ARC review required >> [ ] N/A >> >> Are these components already in the Solaris WOS? >> [ ] Yes >> [*] No - continue with next section (section 3.2) >> >> If yes are these newer versions being delivered? >> [ ] Yes >> [ ] No - ARC review required >> >> If yes are the newer versions replacing the existing versions? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.2 Exported Libraries >> Are libraries being delivered by this project? >> [*] Yes >> [ ] No - continue with next section (section 3.3) >> >> Are 64-bit versions of the libraries being delivered? >> [*] Yes >> [ ] No - ARC review required >> >> Are static versions of the libraries being delivered? >> [ ] Yes - ARC review required >> [*] No >> >> 3.3 Services and the /etc Directory >> (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >> Does the project integrate anything into /etc/init.d or /etc/ >> rc?.d? >> [ ] Yes - ARC review required >> [*] No >> >> Does the project integrate any new entries into /etc/inittab or >> /etc/inetd.conf? >> [ ] Yes - ARC review required >> [*] No >> >> Does the project integrate any private non-public files into / >> etc/default >> or /etc/ configuration files? >> [ ] Yes - ARC review required >> [*] No >> >> Does the service manifests method context grant rights above >> that >> of the noaccess user and basic privilege set? >> [ ] Yes - ARC review required >> [*] No >> >> 3.4 Security >> 3.4.1 Secure By Default >> (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ >> for details) >> (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ >> for details) >> (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ >> for >> addtional details) >> Are there any network services provided by this project? >> [ ] Yes >> [*] No - continue with the next section (section 3.4.2) >> >> Are network services enabled by default? >> [ ] Yes - ARC review required >> [ ] No >> [ ] N/A >> >> Are network services automatically enabled by the project >> during installation? >> [ ] Yes - ARC review required >> [ ] No >> [ ] N/A >> >> Are inbound network communications denied by default? >> [ ] Yes >> [ ] No - ARC review required >> [ ] N/A >> >> Is inbound data checked to prevent content-based attacks? >> [ ] Yes >> [ ] No - ARC review required >> [ ] N/A >> >> Is the outbound receiver authenticated? >> [ ] Yes >> [ ] No - ARC review required >> [ ] N/A >> >> Is the receiver authenticated prior to receiving any sensitive >> outbound communication? >> [ ] Yes >> [ ] No - ARC review required >> [ ] N/A >> >> 3.4.2 Authorization >> (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ >> and >> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >> and >> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >> for details) >> Are there any setuid/setgid privileged binaries in the project? >> [ ] Yes - ARC review required >> [*] No - continue with next section (section 3.4.3) >> >> If yes then are the setuid/setgid privileges handled by the >> use of roles? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.4.3 Auditing >> (see http://opensolaris.org/os/community/arc/policies/audit-policy/ >> for details) >> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >> for details) >> Does this component contain administrative or security >> enforcing software? >> [ ] Yes - ARC review required >> [*] No - continue to next section (section 3.4.4) >> >> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >> for details) >> Do the components create audit logs detailing what took place >> including what event >> took place, who was involved, when the event took place? >> [ ] Yes - ARC contract and Audit project team review required >> [ ] No - ARC review required >> >> >> 3.4.4 Authentication >> (see http://opensolaris.org/os/community/arc/policies/PAM/) >> Do the components contain any authentication code? >> [ ] Yes >> [*] No - continue to next section (section 3.4.5) >> >> If yes do the components use PAM (plugable authentication >> modules) for authentication? >> [ ] Yes >> [ ] No - ARC review required >> >> If yes is a single PAM session maintained during authentication? >> [ ] Yes >> [ ] No - ARC review required >> >> If yes are the components sufficiently privileged to allow the >> requested >> operations (authentication, password change, process >> credential manipulation, >> audit state initialization)? >> [ ] Yes - briefly describe below >> [ ] No - ARC review required >> >> 3.4.5 Passwords >> (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ >> and >> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ >> for details) >> Do any of the components for the project deal with passwords? >> [ ] Yes >> [*] No - continue to next section (section 3.4.6) >> >> If yes are these passwords entered via the CLI or environment? >> [ ] Yes - ARC review required >> [ ] No >> >> Are passwords stored within the file system for the component? >> [ ] Yes >> [ ] No - continue to next section (section 3.4.6) >> >> If yes are the permissions on the file such to protect >> exposing the password(s)? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.4.6 General Security Questions >> (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ >> for details) >> Are there any network protocols used by this project? >> [*] Yes >> [ ] No - continue with the next section (section 3.5) >> >> Do the components use standard network protocols? >> [*] Yes >> [ ] No - ARC review required >> >> Do network services for the project make decisions based upon >> user, host or >> service identities? >> [ ] Yes - explain below >> [*] No >> [ ] N/A >> >> Do the components make use of secret information during >> authentication and/or >> authorization? >> [ ] Yes - explain below >> [*] No >> [ ] N/A >> >> 3.5 Networking >> Do the components access the network? >> [*] Yes >> [ ] No - continue with the next section (section 3.6) >> >> If yes do the components support IPv6? >> [*] Yes >> [ ] No - ARC review required >> >> 3.6 Core Solaris Components >> Do the components of this project compete with or duplicate core >> Solaris components? >> [ ] Yes - ARC review required >> [*] No >> >> Examples of Core Solaris Components include but are not >> limited to: >> >> Secure By Default >> Authorizations >> PAM -- Plugable Authentication Module >> Privilege >> PRM -- Process Rights Management -- Privilege >> Audit >> xVm -- Virtualization >> zones / Solaris Containers >> PRM -- Process Rights Management >> RBAC -- Role Based Access Control >> TX / Trusted Extensions >> ZFS >> SMF -- Service Management Facility >> FMA -- Fault Management Architecture >> SCF -- Smart Card Facility >> IPsec >> >> 4.0 Interfaces >> 4.1 Exported Interfaces >> >> Interface Name Classification Comments >> --------------------------- -------------- ------------------- >> SUNWrtorrent Uncommitted Package >> /usr/bin/rtorrent Uncommitted rtorrent command >> SUNWlibtorrent Uncommitted Package >> /usr/include/torrent/ Uncommitted Header file directory >> /usr/lib/libtorrent.so Uncommitted libtorrent Library >> /usr/lib/libtorrent.so.9 Uncommitted libtorrent Library >> /usr/lib/libtorrent.so.9.2.0 Uncommitted libtorrent Library >> /usr/lib/64/libtorrent* Uncommitted 64-bit Library and >> links >> /usr/lib/pkgconfig/libtorrent.pc >> Uncommitted pkgconfig script >> >> * /64 equals sparcv9 and amd64 >> >> 4.2 Imported Interfaces >> >> Interface Name Classification Comments >> -------------------- -------------- --------------- >> SUNWcurl Uncommitted C-URL Wrappers Library >> SUNWlibC Uncommitted Sun Workshop Compilers >> Bundled libC >> SUNWopensslr Volatile PSARC/2003/500 >> SUNWsigcpp Uncommitted typesafe callback system for >> C++ >> SUNWncurses Uncommitted A CRT screen handling package >> SUNWlibmsr Committed Math & Microtasking >> Libraries (Root) >> >> Appendix A - References >> [1] http://libtorrent.rakshasa.no/ >> >> OSR ID# 11082 11083 >> RFE ID# 6814041 6814042 >> >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> SFW >> 6.5. ARC review type: FastTrack >> 6.6. ARC Exposure: open >> >> _______________________________________________ >> opensolaris-arc mailing list >> opensolaris-arc@opensolaris.org >> > > > > -- > Andy > http://blog.sartek.net From andras.barna@gmail.com Thu Jun 4 00:52:20 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n547qJ6O023897 for ; Thu, 4 Jun 2009 00:52:20 -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.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n547qAT8000896; Thu, 4 Jun 2009 08:52:17 +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 <0KKP00E0JF74P900@nwk-avmta-2.sfbay.sun.com>; Thu, 04 Jun 2009 00:52:16 -0700 (PDT) Received: from sca-ea-mail-3.sun.com ([192.18.43.21]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KKP00C5CF74IA20@nwk-avmta-2.sfbay.sun.com>; Thu, 04 Jun 2009 00:52:16 -0700 (PDT) Received: from relay44i.sun.com ([192.5.209.118]) by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n547nmVr011271; Thu, 04 Jun 2009 07:52:15 +0000 (GMT) Received: from mmp41es.mmp.us.syntegra.com ([160.41.221.10] [160.41.221.10]) by relay44i.sun.com with ESMTP id BT-MMP-225357; Thu, 04 Jun 2009 07:52:01 +0000 (Z) Received: from relay45i.sun.com (relay45i.sun.com [192.5.209.94]) by mmp41es.mmp.us.syntegra.com with ESMTP id BT-MMP-47419093; Thu, 04 Jun 2009 07:51:59 +0000 (Z) Received: from mail-ew0-f205.google.com ([209.85.219.205] [209.85.219.205]) by relay4i.sun.com with ESMTP id BT-MMP-20115699; Thu, 04 Jun 2009 07:51:59 +0000 (Z) Received: by ewy1 with SMTP id 1so903186ewy.8 for ; Thu, 04 Jun 2009 00:51:44 -0700 (PDT) Received: by 10.216.21.205 with SMTP id r55mr670823wer.175.1244101904726; Thu, 04 Jun 2009 00:51:44 -0700 (PDT) Date: Thu, 04 Jun 2009 10:51:44 +0300 From: Andras Barna Subject: Re: rtorrent & libtorrent [PSARC/2009/336 FastTrack timeout 06/10/2009] In-reply-to: <381F38E0-FEC4-495D-B7B2-E54102F4682A@Sun.COM> To: alex zhang Cc: James Walker , PSARC-ext@sun.com Message-id: <56dc2e760906040051l4a05d9a2o34924b2e9fb0dab9@mail.gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Pe+cG15GTTM3BK1N1X6J98/8OszLmCKhhrXYfLY1xk0=; b=qwzgib8SSaefAScEx20e1UrHSciCxYBChJ3NrepdGGjybPuMQUnXO5536nEKX/+JIs 366WHE38vz8Hdo66m5re3rGiBb6S3gTBwKWq1mNNDjk64gdYTl7KOehc9w812NbPGzVy UFOZmMKOJ/LjHcydV7AfDlnihGAlIIdJTwEbc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=nCIADxhFg9ulZg6+D9bdl7W2ohRLdo7AN1d2HUgslzGZKvlXwPVHPY9+MmXeIGI37o ywISzCFRWWFGwu0kI0Ama7yHOtvlRiO6g1OyCLHnjbq/ap1H+iDhPepbrc+d0FMaNvWH /5YA/5vdqkWW5ptExOs159geW6e5G2ic7KJy0= X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Antispam: No, score=-2.6/5.0, scanned in 1.604sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> <56dc2e760906030325v1bac1da8ha099414c951a5ef3@mail.gmail.com> <381F38E0-FEC4-495D-B7B2-E54102F4682A@Sun.COM> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by sac.sfbay.sun.com id n547qJ6O023897 Status: RO Content-Length: 16091 i'd take 2. because no one know the future.. maybe it'll useful some day. (you are renaming libtorrent.so too, right?) thanks On Thu, Jun 4, 2009 at 5:41 AM, alex zhang wrote: > Hi, all > >   Thanks for quick review. > >   As far as my knowledge, now libTorrent (Rakshasa) don't have other client > except rtorrent. > >   For this problem, I have two solve suggestion: > 1. only export SUNWrtorrent, don't export SUNWlibtorrent, compile it as a > static library, which only used by rtorrent. > 2. change SUNWlibtorrent to SUNWrlibtorrent. > >  What is your advice? > > Thanks > - Alex > > On Jun 3, 2009, at 6:25 PM, Andras Barna wrote: > >> i'm not sure if it's a good idea to package rakshasa's libtorrent as >> SUNWlibtorrent because this may confuse people. see: >> http://en.wikipedia.org/wiki/Libtorrent >> >>   * libTorrent (Rakshasa) which powers rTorrent. >>   * Libtorrent (Rasterbar) which powers BTG, Deluge, Free Download >> Manager, Halite, Linkage, Miro, qBittorrent, SharkTorrent, and many >> more. >> >> + i'm dont know if something uses this libtorrent except rtorrent >> >> and would be nice too see SMF stuff for this. >> >> On Wed, Jun 3, 2009 at 1:13 PM, James Walker >> wrote: >>> >>> I'm sponsoring this familiarity case for Alex Zhang. The requested >>> release binding is minor. The man pages have been posted in the >>> materials directory. The OpenSSL contract link will be posted after >>> it is approved. >>> >>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>> This information is Copyright 2009 Sun Microsystems >>> 1. Introduction >>>   1.1. Project/Component Working Name: >>>        rtorrent & libtorent >>>   1.2. Name of Document Author/Supplier: >>>        Author:  Alex Zhang >>>   1.3  Date of This Document: >>>       03 June, 2009 >>> 4. Technical Description >>> libtorent & rtorrent Check List >>> 1.0 Project Information >>> 1.1 Name of project/component >>>   libtorrent & rtorrent >>> >>> 1.2 Author of document >>>   Huawei.Zhang@Sun.COM >>> >>> 2.0 Project Summary >>>  2.1 Project Description >>>   libtorrent is a BitTorrent library written in C++ for *nix, with a >>> focus on high performance and good code. >>> >>>   rtorrent is a BitTorrent client for ncurses, using the libtorrent >>> library. >>> >>>  2.2 Release binding >>>     What is is the release binding? >>>     (see >>> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >>>     [ ] Major >>>     [*] Minor >>>     [ ] Patch or Micro >>>     [ ] Unknown -- ARC review required >>> >>>  2.3 Type of project >>>     Is this case a Linux Familiarity project? >>>     [*] Yes >>>     [ ] No >>> >>>  2.4 Originating Community >>>   2.4.1 Community Name >>>     libtorrent - Jari Sundell [1] >>>     rtorrent - Jari Sundell [1] >>> >>>   2.4.2 Community Involvement >>>     Indicate Sun's involvement in the community >>>     [ ] Maintainer >>>     [ ] Contributor >>>     [*] Monitoring >>> >>>     Will the project team work with the upstream community to resolve >>>     architectural issues of interest to Sun? >>>     [*] Yes >>>     [ ] No - briefly explain >>> >>>     Will we or are we forking from the community? >>>     [ ] Yes - ARC review required prior to forking >>>     [*] No >>> >>> 3.0 Technical Description >>>  3.1 Installation & Sharable >>>   3.1.1S Solaris Installation - section only required for Solaris >>> Software >>>     (see >>> http://opensolaris.org/os/community/arc/policies/install-locations/ for >>> details) >>>     Does this project follow the Install Locations best practice? >>>     [*] Yes >>>     [ ] No - ARC review required >>> >>>     Does this project install into /usr under >>> [sbin|bin|lib|include|man|share]? >>>     [*] Yes >>>     [ ] No or N/A >>> >>>     Does this project install into /opt? >>>     [ ] Yes - explain below >>>     [*] No or N/A >>> >>>     Does this project install into a different directory structure? >>>     [ ] Yes - ARC review required >>>     [*] No or N/A >>> >>>     Do any of the components of this project conflict with anything under >>> /usr? >>>     (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for >>> details) >>>     [ ] Yes - explain below >>>     [*] No >>> >>>     If conflicts exist then will this project install under /usr/gnu? >>>     [ ] Yes >>>     [ ] No - ARC review required >>>     [*] N/A >>> >>>     Is this project installing into /usr/sfw? >>>     [ ] Yes - ARC review required >>>     [*] No >>> >>>   3.1.1W Windows Installation - section only required for Windows >>> Software >>>     (see http://sac.sfbay/WSARC/2002/494 for details) >>>     Does this project install software into a >>>     :\Program Files\Sun\ or >> drive>:\Sun\ >>>     directory? >>>     [ ] Yes >>>     [ ] No - ARC review required >>> >>>     Does the project use the Windows registry? >>>     [ ] Yes >>>     [ ] No - ARC review required >>> >>>     Does the project use >>>     HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ >>>     for the registry key? >>>     [ ] Yes >>>     [ ] No - ARC review required >>> >>>     Is the project's stored location >>>     HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\>> id>\Path? >>>     [ ] Yes >>>     [ ] No - ARC review required >>> >>>   3.1.2 Share and Sharable >>>     Does the module include any components that are used or shared by >>>     other projects? >>>     [*] Yes >>>     [ ] No >>> >>>     If yes are these components packaged to be shared with the other >>> FOSS? >>>     [*] Yes >>>     [ ] No - ARC review required >>>     [ ] N/A >>> >>>     Are these components already in the Solaris WOS? >>>     [ ] Yes >>>     [*] No - continue with next section (section 3.2) >>> >>>     If yes are these newer versions being delivered? >>>     [ ] Yes >>>     [ ] No - ARC review required >>> >>>     If yes are the newer versions replacing the existing versions? >>>     [ ] Yes >>>     [ ] No - ARC review required >>> >>>  3.2 Exported Libraries >>>     Are libraries being delivered by this project? >>>     [*] Yes >>>     [ ] No - continue with next section (section 3.3) >>> >>>     Are 64-bit versions of the libraries being delivered? >>>     [*] Yes >>>     [ ] No - ARC review required >>> >>>     Are static versions of the libraries being delivered? >>>     [ ] Yes - ARC review required >>>     [*] No >>> >>>  3.3 Services and the /etc Directory >>>     (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >>>     Does the project integrate anything into /etc/init.d or /etc/rc?.d? >>>     [ ] Yes - ARC review required >>>     [*] No >>> >>>     Does the project integrate any new entries into /etc/inittab or >>>     /etc/inetd.conf? >>>     [ ] Yes - ARC review required >>>     [*] No >>> >>>     Does the project integrate any private non-public files into >>> /etc/default >>>     or /etc/ configuration files? >>>     [ ] Yes - ARC review required >>>     [*] No >>> >>>     Does the service manifests method context grant rights above that >>>     of the noaccess user and basic privilege set? >>>     [ ] Yes - ARC review required >>>     [*] No >>> >>>  3.4 Security >>>   3.4.1 Secure By Default >>>     (see >>> http://opensolaris.org/os/community/arc/policies/secure-by-default/ for >>> details) >>>     (see >>> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for >>> details) >>>     (see parts of >>> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >>>      addtional details) >>>     Are there any network services provided by this project? >>>     [ ] Yes >>>     [*] No - continue with the next section (section 3.4.2) >>> >>>     Are network services enabled by default? >>>     [ ] Yes - ARC review required >>>     [ ] No >>>     [ ] N/A >>> >>>     Are network services automatically enabled by the project during >>> installation? >>>     [ ] Yes - ARC review required >>>     [ ] No >>>     [ ] N/A >>> >>>     Are inbound network communications denied by default? >>>     [ ] Yes >>>     [ ] No - ARC review required >>>     [ ] N/A >>> >>>     Is inbound data checked to prevent content-based attacks? >>>     [ ] Yes >>>     [ ] No - ARC review required >>>     [ ] N/A >>> >>>     Is the outbound receiver authenticated? >>>     [ ] Yes >>>     [ ] No - ARC review required >>>     [ ] N/A >>> >>>     Is the receiver authenticated prior to receiving any sensitive >>> outbound communication? >>>     [ ] Yes >>>     [ ] No - ARC review required >>>     [ ] N/A >>> >>>   3.4.2 Authorization >>>     (see >>> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >>> >>>  http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and >>> >>>  http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>>          for details) >>>     Are there any setuid/setgid privileged binaries in the project? >>>     [ ] Yes - ARC review required >>>     [*] No - continue with next section (section 3.4.3) >>> >>>     If yes then are the setuid/setgid privileges handled by the use of >>> roles? >>>     [ ] Yes >>>     [ ] No - ARC review required >>> >>>   3.4.3 Auditing >>>     (see >>> http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) >>>     (see http://opensolaris.org/os/community/arc/caselog/2003/397 for >>> details) >>>     Does this component contain administrative or security enforcing >>> software? >>>     [ ] Yes - ARC review required >>>     [*] No - continue to next section (section 3.4.4) >>> >>>     (see http://opensolaris.org/os/community/arc/caselog/2003/397 for >>> details) >>>     Do the components create audit logs detailing what took place >>> including what event >>>     took place, who was involved, when the event took place? >>>     [ ] Yes - ARC contract and Audit project team review required >>>     [ ] No - ARC review required >>> >>> >>>   3.4.4 Authentication >>>     (see http://opensolaris.org/os/community/arc/policies/PAM/) >>>     Do the components contain any authentication code? >>>     [ ] Yes >>>     [*] No - continue to next section (section 3.4.5) >>> >>>     If yes do the components use PAM (plugable authentication modules) >>> for authentication? >>>     [ ] Yes >>>     [ ] No - ARC review required >>> >>>     If yes is a single PAM session maintained during authentication? >>>     [ ] Yes >>>     [ ] No - ARC review required >>> >>>     If yes are the components sufficiently privileged to allow the >>> requested >>>     operations (authentication, password change, process credential >>> manipulation, >>>     audit state initialization)? >>>     [ ] Yes - briefly describe below >>>     [ ] No - ARC review required >>> >>>   3.4.5 Passwords >>>     (see >>> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >>> >>>  http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for >>> details) >>>     Do any of the components for the project deal with passwords? >>>     [ ] Yes >>>     [*] No - continue to next section (section 3.4.6) >>> >>>     If yes are these passwords entered via the CLI or environment? >>>     [ ] Yes - ARC review required >>>     [ ] No >>> >>>     Are passwords stored within the file system for the component? >>>     [ ] Yes >>>     [ ] No - continue to next section (section 3.4.6) >>> >>>     If yes are the permissions on the file such to protect exposing the >>> password(s)? >>>     [ ] Yes >>>     [ ] No - ARC review required >>> >>>   3.4.6 General Security Questions >>>     (see >>> http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for >>> details) >>>     Are there any network protocols used by this project? >>>     [*] Yes >>>     [ ] No - continue with the next section (section 3.5) >>> >>>     Do the components use standard network protocols? >>>     [*] Yes >>>     [ ] No - ARC review required >>> >>>     Do network services for the project make decisions based upon user, >>> host or >>>     service identities? >>>     [ ] Yes - explain below >>>     [*] No >>>     [ ] N/A >>> >>>     Do the components make use of secret information during >>> authentication and/or >>>     authorization? >>>     [ ] Yes - explain below >>>     [*] No >>>     [ ] N/A >>> >>>  3.5 Networking >>>     Do the components access the network? >>>     [*] Yes >>>     [ ] No - continue with the next section (section 3.6) >>> >>>     If yes do the components support IPv6? >>>     [*] Yes >>>     [ ] No - ARC review required >>> >>>  3.6 Core Solaris Components >>>     Do the components of this project compete with or duplicate core >>>     Solaris components? >>>     [ ] Yes - ARC review required >>>     [*] No >>> >>>     Examples of Core Solaris Components include but are not limited to: >>> >>>       Secure By Default >>>       Authorizations >>>       PAM -- Plugable Authentication Module >>>       Privilege >>>       PRM -- Process Rights Management -- Privilege >>>       Audit >>>       xVm -- Virtualization >>>       zones / Solaris Containers >>>       PRM -- Process Rights Management >>>       RBAC -- Role Based Access Control >>>       TX / Trusted Extensions >>>       ZFS >>>       SMF -- Service Management Facility >>>       FMA -- Fault Management Architecture >>>       SCF -- Smart Card Facility >>>       IPsec >>> >>> 4.0 Interfaces >>>  4.1 Exported Interfaces >>> >>>   Interface Name               Classification Comments >>>   ---------------------------  -------------- ------------------- >>>   SUNWrtorrent                 Uncommitted    Package >>>   /usr/bin/rtorrent            Uncommitted    rtorrent command >>>   SUNWlibtorrent               Uncommitted    Package >>>   /usr/include/torrent/        Uncommitted    Header file directory >>>   /usr/lib/libtorrent.so       Uncommitted    libtorrent Library >>>   /usr/lib/libtorrent.so.9     Uncommitted    libtorrent Library >>>   /usr/lib/libtorrent.so.9.2.0 Uncommitted    libtorrent Library >>>   /usr/lib/64/libtorrent*      Uncommitted    64-bit Library and links >>>   /usr/lib/pkgconfig/libtorrent.pc >>>                                Uncommitted    pkgconfig script >>> >>>   * /64 equals sparcv9 and amd64 >>> >>>  4.2 Imported Interfaces >>> >>>   Interface Name       Classification Comments >>>   -------------------- -------------- --------------- >>>   SUNWcurl             Uncommitted    C-URL Wrappers Library >>>   SUNWlibC             Uncommitted    Sun Workshop Compilers Bundled libC >>>   SUNWopensslr         Volatile       PSARC/2003/500 >>>   SUNWsigcpp           Uncommitted    typesafe callback system for C++ >>>   SUNWncurses          Uncommitted    A CRT screen handling package >>>   SUNWlibmsr           Committed      Math & Microtasking Libraries >>> (Root) >>> >>> Appendix A - References >>>  [1] http://libtorrent.rakshasa.no/ >>> >>>  OSR ID# 11082 11083 >>>  RFE ID# 6814041 6814042 >>> >>> 6. Resources and Schedule >>>   6.4. Steering Committee requested information >>>       6.4.1. Consolidation C-team Name: >>>               SFW >>>   6.5. ARC review type: FastTrack >>>   6.6. ARC Exposure: open >>> >>> _______________________________________________ >>> opensolaris-arc mailing list >>> opensolaris-arc@opensolaris.org >>> >> >> >> >> -- >> Andy >> http://blog.sartek.net > > -- Andy http://blog.sartek.net From Huawei.Zhang@Sun.COM Thu Jun 4 02:00:26 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5490P76025226 for ; Thu, 4 Jun 2009 02:00:26 -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.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5490OTO012657 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 4 Jun 2009 10:00:24 +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 <0KKP00I3PICOV500@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 04 Jun 2009 02:00:24 -0700 (PDT) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KKP00CHJICMID80@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 04 Jun 2009 02:00:23 -0700 (PDT) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5490Mho002295 for ; Thu, 04 Jun 2009 09:00:22 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KKP00H00I1BPV00@mail-apac.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 04 Jun 2009 17:00:22 +0800 (SGT) Received: from [129.158.144.119] ([unknown] [129.158.144.119]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KKP00BYKICK1740@mail-apac.sun.com>; Thu, 04 Jun 2009 17:00:22 +0800 (SGT) Date: Thu, 04 Jun 2009 17:00:19 +0800 From: alex zhang Subject: Re: rtorrent & libtorrent [PSARC/2009/336 FastTrack timeout 06/10/2009] In-reply-to: <56dc2e760906040051l4a05d9a2o34924b2e9fb0dab9@mail.gmail.com> Sender: Huawei.Zhang@Sun.COM To: Andras Barna Cc: James Walker , PSARC-ext@Sun.COM Message-id: <0639CAC0-8E97-4BFF-B925-80B089E20E29@Sun.COM> MIME-version: 1.0 X-Mailer: Apple Mail (2.935.3) Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> <56dc2e760906030325v1bac1da8ha099414c951a5ef3@mail.gmail.com> <381F38E0-FEC4-495D-B7B2-E54102F4682A@Sun.COM> <56dc2e760906040051l4a05d9a2o34924b2e9fb0dab9@mail.gmail.com> Status: RO Content-Length: 16648 There is still a question when I renaming "libtorrent.so", since other open source problem who using this library may not expect a different library name in their makefile. In debian, I saw the package libtorrent point to Rakshasa's libtorrent, while an other package libtorrent-rasterbar-dev point to the other one. see the link: http://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=names&keywords=libtorrent Thanks - Alex On Jun 4, 2009, at 3:51 PM, Andras Barna wrote: > i'd take 2. because no one know the future.. maybe it'll useful some > day. > (you are renaming libtorrent.so too, right?) > > thanks > > On Thu, Jun 4, 2009 at 5:41 AM, alex zhang > wrote: >> Hi, all >> >> Thanks for quick review. >> >> As far as my knowledge, now libTorrent (Rakshasa) don't have >> other client >> except rtorrent. >> >> For this problem, I have two solve suggestion: >> 1. only export SUNWrtorrent, don't export SUNWlibtorrent, compile >> it as a >> static library, which only used by rtorrent. >> 2. change SUNWlibtorrent to SUNWrlibtorrent. >> >> What is your advice? >> >> Thanks >> - Alex >> >> On Jun 3, 2009, at 6:25 PM, Andras Barna wrote: >> >>> i'm not sure if it's a good idea to package rakshasa's libtorrent as >>> SUNWlibtorrent because this may confuse people. see: >>> http://en.wikipedia.org/wiki/Libtorrent >>> >>> * libTorrent (Rakshasa) which powers rTorrent. >>> * Libtorrent (Rasterbar) which powers BTG, Deluge, Free Download >>> Manager, Halite, Linkage, Miro, qBittorrent, SharkTorrent, and many >>> more. >>> >>> + i'm dont know if something uses this libtorrent except rtorrent >>> >>> and would be nice too see SMF stuff for this. >>> >>> On Wed, Jun 3, 2009 at 1:13 PM, James Walker >> > >>> wrote: >>>> >>>> I'm sponsoring this familiarity case for Alex Zhang. The requested >>>> release binding is minor. The man pages have been posted in the >>>> materials directory. The OpenSSL contract link will be posted after >>>> it is approved. >>>> >>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>> This information is Copyright 2009 Sun Microsystems >>>> 1. Introduction >>>> 1.1. Project/Component Working Name: >>>> rtorrent & libtorent >>>> 1.2. Name of Document Author/Supplier: >>>> Author: Alex Zhang >>>> 1.3 Date of This Document: >>>> 03 June, 2009 >>>> 4. Technical Description >>>> libtorent & rtorrent Check List >>>> 1.0 Project Information >>>> 1.1 Name of project/component >>>> libtorrent & rtorrent >>>> >>>> 1.2 Author of document >>>> Huawei.Zhang@Sun.COM >>>> >>>> 2.0 Project Summary >>>> 2.1 Project Description >>>> libtorrent is a BitTorrent library written in C++ for *nix, >>>> with a >>>> focus on high performance and good code. >>>> >>>> rtorrent is a BitTorrent client for ncurses, using the libtorrent >>>> library. >>>> >>>> 2.2 Release binding >>>> What is is the release binding? >>>> (see >>>> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >>>> [ ] Major >>>> [*] Minor >>>> [ ] Patch or Micro >>>> [ ] Unknown -- ARC review required >>>> >>>> 2.3 Type of project >>>> Is this case a Linux Familiarity project? >>>> [*] Yes >>>> [ ] No >>>> >>>> 2.4 Originating Community >>>> 2.4.1 Community Name >>>> libtorrent - Jari Sundell [1] >>>> rtorrent - Jari Sundell [1] >>>> >>>> 2.4.2 Community Involvement >>>> Indicate Sun's involvement in the community >>>> [ ] Maintainer >>>> [ ] Contributor >>>> [*] Monitoring >>>> >>>> Will the project team work with the upstream community to >>>> resolve >>>> architectural issues of interest to Sun? >>>> [*] Yes >>>> [ ] No - briefly explain >>>> >>>> Will we or are we forking from the community? >>>> [ ] Yes - ARC review required prior to forking >>>> [*] No >>>> >>>> 3.0 Technical Description >>>> 3.1 Installation & Sharable >>>> 3.1.1S Solaris Installation - section only required for Solaris >>>> Software >>>> (see >>>> http://opensolaris.org/os/community/arc/policies/install- >>>> locations/ for >>>> details) >>>> Does this project follow the Install Locations best practice? >>>> [*] Yes >>>> [ ] No - ARC review required >>>> >>>> Does this project install into /usr under >>>> [sbin|bin|lib|include|man|share]? >>>> [*] Yes >>>> [ ] No or N/A >>>> >>>> Does this project install into /opt? >>>> [ ] Yes - explain below >>>> [*] No or N/A >>>> >>>> Does this project install into a different directory structure? >>>> [ ] Yes - ARC review required >>>> [*] No or N/A >>>> >>>> Do any of the components of this project conflict with >>>> anything under >>>> /usr? >>>> (see http://opensolaris.org/os/community/arc/caselog/ >>>> 2007/047/ for >>>> details) >>>> [ ] Yes - explain below >>>> [*] No >>>> >>>> If conflicts exist then will this project install under /usr/ >>>> gnu? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [*] N/A >>>> >>>> Is this project installing into /usr/sfw? >>>> [ ] Yes - ARC review required >>>> [*] No >>>> >>>> 3.1.1W Windows Installation - section only required for Windows >>>> Software >>>> (see http://sac.sfbay/WSARC/2002/494 for details) >>>> Does this project install software into a >>>> :\Program Files\Sun\ or >>> drive>:\Sun\ >>>> directory? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> Does the project use the Windows registry? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> Does the project use >>>> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\ >>>> \ >>>> for the registry key? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> Is the project's stored location >>>> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\ >>>> \>>> id>\Path? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> 3.1.2 Share and Sharable >>>> Does the module include any components that are used or >>>> shared by >>>> other projects? >>>> [*] Yes >>>> [ ] No >>>> >>>> If yes are these components packaged to be shared with the >>>> other >>>> FOSS? >>>> [*] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> >>>> Are these components already in the Solaris WOS? >>>> [ ] Yes >>>> [*] No - continue with next section (section 3.2) >>>> >>>> If yes are these newer versions being delivered? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> If yes are the newer versions replacing the existing versions? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> 3.2 Exported Libraries >>>> Are libraries being delivered by this project? >>>> [*] Yes >>>> [ ] No - continue with next section (section 3.3) >>>> >>>> Are 64-bit versions of the libraries being delivered? >>>> [*] Yes >>>> [ ] No - ARC review required >>>> >>>> Are static versions of the libraries being delivered? >>>> [ ] Yes - ARC review required >>>> [*] No >>>> >>>> 3.3 Services and the /etc Directory >>>> (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >>>> Does the project integrate anything into /etc/init.d or /etc/ >>>> rc?.d? >>>> [ ] Yes - ARC review required >>>> [*] No >>>> >>>> Does the project integrate any new entries into /etc/inittab or >>>> /etc/inetd.conf? >>>> [ ] Yes - ARC review required >>>> [*] No >>>> >>>> Does the project integrate any private non-public files into >>>> /etc/default >>>> or /etc/ configuration files? >>>> [ ] Yes - ARC review required >>>> [*] No >>>> >>>> Does the service manifests method context grant rights above >>>> that >>>> of the noaccess user and basic privilege set? >>>> [ ] Yes - ARC review required >>>> [*] No >>>> >>>> 3.4 Security >>>> 3.4.1 Secure By Default >>>> (see >>>> http://opensolaris.org/os/community/arc/policies/secure-by- >>>> default/ for >>>> details) >>>> (see >>>> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ >>>> for >>>> details) >>>> (see parts of >>>> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >>>> addtional details) >>>> Are there any network services provided by this project? >>>> [ ] Yes >>>> [*] No - continue with the next section (section 3.4.2) >>>> >>>> Are network services enabled by default? >>>> [ ] Yes - ARC review required >>>> [ ] No >>>> [ ] N/A >>>> >>>> Are network services automatically enabled by the project >>>> during >>>> installation? >>>> [ ] Yes - ARC review required >>>> [ ] No >>>> [ ] N/A >>>> >>>> Are inbound network communications denied by default? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> >>>> Is inbound data checked to prevent content-based attacks? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> >>>> Is the outbound receiver authenticated? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> >>>> Is the receiver authenticated prior to receiving any sensitive >>>> outbound communication? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> [ ] N/A >>>> >>>> 3.4.2 Authorization >>>> (see >>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ >>>> and >>>> >>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>>> and >>>> >>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>>> for details) >>>> Are there any setuid/setgid privileged binaries in the project? >>>> [ ] Yes - ARC review required >>>> [*] No - continue with next section (section 3.4.3) >>>> >>>> If yes then are the setuid/setgid privileges handled by the >>>> use of >>>> roles? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> 3.4.3 Auditing >>>> (see >>>> http://opensolaris.org/os/community/arc/policies/audit-policy/ >>>> for details) >>>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>>> for >>>> details) >>>> Does this component contain administrative or security >>>> enforcing >>>> software? >>>> [ ] Yes - ARC review required >>>> [*] No - continue to next section (section 3.4.4) >>>> >>>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>>> for >>>> details) >>>> Do the components create audit logs detailing what took place >>>> including what event >>>> took place, who was involved, when the event took place? >>>> [ ] Yes - ARC contract and Audit project team review required >>>> [ ] No - ARC review required >>>> >>>> >>>> 3.4.4 Authentication >>>> (see http://opensolaris.org/os/community/arc/policies/PAM/) >>>> Do the components contain any authentication code? >>>> [ ] Yes >>>> [*] No - continue to next section (section 3.4.5) >>>> >>>> If yes do the components use PAM (plugable authentication >>>> modules) >>>> for authentication? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> If yes is a single PAM session maintained during >>>> authentication? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> If yes are the components sufficiently privileged to allow the >>>> requested >>>> operations (authentication, password change, process credential >>>> manipulation, >>>> audit state initialization)? >>>> [ ] Yes - briefly describe below >>>> [ ] No - ARC review required >>>> >>>> 3.4.5 Passwords >>>> (see >>>> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ >>>> and >>>> >>>> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ >>>> for >>>> details) >>>> Do any of the components for the project deal with passwords? >>>> [ ] Yes >>>> [*] No - continue to next section (section 3.4.6) >>>> >>>> If yes are these passwords entered via the CLI or environment? >>>> [ ] Yes - ARC review required >>>> [ ] No >>>> >>>> Are passwords stored within the file system for the component? >>>> [ ] Yes >>>> [ ] No - continue to next section (section 3.4.6) >>>> >>>> If yes are the permissions on the file such to protect >>>> exposing the >>>> password(s)? >>>> [ ] Yes >>>> [ ] No - ARC review required >>>> >>>> 3.4.6 General Security Questions >>>> (see >>>> http://opensolaris.org/os/community/arc/bestpractices/security-questions/ >>>> for >>>> details) >>>> Are there any network protocols used by this project? >>>> [*] Yes >>>> [ ] No - continue with the next section (section 3.5) >>>> >>>> Do the components use standard network protocols? >>>> [*] Yes >>>> [ ] No - ARC review required >>>> >>>> Do network services for the project make decisions based upon >>>> user, >>>> host or >>>> service identities? >>>> [ ] Yes - explain below >>>> [*] No >>>> [ ] N/A >>>> >>>> Do the components make use of secret information during >>>> authentication and/or >>>> authorization? >>>> [ ] Yes - explain below >>>> [*] No >>>> [ ] N/A >>>> >>>> 3.5 Networking >>>> Do the components access the network? >>>> [*] Yes >>>> [ ] No - continue with the next section (section 3.6) >>>> >>>> If yes do the components support IPv6? >>>> [*] Yes >>>> [ ] No - ARC review required >>>> >>>> 3.6 Core Solaris Components >>>> Do the components of this project compete with or duplicate >>>> core >>>> Solaris components? >>>> [ ] Yes - ARC review required >>>> [*] No >>>> >>>> Examples of Core Solaris Components include but are not >>>> limited to: >>>> >>>> Secure By Default >>>> Authorizations >>>> PAM -- Plugable Authentication Module >>>> Privilege >>>> PRM -- Process Rights Management -- Privilege >>>> Audit >>>> xVm -- Virtualization >>>> zones / Solaris Containers >>>> PRM -- Process Rights Management >>>> RBAC -- Role Based Access Control >>>> TX / Trusted Extensions >>>> ZFS >>>> SMF -- Service Management Facility >>>> FMA -- Fault Management Architecture >>>> SCF -- Smart Card Facility >>>> IPsec >>>> >>>> 4.0 Interfaces >>>> 4.1 Exported Interfaces >>>> >>>> Interface Name Classification Comments >>>> --------------------------- -------------- ------------------- >>>> SUNWrtorrent Uncommitted Package >>>> /usr/bin/rtorrent Uncommitted rtorrent command >>>> SUNWlibtorrent Uncommitted Package >>>> /usr/include/torrent/ Uncommitted Header file directory >>>> /usr/lib/libtorrent.so Uncommitted libtorrent Library >>>> /usr/lib/libtorrent.so.9 Uncommitted libtorrent Library >>>> /usr/lib/libtorrent.so.9.2.0 Uncommitted libtorrent Library >>>> /usr/lib/64/libtorrent* Uncommitted 64-bit Library and >>>> links >>>> /usr/lib/pkgconfig/libtorrent.pc >>>> Uncommitted pkgconfig script >>>> >>>> * /64 equals sparcv9 and amd64 >>>> >>>> 4.2 Imported Interfaces >>>> >>>> Interface Name Classification Comments >>>> -------------------- -------------- --------------- >>>> SUNWcurl Uncommitted C-URL Wrappers Library >>>> SUNWlibC Uncommitted Sun Workshop Compilers >>>> Bundled libC >>>> SUNWopensslr Volatile PSARC/2003/500 >>>> SUNWsigcpp Uncommitted typesafe callback system >>>> for C++ >>>> SUNWncurses Uncommitted A CRT screen handling package >>>> SUNWlibmsr Committed Math & Microtasking Libraries >>>> (Root) >>>> >>>> Appendix A - References >>>> [1] http://libtorrent.rakshasa.no/ >>>> >>>> OSR ID# 11082 11083 >>>> RFE ID# 6814041 6814042 >>>> >>>> 6. Resources and Schedule >>>> 6.4. Steering Committee requested information >>>> 6.4.1. Consolidation C-team Name: >>>> SFW >>>> 6.5. ARC review type: FastTrack >>>> 6.6. ARC Exposure: open >>>> >>>> _______________________________________________ >>>> opensolaris-arc mailing list >>>> opensolaris-arc@opensolaris.org >>>> >>> >>> >>> >>> -- >>> Andy >>> http://blog.sartek.net >> >> > > > > -- > Andy > http://blog.sartek.net From andras.barna@gmail.com Thu Jun 4 02:46:12 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n549kC7W025699 for ; Thu, 4 Jun 2009 02:46:12 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n549k1wm020326; Thu, 4 Jun 2009 02:46:10 -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 <0KKP0001HKGXT200@brm-avmta-1.central.sun.com>; Thu, 04 Jun 2009 03:46:09 -0600 (MDT) Received: from sca-ea-mail-3.sun.com ([192.18.43.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KKP00DAEKGXLD70@brm-avmta-1.central.sun.com>; Thu, 04 Jun 2009 03:46:09 -0600 (MDT) Received: from relay13i.sun.com (ip123.net129179-4.block1.us.syntegra.com [129.179.4.123]) by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n549bVTt006715; Thu, 04 Jun 2009 09:46:08 +0000 (GMT) Received: from mmp12es.mmp.us.syntegra.com ([160.41.208.12] [160.41.208.12]) by relay13i.sun.com with ESMTP id BT-MMP-1566075; Thu, 04 Jun 2009 09:46:08 +0000 (Z) Received: from relay13i.sun.com (relay13i.sun.com [129.179.4.123]) by mmp12es.mmp.us.syntegra.com with ESMTP id BT-MMP-122065158; Thu, 04 Jun 2009 09:46:05 +0000 (Z) Received: from mail-ew0-f205.google.com ([209.85.219.205] [209.85.219.205]) by relay1i.sun.com with ESMTP id BT-MMP-3539555; Thu, 04 Jun 2009 09:46:05 +0000 (Z) Received: by ewy1 with SMTP id 1so986566ewy.8 for ; Thu, 04 Jun 2009 02:45:14 -0700 (PDT) Received: by 10.216.45.73 with SMTP id o51mr679562web.10.1244108714380; Thu, 04 Jun 2009 02:45:14 -0700 (PDT) Date: Thu, 04 Jun 2009 12:45:14 +0300 From: Andras Barna Subject: Re: rtorrent & libtorrent [PSARC/2009/336 FastTrack timeout 06/10/2009] In-reply-to: <0639CAC0-8E97-4BFF-B925-80B089E20E29@Sun.COM> To: alex zhang Cc: James Walker , PSARC-ext@sun.com Message-id: <56dc2e760906040245r8d33301o9b98b894362b62f4@mail.gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=9aK9RnnYnJTNvFhWP63K+ucQSFsEOGU/0LBkJW+5Hm8=; b=wlzBnvPx60y6kNq7lvMTOUXicQtb4bVF58B/Xyl+GY7R4i3BrWaEl1yIEj6YgMvU6Z 46Bs7O75ZaxLv+SZ9ZAz7EkHNcfp1o3+BcgECZUmifCptvhSHfk4hRlC3hHmHmElpZ4U jgFE+LWzwa+8Curi6tLGYMKNr3CXvniNu7jRA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mb2/tpjZwANldyLf4QGds7Q4zFZwsCFb5u1UeH8uKqDgLJXzQr6SBEaGbAtINN9YU4 oclg+0eg5b7Q3UiSAHdNhkJgrsE2F5bjR6uk0QcfBUknXV3bQOTeGB1xDlAoh2skFTMa RgbZw/8qezvE5ZD9BycvprX1oIbab0BtZiZhk= X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Antispam: No, score=-2.6/5.0, scanned in 2.114sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> <56dc2e760906030325v1bac1da8ha099414c951a5ef3@mail.gmail.com> <381F38E0-FEC4-495D-B7B2-E54102F4682A@Sun.COM> <56dc2e760906040051l4a05d9a2o34924b2e9fb0dab9@mail.gmail.com> <0639CAC0-8E97-4BFF-B925-80B089E20E29@Sun.COM> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by sac.sfbay.sun.com id n549kC7W025699 Status: RO Content-Length: 17624 yeap they have libtorrent-rasterbar.so for libtorrent-rastebar and for rakshasa's simply libtorrent. so we can go this way too (if noone has other idea(s)) thanks On Thu, Jun 4, 2009 at 12:00 PM, alex zhang wrote: > There is still a question when I renaming "libtorrent.so", > since other open source problem who using this library may not expect a > different library name in their makefile. > > In debian, I saw the package libtorrent point to Rakshasa's libtorrent, > while an other package libtorrent-rasterbar-dev point to the other one. > see the link: > http://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=names&keywords=libtorrent > > Thanks > - Alex > On Jun 4, 2009, at 3:51 PM, Andras Barna wrote: > >> i'd take 2. because no one know the future.. maybe it'll useful some day. >> (you are renaming libtorrent.so too, right?) >> >> thanks >> >> On Thu, Jun 4, 2009 at 5:41 AM, alex zhang wrote: >>> >>> Hi, all >>> >>>  Thanks for quick review. >>> >>>  As far as my knowledge, now libTorrent (Rakshasa) don't have other >>> client >>> except rtorrent. >>> >>>  For this problem, I have two solve suggestion: >>> 1. only export SUNWrtorrent, don't export SUNWlibtorrent, compile it as a >>> static library, which only used by rtorrent. >>> 2. change SUNWlibtorrent to SUNWrlibtorrent. >>> >>>  What is your advice? >>> >>> Thanks >>> - Alex >>> >>> On Jun 3, 2009, at 6:25 PM, Andras Barna wrote: >>> >>>> i'm not sure if it's a good idea to package rakshasa's libtorrent as >>>> SUNWlibtorrent because this may confuse people. see: >>>> http://en.wikipedia.org/wiki/Libtorrent >>>> >>>>  * libTorrent (Rakshasa) which powers rTorrent. >>>>  * Libtorrent (Rasterbar) which powers BTG, Deluge, Free Download >>>> Manager, Halite, Linkage, Miro, qBittorrent, SharkTorrent, and many >>>> more. >>>> >>>> + i'm dont know if something uses this libtorrent except rtorrent >>>> >>>> and would be nice too see SMF stuff for this. >>>> >>>> On Wed, Jun 3, 2009 at 1:13 PM, James Walker >>>> >>>> wrote: >>>>> >>>>> I'm sponsoring this familiarity case for Alex Zhang. The requested >>>>> release binding is minor. The man pages have been posted in the >>>>> materials directory. The OpenSSL contract link will be posted after >>>>> it is approved. >>>>> >>>>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >>>>> This information is Copyright 2009 Sun Microsystems >>>>> 1. Introduction >>>>>  1.1. Project/Component Working Name: >>>>>       rtorrent & libtorent >>>>>  1.2. Name of Document Author/Supplier: >>>>>       Author:  Alex Zhang >>>>>  1.3  Date of This Document: >>>>>      03 June, 2009 >>>>> 4. Technical Description >>>>> libtorent & rtorrent Check List >>>>> 1.0 Project Information >>>>> 1.1 Name of project/component >>>>>  libtorrent & rtorrent >>>>> >>>>> 1.2 Author of document >>>>>  Huawei.Zhang@Sun.COM >>>>> >>>>> 2.0 Project Summary >>>>>  2.1 Project Description >>>>>  libtorrent is a BitTorrent library written in C++ for *nix, with a >>>>> focus on high performance and good code. >>>>> >>>>>  rtorrent is a BitTorrent client for ncurses, using the libtorrent >>>>> library. >>>>> >>>>>  2.2 Release binding >>>>>    What is is the release binding? >>>>>    (see >>>>> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >>>>>    [ ] Major >>>>>    [*] Minor >>>>>    [ ] Patch or Micro >>>>>    [ ] Unknown -- ARC review required >>>>> >>>>>  2.3 Type of project >>>>>    Is this case a Linux Familiarity project? >>>>>    [*] Yes >>>>>    [ ] No >>>>> >>>>>  2.4 Originating Community >>>>>  2.4.1 Community Name >>>>>    libtorrent - Jari Sundell [1] >>>>>    rtorrent - Jari Sundell [1] >>>>> >>>>>  2.4.2 Community Involvement >>>>>    Indicate Sun's involvement in the community >>>>>    [ ] Maintainer >>>>>    [ ] Contributor >>>>>    [*] Monitoring >>>>> >>>>>    Will the project team work with the upstream community to resolve >>>>>    architectural issues of interest to Sun? >>>>>    [*] Yes >>>>>    [ ] No - briefly explain >>>>> >>>>>    Will we or are we forking from the community? >>>>>    [ ] Yes - ARC review required prior to forking >>>>>    [*] No >>>>> >>>>> 3.0 Technical Description >>>>>  3.1 Installation & Sharable >>>>>  3.1.1S Solaris Installation - section only required for Solaris >>>>> Software >>>>>    (see >>>>> http://opensolaris.org/os/community/arc/policies/install-locations/ for >>>>> details) >>>>>    Does this project follow the Install Locations best practice? >>>>>    [*] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>    Does this project install into /usr under >>>>> [sbin|bin|lib|include|man|share]? >>>>>    [*] Yes >>>>>    [ ] No or N/A >>>>> >>>>>    Does this project install into /opt? >>>>>    [ ] Yes - explain below >>>>>    [*] No or N/A >>>>> >>>>>    Does this project install into a different directory structure? >>>>>    [ ] Yes - ARC review required >>>>>    [*] No or N/A >>>>> >>>>>    Do any of the components of this project conflict with anything >>>>> under >>>>> /usr? >>>>>    (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for >>>>> details) >>>>>    [ ] Yes - explain below >>>>>    [*] No >>>>> >>>>>    If conflicts exist then will this project install under /usr/gnu? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>>    [*] N/A >>>>> >>>>>    Is this project installing into /usr/sfw? >>>>>    [ ] Yes - ARC review required >>>>>    [*] No >>>>> >>>>>  3.1.1W Windows Installation - section only required for Windows >>>>> Software >>>>>    (see http://sac.sfbay/WSARC/2002/494 for details) >>>>>    Does this project install software into a >>>>>    :\Program Files\Sun\ or >>>> drive>:\Sun\ >>>>>    directory? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>    Does the project use the Windows registry? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>    Does the project use >>>>>    HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ >>>>>    for the registry key? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>    Is the project's stored location >>>>>    HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\>>>> id>\Path? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>  3.1.2 Share and Sharable >>>>>    Does the module include any components that are used or shared by >>>>>    other projects? >>>>>    [*] Yes >>>>>    [ ] No >>>>> >>>>>    If yes are these components packaged to be shared with the other >>>>> FOSS? >>>>>    [*] Yes >>>>>    [ ] No - ARC review required >>>>>    [ ] N/A >>>>> >>>>>    Are these components already in the Solaris WOS? >>>>>    [ ] Yes >>>>>    [*] No - continue with next section (section 3.2) >>>>> >>>>>    If yes are these newer versions being delivered? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>    If yes are the newer versions replacing the existing versions? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>  3.2 Exported Libraries >>>>>    Are libraries being delivered by this project? >>>>>    [*] Yes >>>>>    [ ] No - continue with next section (section 3.3) >>>>> >>>>>    Are 64-bit versions of the libraries being delivered? >>>>>    [*] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>    Are static versions of the libraries being delivered? >>>>>    [ ] Yes - ARC review required >>>>>    [*] No >>>>> >>>>>  3.3 Services and the /etc Directory >>>>>    (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >>>>>    Does the project integrate anything into /etc/init.d or /etc/rc?.d? >>>>>    [ ] Yes - ARC review required >>>>>    [*] No >>>>> >>>>>    Does the project integrate any new entries into /etc/inittab or >>>>>    /etc/inetd.conf? >>>>>    [ ] Yes - ARC review required >>>>>    [*] No >>>>> >>>>>    Does the project integrate any private non-public files into >>>>> /etc/default >>>>>    or /etc/ configuration files? >>>>>    [ ] Yes - ARC review required >>>>>    [*] No >>>>> >>>>>    Does the service manifests method context grant rights above that >>>>>    of the noaccess user and basic privilege set? >>>>>    [ ] Yes - ARC review required >>>>>    [*] No >>>>> >>>>>  3.4 Security >>>>>  3.4.1 Secure By Default >>>>>    (see >>>>> http://opensolaris.org/os/community/arc/policies/secure-by-default/ for >>>>> details) >>>>>    (see >>>>> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for >>>>> details) >>>>>    (see parts of >>>>> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >>>>>     addtional details) >>>>>    Are there any network services provided by this project? >>>>>    [ ] Yes >>>>>    [*] No - continue with the next section (section 3.4.2) >>>>> >>>>>    Are network services enabled by default? >>>>>    [ ] Yes - ARC review required >>>>>    [ ] No >>>>>    [ ] N/A >>>>> >>>>>    Are network services automatically enabled by the project during >>>>> installation? >>>>>    [ ] Yes - ARC review required >>>>>    [ ] No >>>>>    [ ] N/A >>>>> >>>>>    Are inbound network communications denied by default? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>>    [ ] N/A >>>>> >>>>>    Is inbound data checked to prevent content-based attacks? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>>    [ ] N/A >>>>> >>>>>    Is the outbound receiver authenticated? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>>    [ ] N/A >>>>> >>>>>    Is the receiver authenticated prior to receiving any sensitive >>>>> outbound communication? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>>    [ ] N/A >>>>> >>>>>  3.4.2 Authorization >>>>>    (see >>>>> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >>>>> >>>>> >>>>>  http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and >>>>> >>>>>  http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>>>>         for details) >>>>>    Are there any setuid/setgid privileged binaries in the project? >>>>>    [ ] Yes - ARC review required >>>>>    [*] No - continue with next section (section 3.4.3) >>>>> >>>>>    If yes then are the setuid/setgid privileges handled by the use of >>>>> roles? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>  3.4.3 Auditing >>>>>    (see >>>>> http://opensolaris.org/os/community/arc/policies/audit-policy/ for >>>>> details) >>>>>    (see http://opensolaris.org/os/community/arc/caselog/2003/397 for >>>>> details) >>>>>    Does this component contain administrative or security enforcing >>>>> software? >>>>>    [ ] Yes - ARC review required >>>>>    [*] No - continue to next section (section 3.4.4) >>>>> >>>>>    (see http://opensolaris.org/os/community/arc/caselog/2003/397 for >>>>> details) >>>>>    Do the components create audit logs detailing what took place >>>>> including what event >>>>>    took place, who was involved, when the event took place? >>>>>    [ ] Yes - ARC contract and Audit project team review required >>>>>    [ ] No - ARC review required >>>>> >>>>> >>>>>  3.4.4 Authentication >>>>>    (see http://opensolaris.org/os/community/arc/policies/PAM/) >>>>>    Do the components contain any authentication code? >>>>>    [ ] Yes >>>>>    [*] No - continue to next section (section 3.4.5) >>>>> >>>>>    If yes do the components use PAM (plugable authentication modules) >>>>> for authentication? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>    If yes is a single PAM session maintained during authentication? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>    If yes are the components sufficiently privileged to allow the >>>>> requested >>>>>    operations (authentication, password change, process credential >>>>> manipulation, >>>>>    audit state initialization)? >>>>>    [ ] Yes - briefly describe below >>>>>    [ ] No - ARC review required >>>>> >>>>>  3.4.5 Passwords >>>>>    (see >>>>> >>>>> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >>>>> >>>>> >>>>>  http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for >>>>> details) >>>>>    Do any of the components for the project deal with passwords? >>>>>    [ ] Yes >>>>>    [*] No - continue to next section (section 3.4.6) >>>>> >>>>>    If yes are these passwords entered via the CLI or environment? >>>>>    [ ] Yes - ARC review required >>>>>    [ ] No >>>>> >>>>>    Are passwords stored within the file system for the component? >>>>>    [ ] Yes >>>>>    [ ] No - continue to next section (section 3.4.6) >>>>> >>>>>    If yes are the permissions on the file such to protect exposing the >>>>> password(s)? >>>>>    [ ] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>  3.4.6 General Security Questions >>>>>    (see >>>>> >>>>> http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for >>>>> details) >>>>>    Are there any network protocols used by this project? >>>>>    [*] Yes >>>>>    [ ] No - continue with the next section (section 3.5) >>>>> >>>>>    Do the components use standard network protocols? >>>>>    [*] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>    Do network services for the project make decisions based upon user, >>>>> host or >>>>>    service identities? >>>>>    [ ] Yes - explain below >>>>>    [*] No >>>>>    [ ] N/A >>>>> >>>>>    Do the components make use of secret information during >>>>> authentication and/or >>>>>    authorization? >>>>>    [ ] Yes - explain below >>>>>    [*] No >>>>>    [ ] N/A >>>>> >>>>>  3.5 Networking >>>>>    Do the components access the network? >>>>>    [*] Yes >>>>>    [ ] No - continue with the next section (section 3.6) >>>>> >>>>>    If yes do the components support IPv6? >>>>>    [*] Yes >>>>>    [ ] No - ARC review required >>>>> >>>>>  3.6 Core Solaris Components >>>>>    Do the components of this project compete with or duplicate core >>>>>    Solaris components? >>>>>    [ ] Yes - ARC review required >>>>>    [*] No >>>>> >>>>>    Examples of Core Solaris Components include but are not limited to: >>>>> >>>>>      Secure By Default >>>>>      Authorizations >>>>>      PAM -- Plugable Authentication Module >>>>>      Privilege >>>>>      PRM -- Process Rights Management -- Privilege >>>>>      Audit >>>>>      xVm -- Virtualization >>>>>      zones / Solaris Containers >>>>>      PRM -- Process Rights Management >>>>>      RBAC -- Role Based Access Control >>>>>      TX / Trusted Extensions >>>>>      ZFS >>>>>      SMF -- Service Management Facility >>>>>      FMA -- Fault Management Architecture >>>>>      SCF -- Smart Card Facility >>>>>      IPsec >>>>> >>>>> 4.0 Interfaces >>>>>  4.1 Exported Interfaces >>>>> >>>>>  Interface Name               Classification Comments >>>>>  ---------------------------  -------------- ------------------- >>>>>  SUNWrtorrent                 Uncommitted    Package >>>>>  /usr/bin/rtorrent            Uncommitted    rtorrent command >>>>>  SUNWlibtorrent               Uncommitted    Package >>>>>  /usr/include/torrent/        Uncommitted    Header file directory >>>>>  /usr/lib/libtorrent.so       Uncommitted    libtorrent Library >>>>>  /usr/lib/libtorrent.so.9     Uncommitted    libtorrent Library >>>>>  /usr/lib/libtorrent.so.9.2.0 Uncommitted    libtorrent Library >>>>>  /usr/lib/64/libtorrent*      Uncommitted    64-bit Library and links >>>>>  /usr/lib/pkgconfig/libtorrent.pc >>>>>                               Uncommitted    pkgconfig script >>>>> >>>>>  * /64 equals sparcv9 and amd64 >>>>> >>>>>  4.2 Imported Interfaces >>>>> >>>>>  Interface Name       Classification Comments >>>>>  -------------------- -------------- --------------- >>>>>  SUNWcurl             Uncommitted    C-URL Wrappers Library >>>>>  SUNWlibC             Uncommitted    Sun Workshop Compilers Bundled >>>>> libC >>>>>  SUNWopensslr         Volatile       PSARC/2003/500 >>>>>  SUNWsigcpp           Uncommitted    typesafe callback system for C++ >>>>>  SUNWncurses          Uncommitted    A CRT screen handling package >>>>>  SUNWlibmsr           Committed      Math & Microtasking Libraries >>>>> (Root) >>>>> >>>>> Appendix A - References >>>>>  [1] http://libtorrent.rakshasa.no/ >>>>> >>>>>  OSR ID# 11082 11083 >>>>>  RFE ID# 6814041 6814042 >>>>> >>>>> 6. Resources and Schedule >>>>>  6.4. Steering Committee requested information >>>>>      6.4.1. Consolidation C-team Name: >>>>>              SFW >>>>>  6.5. ARC review type: FastTrack >>>>>  6.6. ARC Exposure: open >>>>> >>>>> _______________________________________________ >>>>> opensolaris-arc mailing list >>>>> opensolaris-arc@opensolaris.org >>>>> >>>> >>>> >>>> >>>> -- >>>> Andy >>>> http://blog.sartek.net >>> >>> >> >> >> >> -- >> Andy >> http://blog.sartek.net > > -- Andy http://blog.sartek.net From carlsonj@phorcys.east.sun.com Thu Jun 4 05:37:28 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n54CbRE5026873 for ; Thu, 4 Jun 2009 05:37: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 n54CbKBY015777 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@Sun.COM>; Thu, 4 Jun 2009 20:37:26 +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 <0KKP00J0JSEEGB00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Thu, 04 Jun 2009 05:37:26 -0700 (PDT) Received: from dm-east-01.east.sun.com ([129.148.9.192]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KKP00JS5SED1Y50@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Thu, 04 Jun 2009 05:37:25 -0700 (PDT) Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143]) by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n54CbMqL061462; Thu, 04 Jun 2009 08:37:22 -0400 (EDT) Received: from phorcys.east.sun.com (phorcys.local [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n54CaC5F003022; Thu, 04 Jun 2009 08:36:12 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n54CaCSX003019; Thu, 04 Jun 2009 08:36:12 -0400 (EDT) Date: Thu, 04 Jun 2009 08:36:12 -0400 From: James Carlson Subject: Re: rtorrent & libtorrent [PSARC/2009/336 FastTrack timeout 06/10/2009] In-reply-to: <56dc2e760906040245r8d33301o9b98b894362b62f4@mail.gmail.com> To: Andras Barna Cc: alex zhang , PSARC-ext@sun.com, James Walker Message-id: <18983.49084.803425.588007@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.4.1.325704 References: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> <56dc2e760906030325v1bac1da8ha099414c951a5ef3@mail.gmail.com> <381F38E0-FEC4-495D-B7B2-E54102F4682A@Sun.COM> <56dc2e760906040051l4a05d9a2o34924b2e9fb0dab9@mail.gmail.com> <0639CAC0-8E97-4BFF-B925-80B089E20E29@Sun.COM> <56dc2e760906040245r8d33301o9b98b894362b62f4@mail.gmail.com> Status: RO Content-Length: 849 Andras Barna writes: > yeap > they have libtorrent-rasterbar.so for libtorrent-rastebar > and for rakshasa's simply libtorrent. so we can go this way too (if > noone has other idea(s)) If the library isn't really well-accepted in the open source community (i.e., it has just one consumer *and* there's an alternative that has many consumers), then making it a static library makes a lot more sense to me. That way, you don't have to deal with either the package naming or the /usr/lib real estate issues. You can always break it back apart later and deliver it as a dynamic library if you find that someone else needs it. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Huawei.Zhang@sun.com Thu Jun 4 18:58:12 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n551wC6W006608 for ; Thu, 4 Jun 2009 18:58:12 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n551wAoj025362 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Thu, 4 Jun 2009 18:58:12 -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 <0KKQ00A0JTH0LH00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 04 Jun 2009 18:58:12 -0700 (PDT) Received: from sineb-mail-2.sun.com ([192.18.19.7]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KKQ003EUTGZNC60@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 04 Jun 2009 18:58:12 -0700 (PDT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n551wBRp006770 for ; Fri, 05 Jun 2009 01:58:11 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KKQ00G00TBY8D00@mail-apac.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Fri, 05 Jun 2009 09:58:11 +0800 (SGT) Received: from [129.158.144.119] ([unknown] [129.158.144.119]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KKQ005TITGXF000@mail-apac.sun.com>; Fri, 05 Jun 2009 09:58:11 +0800 (SGT) Date: Fri, 05 Jun 2009 09:58:07 +0800 From: alex zhang Subject: Re: rtorrent & libtorrent [PSARC/2009/336 FastTrack timeout 06/10/2009] In-reply-to: <18983.49084.803425.588007@gargle.gargle.HOWL> Sender: Huawei.Zhang@sun.com To: James Carlson Cc: Andras Barna , PSARC-ext@sun.com, James Walker Message-id: MIME-version: 1.0 X-Mailer: Apple Mail (2.935.3) Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> <56dc2e760906030325v1bac1da8ha099414c951a5ef3@mail.gmail.com> <381F38E0-FEC4-495D-B7B2-E54102F4682A@Sun.COM> <56dc2e760906040051l4a05d9a2o34924b2e9fb0dab9@mail.gmail.com> <0639CAC0-8E97-4BFF-B925-80B089E20E29@Sun.COM> <56dc2e760906040245r8d33301o9b98b894362b62f4@mail.gmail.com> <18983.49084.803425.588007@gargle.gargle.HOWL> Status: RO Content-Length: 1599 Hi all Thanks for the reply. A good news, it seem that this isn't a problem now. I just download the other libtorrent -- libtorrent- rasterbar-0.14.4.tar.gz, after compile it, I saw it generate a library named libtorrent- rasterbar.so In its compile options, I saw this define: -DPACKAGE_NAME=\"libtorrent- rasterbar\" also the include directory it exported is named "libtorrent", while our libtorrent's include directory named "torrent". That means there is not any conflict between both "libtorrent" now. When we try to port libtorrent-rasterbar later, we can give it an other package name : SUNWlibtorrent-rasterbar. Thanks - Alex On Jun 4, 2009, at 8:36 PM, James Carlson wrote: > Andras Barna writes: >> yeap >> they have libtorrent-rasterbar.so for libtorrent-rastebar >> and for rakshasa's simply libtorrent. so we can go this way too (if >> noone has other idea(s)) > > If the library isn't really well-accepted in the open source community > (i.e., it has just one consumer *and* there's an alternative that has > many consumers), then making it a static library makes a lot more > sense to me. That way, you don't have to deal with either the package > naming or the /usr/lib real estate issues. > > You can always break it back apart later and deliver it as a dynamic > library if you find that someone else needs it. > > -- > James Carlson, Solaris Networking > > Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 > 2084 > MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 > 1677 From James.Walker@sun.com Thu Jun 4 23:34:12 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n556YB5G008345 for ; Thu, 4 Jun 2009 23:34:12 -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 n556Y3iJ028332 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 5 Jun 2009 14:34:10 +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 <0KKR0060568YV100@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 04 Jun 2009 23:34:10 -0700 (PDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KKR0067T68XH800@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 04 Jun 2009 23:34:09 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n556Y9jf010447 for ; Fri, 05 Jun 2009 06:34:09 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KKR00L0061PNF00@mail-amer.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Fri, 05 Jun 2009 00:34:09 -0600 (MDT) Received: from c-67-166-22-238.hsd1.co.comcast.net ([unknown] [129.150.32.38]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KKR00HLI68XY1B0@mail-amer.sun.com>; Fri, 05 Jun 2009 00:34:09 -0600 (MDT) Date: Fri, 05 Jun 2009 00:34:09 -0600 From: Jim Walker Subject: Re: rtorrent & libtorrent [PSARC/2009/336 FastTrack timeout 06/10/2009] In-reply-to: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> Sender: James.Walker@sun.com To: James Walker Cc: PSARC-ext@sun.com, Huawei.Zhang@sun.com Reply-to: James.Walker@sun.com Message-id: <4A28BC61.8070804@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) Status: RO Content-Length: 328 James Walker wrote: > I'm sponsoring this familiarity case for Alex Zhang. The requested > release binding is minor. The man pages have been posted in the > materials directory. The OpenSSL contract link will be posted after > it is approved. I added the approved openssl contract link to the materials directory. Cheers, Jim From James.Walker@sun.com Thu Jun 11 18:48:02 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n5C1m1Gd019520 for ; Thu, 11 Jun 2009 18:48:01 -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.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5C1lwad021555 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 12 Jun 2009 02:48:00 +0100 (BST) 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 <0KL300A0NRNYDY00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 11 Jun 2009 19:47:58 -0600 (MDT) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KL300IALRNXBUC0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Thu, 11 Jun 2009 19:47:57 -0600 (MDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5C1lvU5001334 for ; Fri, 12 Jun 2009 01:47:57 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KL300800RGSR200@mail-amer.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Thu, 11 Jun 2009 19:47:57 -0600 (MDT) Received: from c-67-166-22-238.hsd1.co.comcast.net ([unknown] [129.150.33.113]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KL3003SVRNWKGA0@mail-amer.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Thu, 11 Jun 2009 19:47:56 -0600 (MDT) Date: Thu, 11 Jun 2009 19:47:56 -0600 From: Jim Walker Subject: Re: rtorrent & libtorrent [PSARC/2009/336 FastTrack timeout 06/10/2009] In-reply-to: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> Sender: James.Walker@sun.com To: PSARC-ext@sun.com Cc: Huawei.Zhang@sun.com Reply-to: James.Walker@sun.com Message-id: <4A31B3CC.2050101@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200906031013.n53ADuDq008277@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) Status: RO Content-Length: 117 All issues have been addressed and the timeout has been reached. I'm marking this case closed approved. Cheers, Jim