Jump to content

pequeno

Clients
  • Posts

    744
  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Posts posted by pequeno

  1. 3 hours ago, pequeno said:

    Thank you. Same problem with other language.

    SOLVED! With this procedure:

    1.- Make a copy of the English system language.

    2.- Download a copy of the second language.

    3.- Install a new version of English Copy. The new version file is the second language downloaded.

    4.- Remove second language.

    5.- Rename the English Copy language to second language name.

    Now works with second language selected.

    Thanks!

     

  2. Hello @AlexWebsites I have activated Web Application Firewall. with this configuration:

    Package: OWASP ModSecurity Core Rule Set - >Sensitivity:Medium -> Action:Challenge.

    The CloudFlare Firewall block the notification to the endpoint. This is the Log:

    25 Feb, 2020 23:31:03
    Challenge
    Ireland
    54.240.197.117
    WAF
    Ray ID
    56ad2093fb2f2973
    Method
    POST
    HTTP Version
    HTTP/1.1
    Host
    www.mywebsite.com
    Path
    /forum/applications/bouncer/interface/amazon/sns.php
    Query string
    Empty query string
    User agent
    Amazon Simple Notification Service Agent
    IP address
    54.240.197.117
    ASN
    AS16509 AMAZON-02
    Country
    Ireland
    Service
    WAF
    Rule ID
    OWASP Block (981176)
    Rule message
    Inbound Anomaly Score Exceeded (Total Score: 55, SQLi=6, XSS=15)
    Rule group
    OWASP Inbound Blocking
    Action taken
    Challenge
    Export event JSON
    Additional logs
    26
    07 · No description available		Log	WAF
    03 · No description available		Log	WAF
    900001 · No description available	OWASP Setup	Log	WAF
    900002 · No description available	OWASP Setup	Log	WAF
    900006 · No description available	OWASP Setup	Log	WAF
    900012 · No description available	OWASP Setup	Log	WAF
    960010 · Request content type is not allowed by policy	OWASP HTTP Policy	Log	WAF
    960015 · Request Missing an Accept Header	OWASP Protocol Anomalies	Log	WAF
    960024 · Meta-Character Anomaly Detection Alert - Repetative Non-Word Characters	OWASP Generic Attacks	Log	WAF
    950120 · Possible Remote File Inclusion (RFI) Attack: Off-Domain Reference/Link	OWASP Generic Attacks	Log	WAF
    981133 · Prequalify PM	OWASP Generic Attacks	Log	WAF
    981305 · SQL from	OWASP SQL Injection Attacks	Log	WAF
    981257 · Detects MySQL comment-/space-obfuscated injections and backtick termination	OWASP SQL Injection Attacks	Log	WAF
    981245 · Detects basic SQL authentication bypass attempts 2/3	OWASP SQL Injection Attacks	Log	WAF
    981242 · Detects classic SQL injection probings 1/2	OWASP SQL Injection Attacks	Log	WAF
    981246 · Detects basic SQL authentication bypass attempts 3/3	OWASP SQL Injection Attacks	Log	WAF
    981243 · Detects classic SQL injection probings 2/2	OWASP SQL Injection Attacks	Log	WAF
    uri-981136 · Check simple XSS patterns	OWASP Uri XSS Attacks	Log	WAF
    981136 · Check simple XSS patterns	OWASP XSS Attacks	Log	WAF
    973333 · IE XSS Filters - Attack Detected	OWASP XSS Attacks	Log	WAF
    973344 · IE XSS Filters - Attack Detected	OWASP XSS Attacks	Log	WAF
    973332 · IE XSS Filters - Attack Detected	OWASP XSS Attacks	Log	WAF
    2000000 · Skip Joomla Rules	OWASP Slr Et Joomla Attacks	Log	WAF
    2000001 · Skip LFI Rules	OWASP Slr Et Lfi Attacks	Log	WAF
    2000004 · Skip SQLi Rules	OWASP Slr Et SQLi Attacks	Log	WAF
    2000006 · Skip XSS Rules	OWASP Slr Et XSS Attacks	Log	WAF

    The solution is create a Bypass Rule for the Firewall. In my case:

    Cloudflare_Bypass_Rule.thumb.png.74e00e994414b9e6005fb25390da184d.png

  3. On 1/19/2020 at 5:00 PM, stoo2000 said:

    our issue is very odd. It's like Amazon isn't sending the notification data despite SNS being correctly configured. We'll continue to investigate though!

    Hello, After nearly three months, we have solved the problem, thanks to the @stoo2000 invaluable help.

    I must publicly thank to @stoo2000 for the support. Answering each email, and even contacting himself with Amazon support.

    Finally It was a Cloudflare Firewall issue.
    I must emphasize the dedication, interest and time spent by @stoo2000 all this time.
    Thank you very much.

    Brad Pitt Kiss GIF

     

  4. 3 minutes ago, SJ77 said:

    Well that was a huge pain in the butt and there was no support given here.
    BUT, I got it working and it's AWESOME. My reputation is now squeaky clean!!

    For anyone willing to dive in and try to make this work with their Amazing SES account, the potential rewards are huge. It's worth it!!!

    Thank you @stoo2000 !!!!!

     

    image.thumb.png.b6b6bd87a2c7a97c6dd4a0a0e975f295.png

    I hope solved. @stoo2000 is is trying his best to make it work in Amazon SES, but we don't get it.

  5. 1 minute ago, AlexWebsites said:

    No, I don’t use an email protocol. You don’t need that for this app. Try deleting those. Are you using email with some other notification because email feedback forwarding from SES will send you an email on each instance if you need that. You don’t need to set up an email protocol in SNS for this app, only https, unless you need that for some reason.

    Right. I deleted the email subscription. I used it for information purposes only.

     

  6. 1 hour ago, AlexWebsites said:

    So if you send an email from that email address (same as what is used by IPS) to a bad email, you get an email notification that it bounced but NOT an entry into the database via the endpoint, correct?

    Yes, this is my configuration:

    endpoint.png.ca4983f3bab17643be8ef5e12fcf14d6.png

    Rebotes=bounce

    Quejas=complaint

    In this case I only receive it by email.

    @stoo2000 tested it obtain the same result.

    1 hour ago, AlexWebsites said:

    That’s all I can think of, I’m really not sure why it’s not working for you. It works for me. 

    Works for you at the email and at the endpoint at the same time?

  7. Just now, AlexWebsites said:

    Make sure you are subscribing your verified outgoing email address and not domain name only.

    Yes, I verified domain and email address.

    I have separate subscription for bounce and complaint, and the email notifications reached me correctly.

    Adding endpoint for mailbounce, the notifications works for email but not for endpoint. Following the @stoo2000 recommendations I have deleted subscriptions to the mail and left only the endpoint.

  8. On 10/13/2019 at 7:57 PM, AlexWebsites said:

    I finally seem to have it working on my end. User error by me in terms of setting up notifications in SNS, but I can verify that SES is working and bounces are getting processed. I had to read up on how SES/SNS works. My suggestion to anyone using this in the future when its released, is to set up bounce and complaint SNS to an email notification and verify that it is sending via email/working. Then create a subscription to the app endpoint provided. Thank you @stoo2000!

    Hello, I tested the last version and I have a problem with SNS.

    I have both, email and HTTPS endpoint subscriptions on my topics, the HTTPS endpoint subscription will not receive any data. @stoo2000 recommends me just leave https subscription only. 

    Can someone confirm this to me. Does anyone have an email and https endopoint subscription and does it work?

    Thanks.

     

  9. On 11/4/2019 at 12:50 AM, stoo2000 said:

    To be honest, I'm a little disappointed that only one person contacted me for access to test SNS integration. I'd have liked to test it and tweak it more, but that's not possible without any feedback.

    The main code behind the app is getting some major changes at the moment which, but I think I may just end up releasing a minor update with the SNS code in it, it'll be exactly the same as what you could have had on request. You'd need to figure out how to make SNS/SES work though, that's not something I can help you with.

    Thanks for the new version with Amazon SES support. I can not wait to try it.

  10. On 11/4/2019 at 12:50 AM, stoo2000 said:

    To be honest, I'm a little disappointed that only one person contacted me for access to test SNS integration. I'd have liked to test it and tweak it more, but that's not possible without any feedback.

    The main code behind the app is getting some major changes at the moment which, but I think I may just end up releasing a minor update with the SNS code in it, it'll be exactly the same as what you could have had on request. You'd need to figure out how to make SNS/SES work though, that's not something I can help you with.

    Hello @stoo2000, we are a lot of people waiting for it to work with amazon SES.

    In my case it is a production site that sends hundreds of emails per day, but I can test if you wish.

  11. 2 minutes ago, AlexWebsites said:

    For anyone planing to use this app with SES, that would be my one big suggestion... get Amazon SNS working now to your email address. Learn how to create topics and subscribe to them. Read up with Amazon SES/SNS. Its not difficult. Once you have it working and you are receiving Bounce/Complaint notifications to your email, you'll know that notifications are working from Amazon SES/SNS. You will then basically switch your subscription method from email to an https (endpoint url for your site that will receive these notifications within this bouncer app).

    If you are using SES now, set up and test email notifications with SNS by each sending email address, not domain name. My main issue why I could not get this working was because I set up SNS to my domain name instead of the sending email addresses. I just figured that out today after messing with Amazon on and off this week. I had thought it was "catch-all" by domain name until I read online each email address has to be subscribed to a topic to send out notifications. 

    No problem, I am currently using notifications to my emails without problems.

     

    26 minutes ago, AlexWebsites said:

    Then create a subscription to the app endpoint provided.

    This is the part that I don't understand

  12. 2 minutes ago, AlexWebsites said:

    I finally seem to have it working on my end. User error by me in terms of setting up notifications in SNS, but I can verify that SES is working and bounces are getting processed. I had to read up on how SES/SNS works. My suggestion to anyone using this in the future when its released, is to set up bounce and complaint SNS to an email notification and verify that it is sending via email/working. Then create a subscription to the app endpoint provided. Thank you @stoo2000!

    Thank you. I am looking forward to using it with SES. I hope you can explain better how to configure it SNS and subscription to the endpoint.

×
×
  • Create New...