/dports/security/ossec-hids-server/ossec-hids-3.6.0/etc/rules/log-entries/ |
H A D | mail-alerts | 22 …r [200.207.91.189] (may be forged), reject=550 5.7.1 <andre.pereira@gerdau.com.br>... Relaying den… 23 …r [200.207.91.189] (may be forged), reject=550 5.7.1 <andre.nichele@gerdau.com.br>... Relaying den… 24 … [200.207.91.189] (may be forged), reject=550 5.7.1 <andre.celiberto@gerdau.com.br>... Relaying de… 39 …2=127.0.0.4, relay=120119.user.veloxzone.com.br [201.29.120.119] (may be forged), reject=550 5.7.1… 40 …2=127.0.0.4, relay=120119.user.veloxzone.com.br [201.29.120.119] (may be forged), reject=550 5.7.1… 41 …2=127.0.0.4, relay=120119.user.veloxzone.com.br [201.29.120.119] (may be forged), reject=550 5.7.1… 42 …2=127.0.0.4, relay=120119.user.veloxzone.com.br [201.29.120.119] (may be forged), reject=550 5.7.1… 54 …01-24-166-179.gnace703.dsl.brasiltelecom.net.br [201.24.166.179] (may be forged), reject=550 5.7.1… 55 …01-24-166-179.gnace703.dsl.brasiltelecom.net.br [201.24.166.179] (may be forged), reject=550 5.7.1… 56 …01-24-166-179.gnace703.dsl.brasiltelecom.net.br [201.24.166.179] (may be forged), reject=550 5.7.1… [all …]
|
/dports/security/ossec-hids-agent/ossec-hids-3.6.0/etc/rules/log-entries/ |
H A D | mail-alerts | 22 …r [200.207.91.189] (may be forged), reject=550 5.7.1 <andre.pereira@gerdau.com.br>... Relaying den… 23 …r [200.207.91.189] (may be forged), reject=550 5.7.1 <andre.nichele@gerdau.com.br>... Relaying den… 24 … [200.207.91.189] (may be forged), reject=550 5.7.1 <andre.celiberto@gerdau.com.br>... Relaying de… 39 …2=127.0.0.4, relay=120119.user.veloxzone.com.br [201.29.120.119] (may be forged), reject=550 5.7.1… 40 …2=127.0.0.4, relay=120119.user.veloxzone.com.br [201.29.120.119] (may be forged), reject=550 5.7.1… 41 …2=127.0.0.4, relay=120119.user.veloxzone.com.br [201.29.120.119] (may be forged), reject=550 5.7.1… 42 …2=127.0.0.4, relay=120119.user.veloxzone.com.br [201.29.120.119] (may be forged), reject=550 5.7.1… 54 …01-24-166-179.gnace703.dsl.brasiltelecom.net.br [201.24.166.179] (may be forged), reject=550 5.7.1… 55 …01-24-166-179.gnace703.dsl.brasiltelecom.net.br [201.24.166.179] (may be forged), reject=550 5.7.1… 56 …01-24-166-179.gnace703.dsl.brasiltelecom.net.br [201.24.166.179] (may be forged), reject=550 5.7.1… [all …]
|
/dports/security/ossec-hids-local/ossec-hids-3.6.0/etc/rules/log-entries/ |
H A D | mail-alerts | 22 …r [200.207.91.189] (may be forged), reject=550 5.7.1 <andre.pereira@gerdau.com.br>... Relaying den… 23 …r [200.207.91.189] (may be forged), reject=550 5.7.1 <andre.nichele@gerdau.com.br>... Relaying den… 24 … [200.207.91.189] (may be forged), reject=550 5.7.1 <andre.celiberto@gerdau.com.br>... Relaying de… 39 …2=127.0.0.4, relay=120119.user.veloxzone.com.br [201.29.120.119] (may be forged), reject=550 5.7.1… 40 …2=127.0.0.4, relay=120119.user.veloxzone.com.br [201.29.120.119] (may be forged), reject=550 5.7.1… 41 …2=127.0.0.4, relay=120119.user.veloxzone.com.br [201.29.120.119] (may be forged), reject=550 5.7.1… 42 …2=127.0.0.4, relay=120119.user.veloxzone.com.br [201.29.120.119] (may be forged), reject=550 5.7.1… 54 …01-24-166-179.gnace703.dsl.brasiltelecom.net.br [201.24.166.179] (may be forged), reject=550 5.7.1… 55 …01-24-166-179.gnace703.dsl.brasiltelecom.net.br [201.24.166.179] (may be forged), reject=550 5.7.1… 56 …01-24-166-179.gnace703.dsl.brasiltelecom.net.br [201.24.166.179] (may be forged), reject=550 5.7.1… [all …]
|
/dports/dns/dnscrypt-proxy2/dnscrypt-proxy-2.1.1/vendor/github.com/powerman/check/ |
H A D | stats.go | 36 forged counter member 44 forged: counter{force: force, name: "todo", color: ansiYellow}, 50 return fmt.Sprintf("checks: %s %s %s\t%s", c.passed, c.forged, c.failed, c.name) 78 total.forged.value += stats[t].forged.value 83 total.forged.size = digits(total.forged.value) 90 stats[t].forged.size = total.forged.size
|
/dports/security/py-fail2ban/fail2ban-0.11.2/config/filter.d/ |
H A D | sendmail-reject.conf | 28 …\S+ )?\[%(addr)s\](?: \(may be forged\))?, reject=(550 5\.7\.1 (?P=email)\.\.\. Relaying denied\. … 29 …dom>\S+), arg2=%(addr)s, relay=((?P=dom) )?\[(\d+\.){3}\d+\](?: \(may be forged\))?, reject=421 4\… 37 mdre-extra = ^(?:\S+ )?\[%(addr)s\](?: \(may be forged\))? did not issue \S+ during connection
|
H A D | sendmail-auth.conf | 17 failregex = ^(\S+ )?\[%(addr)s\]( \(may be forged\))?: possible SMTP attack: command=AUTH, count=\d… 18 …pass failed, user=<F-USER>(?:\S+|.*?)</F-USER>, relay=(?:\S+ )?\[%(addr)s\](?: \(may be forged\))?$
|
/dports/security/py-fail2ban/fail2ban-0.11.2/fail2ban/tests/files/logs/ |
H A D | sendmail-auth | 12 …1OHxxSn001499: 192.241.70.95.dsl.static.turk.net [95.70.241.192] (may be forged): possible SMTP at… 22 …ion failure: checkpass failed, user=user@example.com, relay=example.com [192.0.2.3] (may be forged) 24 …on failure: checkpass failed, user=criminal, relay=[192.0.2.100], relay=[192.0.2.4] (may be forged)
|
H A D | sendmail-reject | 7 ….net [80.253.155.119] (may be forged), reject=550 5.7.1 <dautareuk2@hotmail.it>... Relaying denied… 19 …amilopinto.pt>, relay=202.53.73.138.nettlinx.com [202.53.73.138] (may be forged), reject=553 5.1.8… 96 … "192.0.2.195", "desc": "wrong resp. non RFC compiant (ddos prelude?), MSP-mode, (may be forged)" } 97 …a[18624]: v27K4Vj8018624: some-host-24.example.org [192.0.2.195] (may be forged) did not issue MAI… 100 Mar 29 22:33:47 kismet sm-mta[23221]: x2TMXH7Y023221: internettl.org [104.152.52.29] (may be forged… 102 Mar 29 22:51:42 kismet sm-mta[24202]: x2TMpAlI024202: internettl.org [104.152.52.29] (may be forged…
|
/dports/mail/p5-Mail-Graph/Mail-Graph-0.14/t/ |
H A D | testmail.2 | 1 From sample@forged.com Tue Oct 27 18:38:52 1998 3 From: forged@example.com
|
H A D | testmail.1 | 1 From sample@forged.com Tue Oct 27 18:38:52 1998 3 From: forged@example.com
|
H A D | testmail.3 | 1 From sample@forged.com Tue Oct 27 18:38:52 1998 4 From: forged@example.com
|
H A D | testmail.4 | 4 From: forged@example.com 7 To: <forged@example.com>
|
/dports/news/cnews/cnews-cr.g_18/ctl/ |
H A D | controlperm.eg | 3 # but his name can be forged, so don't let him rmgroup... 15 # You can turn this on, at the risk of accepting forged rmgroups
|
/dports/security/py-pynacl/PyNaCl-1.4.0/docs/ |
H A D | signing.rst | 57 forged = signed[:-1] + bytes([int(signed[-1]) ^ 1]) 60 verify_key.verify(forged) 66 nacl.exceptions.BadSignatureError: Signature was forged or corrupt 113 forged = signed_hex[:-1] + bytes([int(signed_hex[-1]) ^ 1]) 116 verify_key.verify(forged) 122 nacl.exceptions.BadSignatureError: Signature was forged or corrupt 169 forged = signed_b64[:-1] + bytes([int(signed_b64[-1]) ^ 1]) 172 verify_key.verify(forged) 178 nacl.exceptions.BadSignatureError: Signature was forged or corrupt
|
/dports/mail/spamassassin-devel/spamassassin-1ea352210/rulesrc/sandbox/jhardin/ |
H A D | 20_tbird_image_spam.cf | 16 describe __FORGED_TBIRD_IMG Possibly forged Thunderbird image spam 27 describe FORGED_TBIRD_IMG_ARROW Likely forged Thunderbird image spam 103 describe FORGED_TBIRD_IMG_TO_MX Likely forged Thunderbird image spam 116 describe FORGED_TBIRD_IMG_SIZE Likely forged Thunderbird image spam
|
/dports/audio/carla/Carla-2.4.1/source/modules/lilv/patches/ |
H A D | sratom_fix-utf8-string-size.patch | 9 use 'strlen' to get the raw byte size of the strings to be forged, 10 if not, strings with multi-byte UTF-8 characters are truncatedly forged.
|
/dports/net/corosync2/corosync-2.4.5/ |
H A D | SECURITY | 5 1. forged group messaging messages which are intended to fault the corosync 7 2. forged group messaging messages which are intended to fault applications 39 attacker could forge messages. These forged messages could fault the corosync
|
/dports/net/nncp/nncp-8.0.2/doc/usecases/ |
H A D | f2f.texi | 4 All Internet connections can be eavesdropped and forged. You 21 and forged nodes. However they are harder to support and require more
|
/dports/mail/p5-Sisimai/Sisimai-v4.25.11/set-of-emails/maildir/bsd/ |
H A D | lhost-sendmail-13.eml | 25 from g5.example.jp [192.0.2.9] (may be forged) 52 Received: from g56.smtp.example.jp (g5.example.jp [192.0.2.9] (may be forged))
|
H A D | lhost-sendmail-58.eml | 20 from no.rdns.hostshield.net [178.159.7.4] (may be forged) 57 Received: from cpanel.com (no.rdns.hostshield.net [178.159.7.4] (may be forged))
|
H A D | lhost-sendmail-34.eml | 20 from 192.0.2.85.static.example.tr [192.0.2.85] (may be forged) 55 …ived: from 192.0.2.85.static.example.tr (192.0.2.85.static.example.tr [192.0.2.85] (may be forged))
|
/dports/dns/yadifa/yadifa-2.5.3-10333/sbin/yadifad/contributions/ |
H A D | 20190323-yadifa-2.3.9-pmtudisc_omit.patch | 12 By preventing forged PMTU information, setting IP_PMTUDISC_OMIT (instead of IP_PMTUDISC_DONT) to DN… 48 + * forged PMTU information.
|
/dports/security/sslsplit/sslsplit-0.5.5/ |
H A D | sslsplit.conf.in | 6 # Use CA cert (and key) to sign forged certs. 10 # Use CA key (and cert) to sign forged certs. 31 # Use URL as CRL distribution point for all forged certs. 180 # When disabled, never add the SNI to forged certificates, even if the SNI
|
/dports/lang/racket/racket-8.3/share/pkgs/optimization-coach/optimization-coach/ |
H A D | instrumentation.rkt | 158 (define forged-stx (inlining-event->forged-stx evt)) 166 forged-stx forged-stx 167 (syntax-position forged-stx) 233 (define (inlining-event->forged-stx evt)
|
/dports/mail/spamassassin-devel/spamassassin-1ea352210/t/data/nice/ |
H A D | 013 | 14 Test whitelist_from_rcvd bar@example.com when relay is forged
|