View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005619 | Composr | securitylogging | public | 2024-02-21 03:26 | 2024-08-04 22:49 |
| Reporter | Patrick Schmalstig | Assigned To | Patrick Schmalstig | ||
| Severity | Feature-request | ||||
| Status | assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0005619: Scamalytics integration | ||||
| Description | I think it would be useful to integrate the Scamalytics API into Composr. https://scamalytics.com It could be a new item on the investigate user page (Scamalytics would not be queried automatically, but an admin can click to query). There could also perhaps be a configuration option allowing site admins to specify whether or not to do a Scamalytics lookup on any IP addresses that trigger a hack attack and include the results in the hack attack message. We might also consider the option to use Scamalytics in the antispam. However, we would strongly advise against this due to potential false-positives and because it would significantly increase the number of queries performed. Composr should cache Scamalytics lookups to reduce API query hits as Scamalytics only allows a certain number of queries per month. Perhaps set the cache lifetime to 1 week. | ||||
| Tags | Roadmap: Sponsorship, Roadmap: v11 partial implementation | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
|
|
For v11 at least, I think all I'm going to do is just include a link to perform an IP lookup directly on their site (from investigate user). Their site gives a lot of useful information which I'm unsure is included in the API itself. |
|
|
Marking as sponsorship. While I'm planning to do the above comment (simple link to the site), if anyone wants deeper API integration of scamalytics, they should sponsor this issue. |
|
|
Given this is a commercial service, I'd only really want to see it integrated as a non-bundled addon (aforementioned simple link is okay). Possibly new hook(s) would need implementing to allow that kind of thing to work. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-02-21 03:26 | Patrick Schmalstig | New Issue | |
| 2024-02-21 03:26 | Patrick Schmalstig | Status | non-assigned => assigned |
| 2024-02-21 03:26 | Patrick Schmalstig | Assigned To | => Patrick Schmalstig |
| 2024-02-21 03:26 | Patrick Schmalstig | Description Updated | View Revisions |
| 2024-02-21 03:28 | Patrick Schmalstig | Description Updated | View Revisions |
| 2024-02-21 03:36 | Patrick Schmalstig | Tag Attached: Roadmap: v11 partial implementation | |
| 2024-02-21 03:37 | Patrick Schmalstig | Note Added: 0008343 | |
| 2024-03-30 14:47 | Patrick Schmalstig | Tag Attached: Roadmap: Sponsorship | |
| 2024-03-30 14:48 | Patrick Schmalstig | Note Added: 0008496 | |
| 2024-08-04 22:49 | Chris Graham | Note Added: 0009094 |
