Activity for dartraiden
-
dartraiden modified a comment on ticket #2311
In addition to the code, a valid digital signature is required. Code signing certificate costs money.
-
In addition to the code, a valid digital signature is required
-
Duplicate of https://sourceforge.net/p/sevenzip/bugs/2311/
-
Old shell integration is still supported. With old menu. New menu required new integration because now only one top level item is allowed. If the developer needs more - he should make a submenu. If you allow the old software to integrate into the new menu, problems will inevitably arise: for example, 7zip will be unusable when the "Cascaded context menu" option is disabled. Thus, only applications whose developers have explicitly confirmed (by using the new API) that they are ready for the new rules...
-
Old shell integration is still supported. With old menu. New menu required new integration because now only one top level item is allowed. If the developer needs more - he should make a submenu. If you allow the old software to integrate into the new menu, problems will inevitably arise: for example, 7zip will be unusable when the "Cascaded context menu" option is disabled. Thus, only applications whose developers have explicitly confirmed (by using the new API) that they are ready for the new rules...
-
Old shell integration is still supported. With old menu. New menu required new integration because now only one top level item is allowed. If the developer needs more - he should make a submenu. If you allow the old software to integrate into the new menu, problems will inevitably arise: for example, 7zip will be unusable when the "Cascaded context menu" option is disabled
-
Old shell integration is still supported. With old menu. New menu required new integration because now only one top level item is allowed. If the developer needs more - he should make a submenu.
-
Old shell integration is still supported. With old menu. New menu required new integration because now only one top level item is allowed
-
Solution to the problem: by default, when installing KeePass, installer should drop an enforced config into its directory that prohibits export without master key if the user needs export without master key, the user deletes this config Thus, if the user has secured the installation directory (installed in Program Files or somehow manually assigned rights so that additional privileges are needed to write there), then the user is safe by default. If not, nothing will save him, even removing this feature...
-
Solution to the problem: by default, when installing KeePass, installer should drop an enforced config into its directory that prohibits export without master key if the user needs export without master key, the user deletes this config Thus, if the user has secured the installation directory (installed in Program Files or somehow manually assigned rights so that additional privileges are needed to write there), then the user is safe by default. If not, nothing will save him, even removing this feature...
-
Solution to the problem: by default, when installing KeePass, drop an enforced config into its directory that prohibits export without master key if the user needs export without master key, the user deletes this config Thus, if the user has secured the installation directory (installed in Program Files or somehow manually assigned rights so that additional privileges are needed to write there), then the user is safe by default. If not, nothing will save him, even removing this feature or switching...
-
Solution to the problem: by default, when installing KeePass, drop an https://sourceforge.net/p/keepass/discussion/329220/thread/a146e5cf6b/?page=2#73e4 into its directory that prohibits export without master key if the user needs export without master key, the user deletes this config Thus, if the user has secured the installation directory (installed in Program Files or somehow manually assigned rights so that additional privileges are needed to write there), then the user is safe by default. If...
-
Solution to the problem: by default, when installing KeePass, drop an https://sourceforge.net/p/keepass/discussion/329220/thread/a146e5cf6b/?page=2#73e4 into its directory that prohibits export without master key if the user needs export without master key, the user deletes this config Thus, if the user has secured the installation directory (installed in Program Files or somehow manually assigned rights so that additional privileges are needed to write there), then the user is safe by default.
-
Solution to the problem: by default, when installing KeePass, drop a config into its directory that prohibits export without master key if the user needs export without master key, the user deletes this config
-
Solution to the problem: * by default, when installing KeePass, drop a config into its directory that prohibits export without master key * if the user needs export without master key, the user deletes this config
-
If an attacker can change the executable file, nothing will save you. Even KeePass XC will not save you. An attacker can change the source code of KeePass XC by adding a silent export of passwords and then replace executable. Even if these code will be removed from KeePass attacker can add it back, compile his own KeePass.exe and replace executable.
-
If an attacker can change the executable file, nothing will save you. Even KeePass XC will not save you. An attacker can change the source code of KeePass XC by adding a silent export of passwords and then replace executable.
-
Duplicate of #1531.
-
Duplicate of #1531.
-
Unfortunately not. Tested on https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.1.tar.gz 21.01: 20 774 Files, 1 403 Folders 19.00 (with patch): 21 436 Files, 1 406 Folders
-
Unfortunately not. Tested on https://releases.wikimedia.org/mediawiki/1.35/mediawiki-1.35.1.tar.gz 21.01: 20 774 Files, 1 403 Folders 19.00 (with pathc): 21 436 Files, 1 406 Folders
-
Fix CPP\7zip\Archive\Tar\TarIn.cpp replace if (item.Name.IsPrefixedBy("PaxHeader/") || item.Name.Find("PaxHeaders.4467/") >= 0) by ~~~ if (item.Name.IsPrefixedBy("PaxHeader/") || item.Name.IsPrefixedBy("PaxHeaders.X/") || item.Name.IsPrefixedBy("./PaxHeaders.X/") || item.Name.Find("PaxHeaders.4467/") >= 0) ~~~~~~
-
Seems like only auth scheme is changes, OSCAR protocol still alive. You can see how it works in Pidgin, there is also an old protocol with a new authorization scheme. But ICQ can kill OSCAR at any moment in favor to new WIM protocol (this protocol is used by official clients: ICQ 10, ICQ Web and ICQ Mobile).
-
Seems like only auth scheme is changes, OSCAR protocol still alive. You can see how it works in Pidgin, there is also an old protocol with a new authorization scheme.
-
Looks like you're right. I was misled by the fact that Audacious, Winamp and foobar2000 plays this file correctly. But AuidoOverload player also tell "Unable to open file"
-
Looks like you're right. I was misled by the fact that Audacious, Wimamp and foobar2000 plays this file correctly. But AuidoOverload player also tell "Unable to open file"
-
Cannot open NSFE file
-
Possible copypaste bug
-
Add 6xBRZ
1