[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-6277":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":18,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":22,"topics":24,"createdAt":10,"pushedAt":10,"updatedAt":30,"readmeContent":31,"aiSummary":32,"trendingCount":16,"starSnapshotCount":16,"syncStatus":33,"lastSyncTime":34,"discoverSource":35},6277,"VeraCrypt","veracrypt\u002FVeraCrypt","veracrypt","Disk encryption with strong security based on TrueCrypt","https:\u002F\u002Fveracrypt.jp",null,"C",9950,1196,226,417,0,8,37,191,40.23,"Other",false,"master",[25,26,27,28,7,29],"encryption","encryption-algorithms","encryption-decryption","idrix","veracrypt-source","2026-06-12 02:01:17","This archive contains the source code of VeraCrypt.\nIt is based on the original TrueCrypt 7.1a with security enhancements and modifications.\n\n# Important\n\nYou may use the source code contained in this archive only if you accept and\nagree to the license terms contained in the file 'License.txt', which is\nincluded in this archive.\n\nNote that the license specifies, for example, that a derived work must not be\ncalled 'TrueCrypt' or 'VeraCrypt'\n\n# Contents\n\n[I. Windows](#i-windows)\n\n[II. Linux and Mac OS X](#ii-linux-and-mac-os-x)\n\n[III. FreeBSD](#iii-freebsd)\n\n[IV. Third-Party Developers (Contributors)](#iv-third-party-developers-contributors)\n\n[V. Legal Information](#v-legal-information)\n\n[VI. Further Information](#vi-further-information)\n\n# I. Windows\n\n## Requirements for Building VeraCrypt for Windows:\n\nA detailed guide on how to build VeraCrypt on Windows can be found in\nthe [documentation](.\u002Fdoc\u002Fhtml\u002Fen\u002FCompilingGuidelineWin.html) in the repository and\nit is also available [online](https:\u002F\u002Fveracrypt.jp\u002Fen\u002FCompilingGuidelineWin.html) or on the [mirror](https:\u002F\u002Fveracrypt.io\u002Fen\u002FCompilingGuidelineWin.html).\n\nIMPORTANT:\n\nThe 64-bit editions of Windows Vista and later versions of Windows, and in\nsome cases (e.g. playback of HD DVD content) also the 32-bit editions do not\nallow the VeraCrypt driver to run without an appropriate digital signature.\nTherefore, all .sys files in official VeraCrypt binary packages are digitally\nsigned with the digital certificate of the IDRIX, which was issued by\nGlobalSign certification authority. At the end of each official .exe and\n.sys file, there are embedded digital signatures and all related certificates\n(i.e. all certificates in the relevant certification chain, such as the\ncertification authority certificates, CA-MS cross-certificate, and the\nIDRIX certificate).\n\nKeep this in mind if you compile VeraCrypt and compare your binaries with the\nofficial binaries. If your binaries are unsigned, the sizes of the official\nbinaries will usually be approximately 10 KiB greater than the sizes of your\nbinaries (there may be further differences if you use a different version of\nthe compiler, or if you install a different or no service pack for Visual\nStudio, or different hotfixes for it, or if you use different versions of\nthe required SDKs).\n\n## Instructions for Signing and Packaging VeraCrypt for Windows:\n\nFirst, create an environment variable 'WSDK81' pointing to the Windows SDK\nfor Windows 8.1 installation directory.\n\nThe folder \"Signing\" contains a batch file (sign.bat) that will sign all\nVeraCrypt components using a code signing certificate present on the\ncertificate store and build the final installation setup and MSI package.\nThe batch file assumes that the code signing certificate is issued by\nGlobalSign. This is the case for IDRIX's certificate. If yours is issued by\nanother CA, then you should put its intermediate certificates in the \"Signing\"\nfolder and modify sign.bat accordingly.\n\nTo generate MSI packages, WiX Toolset v3.11 must be installed.\n\n## VeraCrypt EFI Boot Loader:\n\nVeraCrypt source code contains pre-built EFI binaries under src\\Boot\\EFI.\nThe source code of VeraCrypt EFI Boot Loader is licensed under LGPL and\nit is available at https:\u002F\u002Fgithub.com\u002Fveracrypt\u002FVeraCrypt-DCS.\nFor build instructions, please refer to the file src\\Boot\\EFI\\Readme.txt.\n\n# II. Linux and Mac OS X\n\nA detailed guide on how to build VeraCrypt on Linux can be found in\nthe [documentation](.\u002Fdoc\u002Fhtml\u002Fen\u002FCompilingGuidelineLinux.html) in the repository and\nit is also available [online](https:\u002F\u002Fveracrypt.jp\u002Fen\u002FCompilingGuidelineLinux.html) or on the [mirror](https:\u002F\u002Fveracrypt.io\u002Fen\u002FCompilingGuidelineLinux.html).\n\n## Requirements for Building VeraCrypt for Linux and Mac OS X:\n\n- GNU Make\n- GNU C++ Compiler 4.0 or compatible\n- Apple Xcode or Xcode command line tools (Mac OS X only)\n- YASM 1.3.0 or newer (Linux only, x86\u002Fx64 architecture only)\n- pkg-config\n- wxWidgets 3.0 shared library and header files installed or\n  wxWidgets 3.0 library source code (available at https:\u002F\u002Fwww.wxwidgets.org)\n- FUSE library and header files (available at https:\u002F\u002Fgithub.com\u002Flibfuse\u002Flibfuse\n  and https:\u002F\u002Fmacfuse.github.io\u002F)\n- PCSC-lite library and header files (available at https:\u002F\u002Fgithub.com\u002FLudovicRousseau\u002FPCSC)\n\n## Instructions for Building VeraCrypt for Linux and Mac OS X:\n\n1. Change the current directory to the root of the VeraCrypt source code.\n\n2. If you have no wxWidgets shared library installed, run the following\n   command to configure the wxWidgets static library for VeraCrypt and to\n   build it:\n\n   `$ make WXSTATIC=1 WX_ROOT=\u002Fusr\u002Fsrc\u002FwxWidgets wxbuild`\n\n   The variable `WX_ROOT` must point to the location of the source code of the\n   wxWidgets library. Output files will be placed in the '.\u002Fwxrelease\u002F'\n   directory.\n\n3. To build VeraCrypt, run the following command:\n\n   `$ make`\n\n   or if you have no wxWidgets shared library installed:\n\n   `$ make WXSTATIC=1`\n\n4. If successful, the VeraCrypt executable should be located in the directory\n   'Main'.\n\nBy default, a universal executable supporting both graphical and text user\ninterface (through the switch --text) is built.\nOn Linux, a console-only executable, which requires no GUI library, can be\nbuilt using the 'NOGUI' parameter:\n\n`$ make NOGUI=1 WXSTATIC=1 WX_ROOT=\u002Fusr\u002Fsrc\u002FwxWidgets wxbuild`\n\n`$ make NOGUI=1 WXSTATIC=1`\n\nOn MacOSX, building a console-only executable is not supported.\n\n## Mac OS X specifics:\n\nUnder MacOSX, the latest installed SDK is used by default. To use a different version\nof the SDK when building using make, you can export the environment variable VC_OSX_SDK:\n\n`$ export VC_OSX_SDK=13.0`\n\nFor development dependencies management, you can use [homebrew](https:\u002F\u002Fbrew.sh).\n\n`$ brew install pkg-config yasm wxwidgets`\n\nYou also need system dependencies\n\n`$ brew install --cask macfuse packages`\n\nAfter installing dependencies via brew, you can build a local development build\n\n`$ .\u002Fsrc\u002FBuild\u002Fbuild_veracrypt_macosx.sh -b`\n\nIf you want to build the package, you must pass `-p` to the build script above. The built\nexecutable will be in `.src\u002FMain`\n\nIf you prefer to build from sources, or without homebrew, pkg-config and packages must be installed.\n\nGet pkg-config from https:\u002F\u002Fpkgconfig.freedesktop.org\u002Freleases\u002Fpkg-config-0.29.2.tar.gz and\ncompile using the following commands:\n\n`$ CFLAGS=\"-Wno-int-conversion\" CXXFLAGS=\"-Wno-int-conversion\" .\u002Fconfigure --with-internal-glib`\n\n`$ make`\n\n`$ sudo make install`\n\nAfter making sure pkg-config is available, download and install macFUSE from\nhttps:\u002F\u002Fmacfuse.github.io\u002F\n\nThe [build_veracrypt_macosx.sh](.\u002Fsrc\u002FBuild\u002Fbuild_veracrypt_macosx.sh) script performs the\nfull build of VeraCrypt including the creation of the installer pkg. It expects\nto find the wxWidgets 3.2.5 sources at the same level as where you put\nVeraCrypt sources (i.e. if \"src\" path is \"\u002FUsers\u002Fjoe\u002FProjects\u002FVeraCrypt\u002Fsrc\"\nthen wxWidgets should be at \"\u002FUsers\u002Fjoe\u002FProjects\u002FwxWidgets-3.2.5\")\n\nThe make build process uses Code Signing certificates whose ID is specified in\nsrc\u002FMain\u002FMain.make (look for lines containing \"Developer ID Application\" and\n\"Developer ID Installer\"). You'll have to modify these lines to put the ID of\nyour Code Signing certificates or comment them out if you don't have one.\n\nBecause of incompatibility issues with macFUSE, the SDK 10.9 generates a\nVeraCrypt binary that has issues communicating with the macFUSE kernel extension.\nThus, we recommend using a different macOS SDK version for building VeraCrypt.\n\nThe Packages installer that is used for the VeraCrypt official build has been notarized by IDRIX and it is available at\nhttps:\u002F\u002Fgithub.com\u002Fidrassi\u002Fpackages\u002Freleases\n\n# III. FreeBSD\n\nFreeBSD is supported starting from version 11.\nThe build requirements and instructions are the same as Linux except that gmake\nshould be used instead of make.\n\n# IV. Third-Party Developers (Contributors)\n\nIf you intend to implement a feature, please contact us first to make sure:\n\n1. That the feature has not been implemented (we may have already implemented\n   it, but haven't released the code yet).\n2. That the feature is acceptable.\n3. Whether we need the help of third-party developers with implementing the feature.\n\nInformation on how to contact us can be found at:\nhttps:\u002F\u002Fveracrypt.jp\u002F\nhttps:\u002F\u002Fveracrypt.io\u002F (mirror)\n\n# V. Legal Information\n\n## Copyright Information\n\nThis software as a whole:  \nCopyright (c) 2025 AM Crypto. All rights reserved.  \n\nPortions of this software:  \nCopyright (c) 2025 AM Crypto. All rights reserved.  \nCopyright (c) 2013-2025 IDRIX. All rights reserved.  \nCopyright (c) 2003-2012 TrueCrypt Developers Association. All rights reserved.  \nCopyright (c) 1998-2000 Paul Le Roux. All rights reserved.  \nCopyright (c) 1998-2008 Brian Gladman, Worcester, UK. All rights reserved.  \nCopyright (c) 1995-2023 Jean-loup Gailly and Mark Adler.  \nCopyright (c) 2016 Disk Cryptography Services for EFI (DCS), Alex Kolotnikov  \nCopyright (c) 1999-2023 Dieter Baron and Thomas Klausner.  \nCopyright (c) 2013, Alexey Degtyarev. All rights reserved.  \nCopyright (c) 1999-2016 Jack Lloyd. All rights reserved.  \nCopyright (c) 2013-2019 Stephan Mueller \u003Csmueller@chronox.de>  \nCopyright (c) 1999-2023 Igor Pavlov  \n\nFor more information, please see the legal notices attached to parts of the\nsource code.\n\n## Trademark Information\n\nAny trademarks contained in the source code, binaries, and\u002For in the\ndocumentation, are the sole property of their respective owners.\n\n# VI. Further Information\n\nhttps:\u002F\u002Fveracrypt.jp\nhttps:\u002F\u002Fveracrypt.io (mirror)\n","VeraCrypt 是一个基于 TrueCrypt 的磁盘加密软件，提供强大的安全性能。它通过增强的安全特性和修改来保护用户数据，支持多种加密算法，并且能够在 Windows、Linux、Mac OS X 以及 FreeBSD 等操作系统上运行。项目采用 C 语言编写，确保了良好的跨平台兼容性与执行效率。适用于需要对敏感信息进行高级别保护的场景，如个人隐私保护、企业数据安全管理等。此外，VeraCrypt 还提供了详细的编译指南和签名打包说明，方便开发者自定义构建适合特定需求的版本。",2,"2026-06-11 03:06:12","top_language"]