[Info-ingres] Snooping on another user session

[Adrian Williamson]

Wireshark?

 

I've used this network sniffing software in the past to look at Ingres
connection details.

 

Some of it (e.g. opening a terminal session) is in text.

 

Download wireshark/winpcap and do a packet capture when you connect to
Ingres as a test.

 

I've notes somewhere if you need them.

 

 

 

From: info-ingres-bounces at lists.planetingres.org
<info-ingres-bounces at lists.planetingres.org> On Behalf Of Martin Bowes
Sent: 06 October 2020 10:57
To: 'Ingres lists' <info-ingres at lists.planetingres.org>
Subject: [Info-ingres] Snooping on another user session

 

Hi All,

 

I have a user whose connection details I wish to trap. Specifically their
setting of date_type_alias.

 

They are running a fairly complicated application and although we *could in
theory* get it recut to include a select dbmsinfo('date_type_alias'), in
practice that may be a lot harder than it sounds.

 

The error experienced by one (and only one) user would indicate they have
connected with date alias of ansidate. Yet a scan of their client config
says that should be ingresdate. I've trapped their connected activity with
sc930 on the two installations on which the application is working but have
not found any resetting of the date alias with a set date_alias 'ansidate'
either. 

 

Having looked at the session trace, I can provoke the error using a terminal
monitor connection, but only if I set date_alias 'ansidate'.

 

Ideas?

 

Martin Bowes   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.planetingres.org/pipermail/info-ingres/attachments/20201007/e6a512b6/attachment.html>