Package Details: winbox 4.0beta14-1

Git Clone URL: https://aur.archlinux.org/winbox.git (read-only, click to copy)
Package Base: winbox
Description: Mikrotik RouterOS GUI Configurator
Upstream URL: https://mikrotik.com/download
Licenses: custom
Submitter: TomHetmer
Maintainer: dundee (eworm)
Last Packager: eworm
Votes: 63
Popularity: 2.00
First Submitted: 2013-05-11 20:19 (UTC)
Last Updated: 2024-12-10 09:03 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

Omar007 commented on 2023-10-19 14:09 (UTC)

Well yes, but that's basically saying --yes-i-will-take-this-corrupted-or-virus-invested-file. A checksum mismatch is not something to blindly ignore. And in this case it's not like we can look at the source changes or something.

In general it's weird for there to be different checksums for different people for the same file. That means something is wrong. Whether that is of a malicious cause or not is a different question.

I've grabbed the file again today and it's still the other checksum instead of the one in the PKGBUILD (and also still very slow...).
It would be nice if someone that had the checksum in the PKGBUILD download the binary again and check if it switched to the other checksum or not. If yes, maybe MikroTik replaced it after the initial upload. If not, there might be a regional server/cdn issue or something.

loxothrone commented on 2023-10-18 18:55 (UTC)

you can always skip hash cheking by using makepkg --skipinteg -si PKGBUILD

Omar007 commented on 2023-10-14 22:06 (UTC)

As for @abruegmann, @Saduff (initially), @ypoluektovich, @kroloskar and @sshine, I'm also getting 91f7b0456619dbfc19940a85566c949ce3718321f32709886df5125c71f0b6b7 instead of 09e9683e008d09c981e4a5294c78f93e03dede1af19aee8ba794f5ca4aedef04. I've tried trice, all with the same result.
That said, the speed was incredibly slow and I had to retry one of them at least 3-4 times so not sure what's going on here. I'll try again later to see if anything changed.

marcos.sanm commented on 2023-10-13 16:12 (UTC)

@kroloskar you need to edit the PKGBUILD, you can do it easy from "app store" and change the version to 3.40 and the first of four checksums with this:

09e9683e008d09c981e4a5294c78f93e03dede1af19aee8ba794f5ca4aedef04

kroloskar commented on 2023-10-13 05:25 (UTC) (edited on 2023-10-13 05:28 (UTC) by kroloskar)

Building winbox... ==> Making package: winbox 3.40-1 (Fri, 13 Oct 2023, 07:23:39) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found winbox-3.40.exe -> Found winbox.desktop -> Found winbox.png -> Found winbox ==> Validating source files with sha256sums... winbox-3.40.exe ... FAILED winbox.desktop ... Passed winbox.png ... Passed winbox ... Passed ==> ERROR: One or more files did not pass the validity check! ... can someone explain how to deal with it? When you go to the website, the file you downoload is winbox64 not winbox-3.40... could this be the problem?

marcos.sanm commented on 2023-10-12 14:00 (UTC)

For lastest version:

pkver=3.40

first checksum 09e9683e008d09c981e4a5294c78f93e03dede1af19aee8ba794f5ca4aedef04

sshine commented on 2023-10-12 10:34 (UTC) 

$ sha256sum winbox-3.40.exe
91f7b0456619dbfc19940a85566c949ce3718321f32709886df5125c71f0b6b7  winbox-3.40.exe

kroloskar commented on 2023-10-12 04:47 (UTC)

downloaded now and: sha256sum winbox64.exe
91f7b0456619dbfc19940a85566c949ce3718321f32709886df5125c71f0b6b7 winbox64.exe so problem NOT solved

Saduff commented on 2023-10-11 23:43 (UTC)

It was some issue on the mikrotik website. Downloaded fresh copy yesterday and got 91f7b0, redownloaded today and got the same checksum as in the PKGBUILD (09e968), so problem solved.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »