Re: postgresql83-server - Further Woes

2019-11-04 Thread Bill Cole
On 4 Nov 2019, at 17:22, Michael Newman via macports-users wrote: The only solution offered by the developer of DetectX was to tell DetectX to ignore changes to macports plist files. That seems to defeat the purpose of DetectX. DetectX is supposed to warn you of possible nefarious changes to

Re: postgresql83-server - Further Woes

2019-11-04 Thread Michael Newman via macports-users
The only solution offered by the developer of DetectX was to tell DetectX to ignore changes to macports plist files. That seems to defeat the purpose of DetectX. DetectX is supposed to warn you of possible nefarious changes to your system. Choosing to ignore a possible problem is no solution.

Re: postgresql83-server - Further Woes

2019-11-03 Thread Michael Newman via macports-users
I have a license for and use DetectX Swift. I wrote to the developer. Phil’s full reply is below. I am a bit wary about simply telling DetectX to ignore this. Something is going on and I want to know what it is. I’ve written Phil back to let him know what I learned from this list. (I am gratef

Re: postgresql83-server - Further Woes

2019-11-03 Thread Al Varnell via macports-users
Recommend you contact the Developer at >. Phil has been a colleague of mine for several years and very responsive. Operates out of Australia. You should be aware that if you are actually using the older DetectX rather thanDetectX Swift,

Re: postgresql83-server - Further Woes

2019-11-03 Thread Bill Cole
On 3 Nov 2019, at 5:46, Michael Newman via macports-users wrote: Perhaps this is a bug in DetectX, It very much sounds like that. Stating that a file which no longer exists has "changed" might be technically correct, but it certainly is not clear. Perhaps the developer of DetectX can illumin

Re: postgresql83-server - Further Woes

2019-11-03 Thread Michael Newman via macports-users
I have uninstalled the port, but DetectX keeps telling me that the plist has been changed. If it only happened once when I still had the port installed I’d say, yeah, problem solved. But when the plist keeps getting changed after the port has been uninstalled I have to wonder what’s happening.

Re: postgresql83-server - Further Woes

2019-11-03 Thread Al Varnell via macports-users
I'm not sure what solution you are seeking here. DetectX will record each and every time a key file is added or removed to/from selected locations, which includes all LaunchAgents, LaunchDaemons, Applications and a few other places where malware is often installed. When you see such a notice, if

Re: postgresql83-server - Further Woes

2019-11-03 Thread Ryan Schmidt
On Nov 3, 2019, at 04:19, Michael Newman wrote: > Locate did not find this plist on the boot volume. It did find it in a Carbon > Copy Cloner SafetyNet directory on a backup drive. > > MrMuscle:home mnewman$ locate org.macports.postgresql83-server.plist > /Volumes/Clorox2/_CCC SafetyNet/2019-

Re: postgresql83-server - Further Woes

2019-11-03 Thread Michael Newman via macports-users
Thank you. Locate did not find this plist on the boot volume. It did find it in a Carbon Copy Cloner SafetyNet directory on a backup drive. MrMuscle:home mnewman$ locate org.macports.postgresql83-server.plist /Volumes/Clorox2/_CCC SafetyNet/2019-10-30 (October 30) 01-00-52/Library/LaunchDaemons

Re: postgresql83-server - Further Woes

2019-11-03 Thread Ryan Schmidt
On Nov 3, 2019, at 02:10, Michael Newman wrote: > Periodically DetectX generates the following message: > > = > Items: org.macports.postgresql83-server.plist > Some background launch items have just been changed on your mac which can > affect its security > = > > I had previously un

postgresql83-server - Further Woes

2019-11-03 Thread Michael Newman via macports-users
Periodically DetectX generates the following message: = Items: org.macports.postgresql83-server.plist Some background launch items have just been changed on your mac which can affect its security = I had previously uninstalled postgresql83-server and can’t find org.macports.postgresql8