dreieck-
thanks for the heads up; fixed and pushed!
Git Clone URL: | https://aur.archlinux.org/wpscrack.git (read-only, click to copy) |
---|---|
Package Base: | wpscrack |
Description: | PoC tool to brute force WPS - external registrar PIN of wlan access points |
Upstream URL: | https://github.com/ml31415/wpscrack |
Licenses: | |
Submitter: | sanerb |
Maintainer: | sanerb |
Last Packager: | sanerb |
Votes: | 1 |
Popularity: | 0.000000 |
First Submitted: | 2015-08-25 00:01 |
Last Updated: | 2018-09-01 16:32 |
dreieck-
thanks for the heads up; fixed and pushed!
Dependency pycrypto
can not anymore be fulfilled by any package.
And official Arch Linux package python2-crypto
has been replaced by python2-pycryptodome
, which not anymore has an entry to provide pycrypto
(but python2-crypto
).
However, replacing the dependency on pycrypto
by a dependency on python2-crypto
also works for wpscrack
.
Also, you should change the dependency on scapy
to python2-scapy
. With scapy
installed and not python2-scapy
, I get the error
Traceback (most recent call last):
File "/sbin/wpscrack", line 11, in <module>
from scapy.all import *
ImportError: No module named scapy.all
With python2-scapy
it works; if scapy
by its own is necessary I could not test.
package()
tries to install README
, but
==> Starting package()...
install: cannot stat 'README': No such file or directory
==> ERROR: A failure occurred in package().
However, there is a README.md
.
the PKGBUILD has four entries in the source
-array but only three entries in the sha512sums
-array, leading to
==> ERROR: Integrity checks (sha512) differ in size from the source array.
@dreieck-
updated and pushed. thanks!
ah, yep. dropbox killed public folders or... something like that a bit back.
i'll self-host and update with https://github.com/ml31415/wpscrack as well, give me a bit
Download URL not working:
-> Downloading wpscrack.zip...
--2017-04-10 13:29:51-- http://dl.dropbox.com/u/22108808/wpscrack.zip
Resolving dl.dropbox.com... 162.125.66.6
Connecting to dl.dropbox.com|162.125.66.6|:80... connected.
HTTP request sent, awaiting response... 302 FOUND
Location: http://dl.dropboxusercontent.com/u/22108808/wpscrack.zip [following]
--2017-04-10 13:29:51-- http://dl.dropboxusercontent.com/u/22108808/wpscrack.zip
Resolving dl.dropboxusercontent.com... 162.125.66.6
Reusing existing connection to dl.dropbox.com:80.
HTTP request sent, awaiting response... 302 FOUND
Location: https://dl.dropboxusercontent.com/u/22108808/wpscrack.zip [following]
--2017-04-10 13:29:51-- https://dl.dropboxusercontent.com/u/22108808/wpscrack.zip
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Connecting to dl.dropboxusercontent.com|162.125.66.6|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-04-10 13:29:52 ERROR 404: Not Found.
==> ERROR: Failure while downloading http://dl.dropbox.com/u/22108808/wpscrack.zip
Aborting...
Please note the following additions:
# Bug reports can be filed at https://bugs.square-r00t.net/index.php?project=3
# News updates for packages can be followed at https://devblog.square-r00t.net
(If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to https://devblog.square-r00t.net/rss/?category=aur in your favourite RSS reader.)
Note that you should still use the AUR web interface for flagging packages as out-of-date if a new version is released; the aforementioned bug tracker is to aid in issues with building/packaging/the PKGBUILD formats/etc. specifically.
GPG signature "errors" are explained here:
https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds
Please read; it's not a bug.
Thanks!
Pinned Comments
sanerb commented on 2016-06-26 06:22
Please note the following additions:
# Bug reports can be filed at https://bugs.square-r00t.net/index.php?project=3
# News updates for packages can be followed at https://devblog.square-r00t.net
(If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to https://devblog.square-r00t.net/rss/?category=aur in your favourite RSS reader.)
Note that you should still use the AUR web interface for flagging packages as out-of-date if a new version is released; the aforementioned bug tracker is to aid in issues with building/packaging/the PKGBUILD formats/etc. specifically.
GPG signature "errors" are explained here:
https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds
Please read; it's not a bug.
Thanks!