Bug#1053134: ITP: python-cloudscraper -- Python module to bypass Cloudflare's anti-bot page
Package: wnpp Severity: wishlist Owner: Carles Pina i Estany X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: python-cloudscraper Version : 1.2.68 Upstream Contact: VeNoMouS * URL : https://github.com/VeNoMouS/cloudscraper * License : MIT Programming Lang: Python Description : Python module to bypass Cloudflare's anti-bot page --- A simple Python module to bypass Cloudflare's anti-bot page (also known as "I'm Under Attack Mode", or IUAM), implemented with Requests. Cloudflare changes their techniques periodically, so I will update this repo frequently. This can be useful if you wish to scrape or crawl a website protected with Cloudflare. Cloudflare's anti-bot page currently just checks if the client supports Javascript, though they may add additional techniques in the future. Due to Cloudflare continually changing and hardening their protection page, cloudscraper requires a JavaScript Engine/interpreter to solve Javascript challenges. This allows the script to easily impersonate a regular web browser without explicitly deobfuscating and parsing Cloudflare's Javascript. --- I ITP simplemonitor (#1016113). One of simplemonitor dependencies is pyaarlo (#1053132). python-cloudscraper is a dependency of pyaarlo. Incidentally, I've used cloudscraper (from upstream) previously so I'm familiar with it. I plan to package it inside the Debian Python Team. I will need a sponsor.
Bug#1053132: ITP: python-pyaarlo -- Module for Python that provides asynchronous access to Netgear Arlo cameras
Package: wnpp Severity: wishlist Owner: Carles Pina i Estany X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: python-pyaarlo Version : 0.8.0.beta.8 Upstream Contact: Ntwrecked * URL : https://github.com/twrecked/pyaarlo * License : LGPL-3.0 Programming Lang: Python Description : Module for Python that provides asynchronous access to Netgear Arlo cameras - It starts a background thread that opens a single, persistant connection, an event stream, to the Arlo servers. As things happen to the Arlo devices - motion detected, battery level changes, mode changes, etc... - the Arlo servers post these events onto the event stream. The background thread reads these events from the stream, updates Pyaarlo's internal state and calls any user registered callbacks. - I submitted an ITP bug for simplemonitor (#1016113). pyarlo is a dependency of simplemonitor. I plan to maintain it inside the Debian Python Team. I will need a sponsor.
Re: RFC/MBF: Dropping support for ifupdown hook scripts from network-manager package
Am 27.09.23 um 22:30 schrieb Vincent Blut: From the above list, I plan to exclude the following packages: chrony ntpsec-ntpdate => already provide native NM-dispatcher scripts ... So, the remaining list of packages which I plan to do a MBF for is: aoetools auto6to4 avahi-autoipd bind9 chrony As you rightfully stated higher up, chrony already includes native NM-dispatcher scripts so you can remove it from the list of affected packages. Oops, indeed. Thanks for spotting that obvious mistake. Updated the list. Regards, Michael P.S.: Thanks for maintaining chrony. I like the software as well as how it's maintained in Debian! OpenPGP_signature.asc Description: OpenPGP digital signature
Re: RFC/MBF: Dropping support for ifupdown hook scripts from network-manager package
Le 2023-09-27 21:45, Michael Biebl a écrit :
> Hi everyone,
>
> NetworkManager provides a service named NetworkManager-dispatcher [1], which
> executes scripts in /{etc,usr/lib}/NetworkManager/dispatcher.d upon
> (network) state changes.
>
> This is in spirit similar to ifupdown's /etc/network/if-*.d/ scripts.
> The concepts do not match completely though. For ifupdown, the hook
> interface is also use to extend the functionality of ifupdown itself.
>
> That said, the Debian network-manager package has shipped a
> /etc/NetworkManager/dispatcher.d/01-ifupdown script for several releases,
> which fakes an ifupdown environment and tried to execute those ifupdown hook
> scripts. This emulation of an ifupdown environment was never complete and
> also led to undesired effects, like hook scripts being executed that are not
> really suitable if NetworkManager is managing the interface.
>
> I thus plan to drop /etc/NetworkManager/dispatcher.d/01-ifupdown.
>
>
> Currently, the following packages ship hook scripts for ifupdown
>
> $ apt-file search /etc/network/if- | grep -v ^ifupdown
> aoetools: /etc/network/if-up.d/aoe-discover
> auto6to4: /etc/network/if-up.d/auto6to4
> avahi-autoipd: /etc/network/if-down.d/avahi-autoipd
> avahi-autoipd: /etc/network/if-up.d/avahi-autoipd
> bind9: /etc/network/if-down.d/bind9
> bind9: /etc/network/if-up.d/bind9
> bridge-utils: /etc/network/if-down.d/bridge
> bridge-utils: /etc/network/if-post-down.d/bridge
> bridge-utils: /etc/network/if-pre-up.d/bridge
> chrony: /etc/network/if-post-down.d/chrony
> chrony: /etc/network/if-up.d/chrony
> clamav-freshclam: /etc/network/if-down.d/clamav-freshclam-ifupdown
> clamav-freshclam: /etc/network/if-up.d/clamav-freshclam-ifupdown
> ethtool: /etc/network/if-pre-up.d/ethtool
> ethtool: /etc/network/if-up.d/ethtool
> guidedog: /etc/network/if-down.d/51guidedog
> guidedog: /etc/network/if-up.d/51guidedog
> hostapd: /etc/network/if-post-down.d/hostapd
> hostapd: /etc/network/if-pre-up.d/hostapd
> htpdate: /etc/network/if-up.d/htpdate
> ifenslave: /etc/network/if-post-down.d/ifenslave
> ifenslave: /etc/network/if-pre-up.d/ifenslave
> ifenslave: /etc/network/if-up.d/ifenslave
> ifmetric: /etc/network/if-up.d/ifmetric
> initscripts: /etc/network/if-up.d/mountnfs
> isatapd: /etc/network/if-down.d/isatapd
> isatapd: /etc/network/if-up.d/isatapd
> linux-wlan-ng: /etc/network/if-post-down.d/linux-wlan-ng-post-down
> linux-wlan-ng: /etc/network/if-pre-up.d/linux-wlan-ng-pre-up
> lprng: /etc/network/if-up.d/lprng
> macchanger: /etc/network/if-post-down.d/macchanger
> macchanger: /etc/network/if-pre-up.d/macchanger
> miredo: /etc/network/if-up.d/miredo
> nslcd: /etc/network/if-up.d/nslcd
> ntpsec-ntpdate: /etc/network/if-up.d/ntpsec-ntpdate
> openntpd: /etc/network/if-up.d/openntpd
> openresolv: /etc/network/if-down.d/resolvconf
> openresolv: /etc/network/if-up.d/000resolvconf
> openvpn: /etc/network/if-down.d/openvpn
> openvpn: /etc/network/if-up.d/openvpn
> openvswitch-switch: /etc/network/if-post-down.d/openvswitch
> openvswitch-switch: /etc/network/if-pre-up.d/openvswitch
> postfix: /etc/network/if-down.d/postfix
> postfix: /etc/network/if-up.d/postfix
> quicktun: /etc/network/if-down.d/quicktun
> quicktun: /etc/network/if-post-down.d/quicktun
> quicktun: /etc/network/if-pre-up.d/quicktun
> quicktun: /etc/network/if-up.d/quicktun
> resolvconf: /etc/network/if-down.d/resolvconf
> resolvconf: /etc/network/if-up.d/000resolvconf
> sendmail-base: /etc/network/if-down.d/sendmail
> sendmail-base: /etc/network/if-post-down.d/sendmail
> sendmail-base: /etc/network/if-up.d/sendmail
> shorewall-init: /etc/network/if-post-down.d/shorewall
> shorewall-init: /etc/network/if-up.d/shorewall
> sidedoor: /etc/network/if-up.d/sidedoor
> slrn: /etc/network/if-up.d/slrn
> slrnpull: /etc/network/if-up.d/slrnpull
> tinc: /etc/network/if-post-down.d/tinc
> tinc: /etc/network/if-pre-up.d/tinc
> tinc: /etc/network/if-up.d/tinc
> ucarp: /etc/network/if-up.d/ucarp
> uml-utilities: /etc/network/if-pre-up.d/uml-utilities
> uml-utilities: /etc/network/if-up.d/uml-utilities
> vde2: /etc/network/if-post-down.d/vde2
> vde2: /etc/network/if-pre-up.d/vde2
> vlan: /etc/network/if-post-down.d/vlan
> vlan: /etc/network/if-pre-up.d/vlan
> vlan: /etc/network/if-up.d/ip
> whereami: /etc/network/if-pre-up.d/whereami
> wide-dhcpv6-client: /etc/network/if-post-down.d/wide-dhcpv6-client
> wide-dhcpv6-client: /etc/network/if-up.d/wide-dhcpv6-client
> wireless-tools: /etc/network/if-post-down.d/wireless-tools
> wireless-tools: /etc/network/if-pre-up.d/wireless-tools
> wpasupplicant: /etc/network/if-down.d/wpasupplicant
> wpasupplicant: /etc/network/if-post-down.d/wpasupplicant
> wpasupplicant: /etc/network/if-pre-up.d/wpasupplicant
> wpasupplicant: /etc/network/if-up.d/wpasupplicant
>
>
> I plan to do a MBF, asking those packages to ship a native
> NetworkManager-dispatcher hook script in
> /usr/lib/NetworkManager/dispatcher.d
>
> From the above list, I plan to exclude the following package
RFC/MBF: Dropping support for ifupdown hook scripts from network-manager package
Hi everyone,
NetworkManager provides a service named NetworkManager-dispatcher [1],
which executes scripts in /{etc,usr/lib}/NetworkManager/dispatcher.d
upon (network) state changes.
This is in spirit similar to ifupdown's /etc/network/if-*.d/ scripts.
The concepts do not match completely though. For ifupdown, the hook
interface is also use to extend the functionality of ifupdown itself.
That said, the Debian network-manager package has shipped a
/etc/NetworkManager/dispatcher.d/01-ifupdown script for several
releases, which fakes an ifupdown environment and tried to execute those
ifupdown hook scripts. This emulation of an ifupdown environment was
never complete and also led to undesired effects, like hook scripts
being executed that are not really suitable if NetworkManager is
managing the interface.
I thus plan to drop /etc/NetworkManager/dispatcher.d/01-ifupdown.
Currently, the following packages ship hook scripts for ifupdown
$ apt-file search /etc/network/if- | grep -v ^ifupdown
aoetools: /etc/network/if-up.d/aoe-discover
auto6to4: /etc/network/if-up.d/auto6to4
avahi-autoipd: /etc/network/if-down.d/avahi-autoipd
avahi-autoipd: /etc/network/if-up.d/avahi-autoipd
bind9: /etc/network/if-down.d/bind9
bind9: /etc/network/if-up.d/bind9
bridge-utils: /etc/network/if-down.d/bridge
bridge-utils: /etc/network/if-post-down.d/bridge
bridge-utils: /etc/network/if-pre-up.d/bridge
chrony: /etc/network/if-post-down.d/chrony
chrony: /etc/network/if-up.d/chrony
clamav-freshclam: /etc/network/if-down.d/clamav-freshclam-ifupdown
clamav-freshclam: /etc/network/if-up.d/clamav-freshclam-ifupdown
ethtool: /etc/network/if-pre-up.d/ethtool
ethtool: /etc/network/if-up.d/ethtool
guidedog: /etc/network/if-down.d/51guidedog
guidedog: /etc/network/if-up.d/51guidedog
hostapd: /etc/network/if-post-down.d/hostapd
hostapd: /etc/network/if-pre-up.d/hostapd
htpdate: /etc/network/if-up.d/htpdate
ifenslave: /etc/network/if-post-down.d/ifenslave
ifenslave: /etc/network/if-pre-up.d/ifenslave
ifenslave: /etc/network/if-up.d/ifenslave
ifmetric: /etc/network/if-up.d/ifmetric
initscripts: /etc/network/if-up.d/mountnfs
isatapd: /etc/network/if-down.d/isatapd
isatapd: /etc/network/if-up.d/isatapd
linux-wlan-ng: /etc/network/if-post-down.d/linux-wlan-ng-post-down
linux-wlan-ng: /etc/network/if-pre-up.d/linux-wlan-ng-pre-up
lprng: /etc/network/if-up.d/lprng
macchanger: /etc/network/if-post-down.d/macchanger
macchanger: /etc/network/if-pre-up.d/macchanger
miredo: /etc/network/if-up.d/miredo
nslcd: /etc/network/if-up.d/nslcd
ntpsec-ntpdate: /etc/network/if-up.d/ntpsec-ntpdate
openntpd: /etc/network/if-up.d/openntpd
openresolv: /etc/network/if-down.d/resolvconf
openresolv: /etc/network/if-up.d/000resolvconf
openvpn: /etc/network/if-down.d/openvpn
openvpn: /etc/network/if-up.d/openvpn
openvswitch-switch: /etc/network/if-post-down.d/openvswitch
openvswitch-switch: /etc/network/if-pre-up.d/openvswitch
postfix: /etc/network/if-down.d/postfix
postfix: /etc/network/if-up.d/postfix
quicktun: /etc/network/if-down.d/quicktun
quicktun: /etc/network/if-post-down.d/quicktun
quicktun: /etc/network/if-pre-up.d/quicktun
quicktun: /etc/network/if-up.d/quicktun
resolvconf: /etc/network/if-down.d/resolvconf
resolvconf: /etc/network/if-up.d/000resolvconf
sendmail-base: /etc/network/if-down.d/sendmail
sendmail-base: /etc/network/if-post-down.d/sendmail
sendmail-base: /etc/network/if-up.d/sendmail
shorewall-init: /etc/network/if-post-down.d/shorewall
shorewall-init: /etc/network/if-up.d/shorewall
sidedoor: /etc/network/if-up.d/sidedoor
slrn: /etc/network/if-up.d/slrn
slrnpull: /etc/network/if-up.d/slrnpull
tinc: /etc/network/if-post-down.d/tinc
tinc: /etc/network/if-pre-up.d/tinc
tinc: /etc/network/if-up.d/tinc
ucarp: /etc/network/if-up.d/ucarp
uml-utilities: /etc/network/if-pre-up.d/uml-utilities
uml-utilities: /etc/network/if-up.d/uml-utilities
vde2: /etc/network/if-post-down.d/vde2
vde2: /etc/network/if-pre-up.d/vde2
vlan: /etc/network/if-post-down.d/vlan
vlan: /etc/network/if-pre-up.d/vlan
vlan: /etc/network/if-up.d/ip
whereami: /etc/network/if-pre-up.d/whereami
wide-dhcpv6-client: /etc/network/if-post-down.d/wide-dhcpv6-client
wide-dhcpv6-client: /etc/network/if-up.d/wide-dhcpv6-client
wireless-tools: /etc/network/if-post-down.d/wireless-tools
wireless-tools: /etc/network/if-pre-up.d/wireless-tools
wpasupplicant: /etc/network/if-down.d/wpasupplicant
wpasupplicant: /etc/network/if-post-down.d/wpasupplicant
wpasupplicant: /etc/network/if-pre-up.d/wpasupplicant
wpasupplicant: /etc/network/if-up.d/wpasupplicant
I plan to do a MBF, asking those packages to ship a native
NetworkManager-dispatcher hook script in
/usr/lib/NetworkManager/dispatcher.d
From the above list, I plan to exclude the following packages:
chrony
ntpsec-ntpdate
=> already provide native NM-dispatcher scripts
bridge-utils
ethtool
ifenslave
ifmetric
initscripts
macchanger
openvswitch-switch
vde2
vlan
wireless-tools
wpasupplicant
=> afaics, those are packages, that extend the fu
Bug#1053104: ITP: vgrep -- a user-friendly pager for grep
Package: wnpp Severity: wishlist Owner: Xi Lu * Package name: vgrep Version : 2.6.1-1 Upstream Author : Valentin Rothberg * URL : https://github.com/vrothberg/vgrep * License : GPL-3.0 Programming Lang: Go Description : a user-friendly pager for grep vgrep is a pager for grep, git-grep, ripgrep and similar grep implementations, and allows for opening the indexed file locations in a user-specified editor such as vim or emacs. vgrep is inspired by the ancient **cgvg** scripts but extended to perform further operations such as listing statistics of files and directory trees or showing the context lines before and after the matches. vgrep runs on Linux, Windows and Mac OS.
Re: lintian.debian.org off ?
Otto Kekäläinen wrote on 27/09/2023 at 06:35:07+0200: > Hi! > > Thanks for the context - so there is no need technical incompatibility > at play, but mostly a matter of having resources and time to do it. > .. >> Regarding the 301 redirection I'll see with the interested parties (DSA >> and Lintian maintainers) if this option is fine with everyone. > > I could easily write Ansible code to maintain a simple Nginx server, > with 302 redirects https://lintian.debian.org/tags/(.*)/?$ -> > https://udd.debian.org/lintian-tag.cgi?tag=$1, use same Ansible style > as salsa.debian.org is maintained on > (https://salsa.debian.org/salsa/salsa-ansible), and also donate a tiny > virtual machine for Debian project if needed. Is there some special > bureaucracy on top of that work to do to be able to contribute with > this? Don't worry, the server still exists, it's just down, and reputting the DNS takes little to no time. Regarding apache config, I'm fine with doing it. It's a matter of checking with everyone that we want to do that as the plan was nuking the server from orbit. Providing debian.org infrastructure requires to be a member of the Debian System Administrators (DSA) team, which in turn requires to be a Debian Developer, so, sadly, you can't really help on that part. That being said, thank you for offering your time. > I know Lintian tag info is available via command line, but I > frequently need to educate upstreams about Lintian rules, and thus > really also need a URL to share to them. Perhaps I could implement > that later in the year. -- PEB signature.asc Description: PGP signature
