31–40 of 68 posts
"That's expensive, and complicated! We'll just do regular audits and be fine."
[some time later]
"Someone exfiltrated all our data using mysqldump!"
= /
Moral of the story. For my sake: Check the access logs. Regularly.
Can't test the product they try to promote because emails with a `+` in them are not valid.
Email validation regexes are so annoying. Everyone ought to just use .+@.+ as their validation regex and not be more strict than that. Beyond that just queue and try to deliver the email. Tell the user than an email should arrive shortly and that if it doesn’t they should check their spam folder and that they should check that they gave the correct email address. When you say this you repeat the email address that th…
Moral of the story. For my sake: Check the access logs. Regularly.
Why, are you bored? They can just access the db from an internal host that already has connections and exfiltrate from there. That's part of why people retrieve data using holes in web apps - it looks like a spike in normal traffic.
A little update on the service Security Guardian after the publication of this post. Thanks to Hacker News and its incredible community, there have been a massive number of new users. We are working on adding more resources to the infrastructure to make the scans quicker. For now, it is possible that some of you have to wait some hours before receiving the first results. Thanks for trying our new product, we hope to…
> Then, they blocked the IP address of our scanner so we could not scan their server anymore. Long time lurker, made an account just to ask this: What are your comments on this unprofessional reaction from the Swiss?
currently infoteam.ch seems to be hosted on METANET (metanet.ch). Is there anyone who can deny or confirm that this is the provider they don't want to mention? source: nslookup infoteam.ch; whois 80.74.143.113
(I do think, however, that it would be important to know.)
Can't test the product they try to promote because emails with a `+` in them are not valid.
Email validation regexes are so annoying. Everyone ought to just use .+@.+ as their validation regex and not be more strict than that. Beyond that just queue and try to deliver the email. Tell the user than an email should arrive shortly and that if it doesn’t they should check their spam folder and that they should check that they gave the correct email address. When you say this you repeat the email address that th…
codetrotter@example
code@trotter@example.com
code trotter@example.com
codetrotter@example..com
codetrotter@example.com.
.codetrotter@example.com
My company runs a website that has elderly people signing up for newsletters. The client is paranoid about not getting every last drop of possible data, and raises hell for every email address that isn't deliverable. There are LOTS of ways to easily ruin a simple email address.
Their vulnerability scanner is basically an on-demand DOS attack. Tried it on my site and almost brought it down
For whoever was wondering who this provider is: according to whois-nslookup-mxtoolbox_arin_lookup, the server hosting infoteam.ch is provided by metanet (metanet.ch) Not trying to ruin their business, but they should consider handling issues like this one properly.
Maybe I’m wrong but the PTR of the IP seems to be in a spam blacklist: https://apility.io/search?q=infoteam.ch https://apility.io/search?q=80.74.143.113 https://apility.io/search?q=dynco.ch This thing happens sometimes, specially if you use a shared hosting. Recently using a well known cloud provider the Public IP address assigned was in a spam blacklist! It’s a good idea to have a look at your IP and domains frequen…