Redditbot is currently blocked by AppSec and not excluded from bot challenges
Los mantenedores suelen responder en 2 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 30/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Área
- security
Línea de trabajo
Start with the linked appsec-bot-challenge-exclude-social WAF configuration and compare how its existing social crawlers are verified. The issue does not identify a trustworthy Redditbot network attribute or settle whether a User-Agent-only definition is acceptable, so first establish a recommended verification method. Done means Redditbot can be allowed without relying on spoofable headers or broad cloud IP ranges.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What would you like to be added?
The Reddit link-preview crawler (redditbot) is currently being blocked/challenged by CrowdSec AppSec and the new bot detection feature.
It is not currently included in the appsec-bot-challenge-exclude-social WAF configuration.
I would like to add support for Redditbot as a legitimate social-media crawler, similar to the existing exclusions for services such as Twitter/X, LinkedIn, Discord, Pinterest, etc.
Observed User-Agent
The requests I am seeing use the following User-Agent:
Mozilla/5.0 (compatible; redditbot/1.0; +http://www.reddit.com/feedback)
The identifying part appears to be:
redditbot/1.0
Network verification
The challenge is that, unlike some of the other supported bots, I have not been able to identify a dedicated and trustworthy IP range for Redditbot that we could use for verification.
For example, we observed a request with the following headers:
User-Agent: Mozilla/5.0 (compatible; redditbot/1.0; +http://www.reddit.com/feedback)
X-Forwarded-Host: ...
X-Span: ...
X-Sampled: 1
X-Trace: ...
Traceparent: ...
X-Forwarded-Server: ...
X-Parent: 0
However, I don't consider these headers to be suitable authentication/verification mechanisms for a legitimate bot whitelist. I also don't want to whitelist broad cloud-provider IP ranges merely because Redditbot may originate from such infrastructure.
Question
What is the recommended way to add redditbot to the appsec-bot-challenge-exclude-social configuration?
In particular:
- Is there an official Redditbot IP range, ASN, reverse-DNS pattern, or other network attribute that CrowdSec recommends using to verify that requests genuinely originate from Reddit?
- If no trustworthy network verification is available, does CrowdSec support a User-Agent-only legitimate-bot definition for Redditbot? I assume not, as the user-agent can be spoofed by anyone and would bypass bot protection completely.
- Is there another recommended mechanism for allowing Reddit's URL/link-preview crawler without weakening AppSec bot protection?
I'd be happy to contribute a reddit.json definition if there is a recommended verification method.
Thanks!
Why is this needed?
Unlike other social media bots, Reddit is not included in the list of appsec-bot-challenge-exclude-social. Therefore, it is blocked and gets the bot verification challenge. Unable to fetch blog post seo content, images and sorts.
- Lenguaje dominante
- Go
- Estrellas
- 15.1k
- Forks
- 726
- Merge medio
- 2 d 51 min
- PR fusionados (30 d)
- 18
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de crowdsecurity/crowdsec
-
[docker] Align build and debian releasePosiblemente ocupada @albundy83 la tomó hace 2 días. Abiertokind/enhancement needs/triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
crowdsecurity/crowdsec#4803 · 3 comentarios ·
Los mantenedores suelen responder en 2 días
-
Bucket queues preallocate all their slots when the bucket is createdPosiblemente ocupada @AdzerKI la tomó hace 4 días. Abiertokind/bug needs/triage os/linux
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
crowdsecurity/crowdsec#4799 · 3 comentarios ·
Los mantenedores suelen responder en 2 días
-
kind/bug needs/triage os/linux
Dificultad 3/5 1-2 días Aptitud para principiantes 25/100
crowdsecurity/crowdsec#4797 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
needs/kind needs/triage
Dificultad 5/5 Más de una semana Aptitud para principiantes 38/100
crowdsecurity/crowdsec#4795 · 2 comentarios ·
Los mantenedores suelen responder en 2 días
-
kind/bug needs/triage os/linux
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
crowdsecurity/crowdsec#4790 · 1 comentario ·
Los mantenedores suelen responder en 2 días
Todos los issues de crowdsecurity/crowdsec
Issues similares
-
govulncheck reports 7 reachable vulnerabilities in dependenciesPosiblemente ocupada @dwisiswant0 la tomó hoy. AbiertoType: Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
projectdiscovery/rawhttp#558 ·
-
govulncheck reports 8 vulnerabilities in called codePosiblemente ocupada @dwisiswant0 la tomó hoy. AbiertoType: Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
projectdiscovery/vulnx#517 ·
-
routing: the tray panel's stage stands still with motion reduced while a request is in flightAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
-
Type: Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
rubys/roundhouse#1946 ·