The drsocssl connection type is NOT for HDR/RSS/SDS communication, it is for DRDA connections from DB2 development stack clients. Use the onsocssl connection types for HDR/RSS/SDS and native Informix clients.

The traffic between the primary and secondary servers contains your data which may or may not be sensitive data. Yes it is in binary, but it is completely readable. The traffic is mostly logical log records and there have been at least two applications written, besides onlog, that can read and display logical log data, so not hard at all. That is why one would encrypt the connections between the primary and secondary. You should also use a dedicated connection marked with the s=6 option to prevent any clients from connecting to that port.

Art

The drsocssl connection type is NOT for HDR/RSS/SDS communication, it is for DRDA connections from DB2 development stack clients. Use the onsocssl connection types for HDR/RSS/SDS and native Informix clients.

The traffic between the primary and secondary servers contains your data which may or may not be sensitive data. Yes it is in binary, but it is completely readable. The traffic is mostly logical log records and there have been at least two applications written, besides onlog, that can read and display logical log data, so not hard at all. That is why one would encrypt the connections between the primary and secondary. You should also use a dedicated connection marked with the s=6 option to prevent any clients from connecting to that port.

Art

Hi Art,

Can you naked the 2 applications that can decode logs?

Regards,

David.

The drsocssl connection type is NOT for HDR/RSS/SDS communication, it is for DRDA connections from DB2 development stack clients. Use the onsocssl connection types for HDR/RSS/SDS and native Informix clients.

The traffic between the primary and secondary servers contains your data which may or may not be sensitive data. Yes it is in binary, but it is completely readable. The traffic is mostly logical log records and there have been at least two applications written, besides onlog, that can read and display logical log data, so not hard at all. That is why one would encrypt the connections between the primary and secondary. You should also use a dedicated connection marked with the s=6 option to prevent any clients from connecting to that port.

Art

David:

Paul Watson wrote one and another was a commercial product by one of the Informix old timers, but I've lost the link I had to his site.

Art

Hi Art,

Can you naked the 2 applications that can decode logs?

Regards,

David.

David:

Paul Watson wrote one and another was a commercial product by one of the Informix old timers, but I've lost the link I had to his site.

Art

Hi Art,

Can you naked the 2 applications that can decode logs?

Regards,

David.

The drsocssl connection type is NOT for HDR/RSS/SDS communication, it is for DRDA connections from DB2 development stack clients. Use the onsocssl connection types for HDR/RSS/SDS and native Informix clients.

The traffic between the primary and secondary servers contains your data which may or may not be sensitive data. Yes it is in binary, but it is completely readable. The traffic is mostly logical log records and there have been at least two applications written, besides onlog, that can read and display logical log data, so not hard at all. That is why one would encrypt the connections between the primary and secondary. You should also use a dedicated connection marked with the s=6 option to prevent any clients from connecting to that port.

Art