Altap Salamander Support Forums

strange, my antivirus (https://eset.com) does not report anything suspicious,

those who have github account, you can download build artifacts from my github job: https://github.com/lejcik/salamander/actions/runs/13088683936 (or newer)

binaries compiled on github should be clean, if you antivirus ...

ok, then try to download it from here: https://uschovna.cz/zasilka/RG2D5WT7IRNEC89S-XS5

Ok, you can download the libraries from here: https://drive.google.com/file/d/1GjZwKJ ... xCBt2/view

Did you manage to compile the plugin?

Firstly, you have to have vcpkg utility, when you integrate it with Visual Studio, it will build everyting for you. It's also good to define OPENSAL_BUILD_DIR environment variable.


c:\projects> git clone https://github.com/Microsoft/vcpkg.git
c:\projects> cd vcpkg
c:\projects\vcpkg> bootstrap ...

Go to the link above to the discussion and see my long comment there, but basically this sentence explains it:

- load libheif.dll and libwebp.dll dynamically (currently they have to be copied to the directory where salamand.exe is)

I plan to fix this issue, but for now if you copy the related ...

I "played" a bit with the PictView plugin, and I've added support for viewing .heif and .webp files. This is an experimental feature, it's more a hack than a regular implementation, but it works with some limitations. For more details, see the pull request and discussion:

https://github.com ...

How it is going with open-sourcing the AS? Is there any progress?

I'd repeat my suggestion - if it's too much effort to publish all the source codes at once, please consider publishing the sources by components, for example plugin by plugin.

Also, if there's any work I can help you with, just ping ...

This is very good news! If it's too much effort to publish all the source codes at once, please consider publishing the sources by components, for example plugin by plugin. Just let the community doesn't have to wait for ages.

Fingers crossed. Thanks.

And regarding the second example, it seems that the certificate file was not parsed. I think it's because of the uncommented lines just above the --BEGIN CERTIFICATE-- line, try out to comment them out to view the content, or try to run:

openssl x509 -in e:\cacert.pem -text

Then it should work ...

Hi AD7,

This is not that easy task. In fact, I have only a few strings in the certdump.cpp file: (see the BIO_printf() calls)
https://github.com/lejcik/certviewer/blob/master/certdump.cpp

In your example, the header (object type and format strings) can be translated easily, but the rest of the ...

Hi all, I have an update of this plugin. It didn't work as I wanted (tested with certificates that I got from my company), so that I improved it to ease my job :)

I improved certificate formats auto-detection, added support for a few more certificate formats, and updated the sources for openssl ...

Zdravim, to by bolo super ak vydate Salamander ako open-source, ja s nim pracujem takmer kazdy den, a mat moznost ho vylepsovat by ma velmi potesila. Uz som pre Salamander nieco kodil (SDK4, upravy TAR pluginu), C++ zvladam, rad sa pridam k projektu :)

Ako full-time zamestnanec mi uz vela volneho ...

I fixed a few issues with the TAR plugin, I updated the attached archives in the initial post, so you can download it there.

As I can't change the plugin version (otherwise the lang modules will not work), make sure you have the binary from 7.1.2022.

Enjoy

Thanks for testing and reporting issues. I'll try to fix them and will post here the updated plugin...

Hi all, I'm sharing a small update of the TAR plugin. I've added support for .xz and .zst archive types. Thanks to Altap staff for help.

See the attachment, download the plugin for your Salamander version, and copy the plugin binary into plugins\tar directory where your Slamander is installed, for ...