[jira] [Created] (TS-1010) strlcpy breaks WCCP Security

2011-11-02 Thread Alan M. Carroll (Created) (JIRA) 
strlcpy breaks WCCP Security


 Key: TS-1010
 URL: https://issues.apache.org/jira/browse/TS-1010
 Project: Traffic Server
  Issue Type: Bug
  Components: Network
Affects Versions: 3.1.0
Reporter: Alan M. Carroll
Assignee: Alan M. Carroll


The requirements for WCCP security key handling are precisely those of strncpy -
* The buffer must be zero padded.
* The terminating nul must *not* be copied if the key fills the buffer.
Rather than doing something complex with strlcpy to satisfy these requirements 
it is much easier to simply use strncpy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (TS-1010) strlcpy breaks WCCP Security

2011-11-02 Thread Alan M. Carroll (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TS-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan M. Carroll resolved TS-1010.
-

   Resolution: Fixed
Fix Version/s: 3.1.1

Changed back to strncpy.

> strlcpy breaks WCCP Security
> 
>
> Key: TS-1010
> URL: https://issues.apache.org/jira/browse/TS-1010
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Network
>Affects Versions: 3.1.0
>Reporter: Alan M. Carroll
>Assignee: Alan M. Carroll
>  Labels: wccp
> Fix For: 3.1.1
>
>
> The requirements for WCCP security key handling are precisely those of 
> strncpy -
> * The buffer must be zero padded.
> * The terminating nul must *not* be copied if the key fills the buffer.
> Rather than doing something complex with strlcpy to satisfy these 
> requirements it is much easier to simply use strncpy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (TS-984) LogFile::roll crash at Machine::instance

2011-11-02 Thread Alan M. Carroll (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/TS-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142565#comment-13142565
 ] 

Alan M. Carroll commented on TS-984:


Problem identified and fixed.

> LogFile::roll crash at Machine::instance
> 
>
> Key: TS-984
> URL: https://issues.apache.org/jira/browse/TS-984
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Logging
>Affects Versions: 3.1.0
>Reporter: Zhao Yongming
>Assignee: Alan M. Carroll
>  Labels: crash
> Fix For: 3.1.1
>
> Attachments: ts-984.diff
>
>
> this is a strange error when I testing the current trunk with logging 
> colation server enabled:
> {code}
> [Oct 16 01:24:48.643] Server {0x2b4967f51760} WARNING: File 
> /var/log/trafficserver/ex_squid.log will be rolled because a LogObject with 
> different format is requesting the same filename
> FATAL: Machine.cc:37: failed assert `_instance || !"Machine instance accessed 
> before initialization"`
> /usr/bin/traffic_server - STACK TRACE: 
> /usr/lib64/trafficserver/libtsutil.so.3(ink_fatal_va+0xc5)[0x2b49651a5109]
> /usr/lib64/trafficserver/libtsutil.so.3(ink_fatal+0xa3)[0x2b49651a51bb]
> /usr/lib64/trafficserver/libtsutil.so.3(_ink_assert+0xc2)[0x2b49651a3aee]
> /usr/bin/traffic_server(Machine::instance()+0x24)[0x634a04]
> /usr/bin/traffic_server(LogFile::roll(long, long)+0x230)[0x5f8138]
> /usr/bin/traffic_server(LogObjectManager::_solve_filename_conflicts(LogObject*,
>  int)+0x489)[0x603263]
> /usr/bin/traffic_server(LogObjectManager::_manage_object(LogObject*, bool, 
> int)+0x126)[0x6029ea]
> /usr/bin/traffic_server(LogObjectManager::manage_object(LogObject*, 
> int)+0x2d)[0x5e9e27]
> /usr/bin/traffic_server(LogConfig::read_xml_log_config(int)+0x3189)[0x5f28c9]
> /usr/bin/traffic_server(LogConfig::setup_log_objects()+0x229)[0x5edd63]
> /usr/bin/traffic_server(LogConfig::init(LogConfig*)+0x254)[0x5ec3ea]
> /usr/bin/traffic_server(Log::init(int)+0x30c)[0x5e8134]
> /usr/bin/traffic_server(main+0xb6a)[0x5161a4]
> /lib64/libc.so.6(__libc_start_main+0xfd)[0x2b49673b4ebd]
> /usr/bin/traffic_server[0x4cc789]
> {code}
> there is two problem here:
> 1, why the machine is not initialized?
> 2, what does "WARNING: File /var/log/trafficserver/ex_squid.log will be 
> rolled because a LogObject with different format is requesting the same 
> filename" mean? is that harm?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (TS-984) LogFile::roll crash at Machine::instance

2011-11-02 Thread Alan M. Carroll (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TS-984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan M. Carroll resolved TS-984.


Resolution: Fixed

> LogFile::roll crash at Machine::instance
> 
>
> Key: TS-984
> URL: https://issues.apache.org/jira/browse/TS-984
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Logging
>Affects Versions: 3.1.0
>Reporter: Zhao Yongming
>Assignee: Alan M. Carroll
>  Labels: crash
> Fix For: 3.1.1
>
> Attachments: ts-984.diff
>
>
> this is a strange error when I testing the current trunk with logging 
> colation server enabled:
> {code}
> [Oct 16 01:24:48.643] Server {0x2b4967f51760} WARNING: File 
> /var/log/trafficserver/ex_squid.log will be rolled because a LogObject with 
> different format is requesting the same filename
> FATAL: Machine.cc:37: failed assert `_instance || !"Machine instance accessed 
> before initialization"`
> /usr/bin/traffic_server - STACK TRACE: 
> /usr/lib64/trafficserver/libtsutil.so.3(ink_fatal_va+0xc5)[0x2b49651a5109]
> /usr/lib64/trafficserver/libtsutil.so.3(ink_fatal+0xa3)[0x2b49651a51bb]
> /usr/lib64/trafficserver/libtsutil.so.3(_ink_assert+0xc2)[0x2b49651a3aee]
> /usr/bin/traffic_server(Machine::instance()+0x24)[0x634a04]
> /usr/bin/traffic_server(LogFile::roll(long, long)+0x230)[0x5f8138]
> /usr/bin/traffic_server(LogObjectManager::_solve_filename_conflicts(LogObject*,
>  int)+0x489)[0x603263]
> /usr/bin/traffic_server(LogObjectManager::_manage_object(LogObject*, bool, 
> int)+0x126)[0x6029ea]
> /usr/bin/traffic_server(LogObjectManager::manage_object(LogObject*, 
> int)+0x2d)[0x5e9e27]
> /usr/bin/traffic_server(LogConfig::read_xml_log_config(int)+0x3189)[0x5f28c9]
> /usr/bin/traffic_server(LogConfig::setup_log_objects()+0x229)[0x5edd63]
> /usr/bin/traffic_server(LogConfig::init(LogConfig*)+0x254)[0x5ec3ea]
> /usr/bin/traffic_server(Log::init(int)+0x30c)[0x5e8134]
> /usr/bin/traffic_server(main+0xb6a)[0x5161a4]
> /lib64/libc.so.6(__libc_start_main+0xfd)[0x2b49673b4ebd]
> /usr/bin/traffic_server[0x4cc789]
> {code}
> there is two problem here:
> 1, why the machine is not initialized?
> 2, what does "WARNING: File /var/log/trafficserver/ex_squid.log will be 
> rolled because a LogObject with different format is requesting the same 
> filename" mean? is that harm?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Issue Comment Edited] (TS-984) LogFile::roll crash at Machine::instance

2011-11-02 Thread Alan M. Carroll (Issue Comment Edited) (JIRA) 

[ 
https://issues.apache.org/jira/browse/TS-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142565#comment-13142565
 ] 

Alan M. Carroll edited comment on TS-984 at 11/2/11 9:27 PM:
-

Problem identified and fixed. r1196806

  was (Author: amc):
Problem identified and fixed.
  
> LogFile::roll crash at Machine::instance
> 
>
> Key: TS-984
> URL: https://issues.apache.org/jira/browse/TS-984
> Project: Traffic Server
>  Issue Type: Bug
>  Components: Logging
>Affects Versions: 3.1.0
>Reporter: Zhao Yongming
>Assignee: Alan M. Carroll
>  Labels: crash
> Fix For: 3.1.1
>
> Attachments: ts-984.diff
>
>
> this is a strange error when I testing the current trunk with logging 
> colation server enabled:
> {code}
> [Oct 16 01:24:48.643] Server {0x2b4967f51760} WARNING: File 
> /var/log/trafficserver/ex_squid.log will be rolled because a LogObject with 
> different format is requesting the same filename
> FATAL: Machine.cc:37: failed assert `_instance || !"Machine instance accessed 
> before initialization"`
> /usr/bin/traffic_server - STACK TRACE: 
> /usr/lib64/trafficserver/libtsutil.so.3(ink_fatal_va+0xc5)[0x2b49651a5109]
> /usr/lib64/trafficserver/libtsutil.so.3(ink_fatal+0xa3)[0x2b49651a51bb]
> /usr/lib64/trafficserver/libtsutil.so.3(_ink_assert+0xc2)[0x2b49651a3aee]
> /usr/bin/traffic_server(Machine::instance()+0x24)[0x634a04]
> /usr/bin/traffic_server(LogFile::roll(long, long)+0x230)[0x5f8138]
> /usr/bin/traffic_server(LogObjectManager::_solve_filename_conflicts(LogObject*,
>  int)+0x489)[0x603263]
> /usr/bin/traffic_server(LogObjectManager::_manage_object(LogObject*, bool, 
> int)+0x126)[0x6029ea]
> /usr/bin/traffic_server(LogObjectManager::manage_object(LogObject*, 
> int)+0x2d)[0x5e9e27]
> /usr/bin/traffic_server(LogConfig::read_xml_log_config(int)+0x3189)[0x5f28c9]
> /usr/bin/traffic_server(LogConfig::setup_log_objects()+0x229)[0x5edd63]
> /usr/bin/traffic_server(LogConfig::init(LogConfig*)+0x254)[0x5ec3ea]
> /usr/bin/traffic_server(Log::init(int)+0x30c)[0x5e8134]
> /usr/bin/traffic_server(main+0xb6a)[0x5161a4]
> /lib64/libc.so.6(__libc_start_main+0xfd)[0x2b49673b4ebd]
> /usr/bin/traffic_server[0x4cc789]
> {code}
> there is two problem here:
> 1, why the machine is not initialized?
> 2, what does "WARNING: File /var/log/trafficserver/ex_squid.log will be 
> rolled because a LogObject with different format is requesting the same 
> filename" mean? is that harm?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (TS-1011) SSL doesn't work on Solaris

2011-11-02 Thread Theo Schlossnagle (Created) (JIRA) 
SSL doesn't work on Solaris
---

 Key: TS-1011
 URL: https://issues.apache.org/jira/browse/TS-1011
 Project: Traffic Server
  Issue Type: Bug
 Environment: Solaris 10+
Reporter: Theo Schlossnagle
Assignee: Theo Schlossnagle


Inbound SSL connections hang during handshake as the file descriptor isn't 
refreshed in io system.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (TS-989) Update logging to be IPv6 compatible.

2011-11-02 Thread Alan M. Carroll (Resolved) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TS-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan M. Carroll resolved TS-989.


Resolution: Fixed

> Update logging to be IPv6 compatible.
> -
>
> Key: TS-989
> URL: https://issues.apache.org/jira/browse/TS-989
> Project: Traffic Server
>  Issue Type: Improvement
>  Components: Logging
>Affects Versions: 3.1.0
>Reporter: Alan M. Carroll
>Assignee: Alan M. Carroll
>  Labels: ipv6, logging
> Fix For: 3.1.2
>
>
> Change logging to support IPv6 data.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (TS-561) Origin-server side IPv6 support

2011-11-02 Thread Alan M. Carroll (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TS-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan M. Carroll updated TS-561:
---

Fix Version/s: (was: 3.1.1)
   3.1.2

> Origin-server side IPv6 support
> ---
>
> Key: TS-561
> URL: https://issues.apache.org/jira/browse/TS-561
> Project: Traffic Server
>  Issue Type: New Feature
>  Components: Network
> Environment: Linux 4.x
>Reporter: Anirban Roy
>Assignee: Alan M. Carroll
> Fix For: 3.1.2
>
>
> raffic Server used as forward proxy in a number of places including web 
> crawling and feed fetching applications. In those applications, 
> (origin)server side IPv6 support is desirable. As the Internet running out of 
> IPv4 addresses, the new sites will run on IPv6 stack. The applications 
> pulling content using traffic server should be able to do so in the changing 
> scenario.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira