Package Details: wxhexeditor 0.24-4

Git Clone URL: https://aur.archlinux.org/wxhexeditor.git (read-only, click to copy)
Package Base: wxhexeditor
Description: A free hex editor / disk editor for Linux, Windows and MacOSX
Upstream URL: http://www.wxhexeditor.org
Licenses: GPL2
Submitter: None
Maintainer: severach (mxfm)
Last Packager: severach
Votes: 87
Popularity: 0.000109
First Submitted: 2009-01-20 22:52 (UTC)
Last Updated: 2022-12-16 03:28 (UTC)

Dependencies (4)

Required by (0)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 11 Next › Last »

mxfm commented on 2021-04-15 11:40 (UTC)

Please write upstream.

nyanpasu64 commented on 2021-04-15 06:14 (UTC)

Running KDE. Whenever I try opening a file, I get error:

./src/common/evtloopcmn.cpp(110): assert "Assert failure" failed in Yield(): wxYield called recursively

dario commented on 2020-07-23 07:24 (UTC)

Works for me, too.

mxfm commented on 2020-07-23 07:21 (UTC) (edited on 2020-07-23 07:22 (UTC) by mxfm)

@abd It works for me:

==> Validating source files with md5sums...

v0.24.tar.gz ... Passed                                                                                                             
01-add-pkexec-support.patch ... Passed                 
02-remove-strange-output.patch ... Passed

abd commented on 2020-07-22 03:29 (UTC) (edited on 2020-07-22 03:30 (UTC) by abd)

Got stumbled on: 

v0.24.tar.gz ... Passed   
01-add-pkexec-support.patch ... Passed   
02-remove-strange-output.patch ... FAILED   
==> ERROR: One or more files did not pass the validity check!

How can we fix such this?

mxfm commented on 2019-08-10 14:15 (UTC)

@toyarchery, I was not aware of this.

Patch is added, gksu and polkit are added as optdepends. Tested on my laptop.

toyarchery commented on 2019-08-10 13:13 (UTC)

I agree, but that's how wxHexEditor was designed: temporarily getting read/write access by chown, and limiting root access to this command. It already does that with gksu, but it would be more future-proof to use pkexec instead

mxfm commented on 2019-08-10 12:54 (UTC)

@toyarchery, I don't understand you. What is your goal?

If you want to run editor as root, you can run 'sudo wxHexEdit'. It just works. What added value does gksu or pkexec policy provide?

If you want to execute wxHexEditor in a such way, that only changes are written with root access, then this is impossible. Either the whole app is run as root or not.

The idea behind polkit is that application should be written in a such way, that only piece that requires root access is executed via polkit. Since wxHexEditor is 'legacy app' in this regard, this aspect is irrelevant because the whole app must be run as root. You are not making code more secure by executing it with gksu/polkit instead of sudo.

Regarding the patch. Does it try to change permission of file by executing 'pkexec --user root chown' in order to write to it? This does not work in general case. For example, I want inspect my drive /dev/sda and changing its ownership is not a good idea.

toyarchery commented on 2019-08-10 11:52 (UTC)

Alright, I've sent a pull request to upstream to add support for pkexec. In the meantime we can either add gksu regardless or patch it with pkexec

mxfm commented on 2019-08-10 08:57 (UTC) (edited on 2019-08-10 08:58 (UTC) by mxfm)

@toyarchery, I could not make gksu-polkit-git because git.debian.org is down, AFAIK it is down for 1-2 years (the package was last updated in 2015).

Regarding running wxHexEditor as root. You can use folowing policy file (/usr/share/polkit-1/actions/org.freedesktop.wxHexEditor.policy):

<policyconfig> <action id="org.freedesktop.policykit.exec.wxHexEditor"> <message>Authentication is required to run wxHexEditor </message> <defaults> <allow_any>auth_admin</allow_any> <allow_inactive>auth_admin</allow_inactive> <allow_active>auth_admin</allow_active> </defaults> <annotate key="org.freedesktop.policykit.exec.path">/usr/bin/wxHexEditor</annotate> <annotate key="org.freedesktop.policykit.exec.allow_gui">true</annotate> </action> </policyconfig>

and execute 'pkexec wxHexEditor'.

However, this seems unnecessary because the whole wxHexEditor is running as root and there is no difference comparing to running with 'sudo'.

« First ‹ Previous 1 2 3 4 5 6 7 .. 11 Next › Last »