Volodymyr Sydorenko avatar

Volodymyr Sydorenko

Community

@VSydorenko · Kyiv

9Followers
|
34Public Repos
|
4Published Skills

Ukrainian digital-signature and fiscal-compliance engineering: PRRO receipt signing, UAPKI crypto integration, and 1C native component development.

Skills Distribution
DomainCybersecurit...Digital Signature .. (40%)Fiscal Compliance .. (25%)1C Enterprise Comp.. (20%)Cryptographic Test.. (15%)

Agent Skills by Volodymyr Sydorenko

Showing 4 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Volodymyr Sydorenko

FAQPage Schema
What tasks can I accomplish with VSydorenko's skills?

You can sign PRRO fiscal documents (receipts, Z-reports) for the Ukrainian tax server, integrate the UAPKI crypto library for DSTU 4145 digital signatures, test the signing stack offline without a 1C host, and build/package 1C native external components on Windows.

Who are these skills designed for?

Developers and integrators working on Ukrainian fiscalization and qualified electronic signature (КЕП/ЕЦП) systems — specifically engineers embedding UAPKI into SimplyAddinConnect, maintaining 1C native components, or debugging tax.gov.ua fiscal server rejections.

How do I test UAPKI signing without a running 1C instance?

Use the ecp-testing-without-1c skill: it provides a native component test harness with IComponentBase emulation, enabling offline SIGN/VERIFY operations against test key material such as test-diia.p12, so the crypto stack can be validated independently of the 1C host.

What are the prerequisites for the 1C native component skill?

You need a Windows build environment and familiarity with the 1C AddInNative API: MANIFEST.XML packaging, the IComponentBase/ExtCompT interfaces, tVariant types, and handling the dependent-DLL problem when delivering the external component to end users.

Which cryptographic standards and formats are covered?

The skills cover Ukrainian national standards: DSTU 4145 signatures, CAdES-BES and ДСТУ 7564 (Купина) for PRRO fiscal documents, plus UAPKI provider concepts including cm-pkcs12 key storages, cmProviders configuration, and the process json_free call convention.