Как зарегистрировать домен и не попасть под суд

Building VirtualBox

  1. Change to the root directory and execute our configure script to setup your build environment:
    cscript configure.vbs

    If the script finds all the tools necessary, it will output two files: AutoConfig.kmk containing information where to find the tools on your system and env.bat, a batch file to setup your environment for building VirtualBox. You only have to execute this step once, unless something about your tools changes in which case you have to repeat the above step. Keep in mind that the script always overwrites the two generated files so you should not manually edit them.

  1. Change to the root directory of the sources and enter our build shell environment: env.bat.
  1. To manually override any tool or change Config.kmk settings, create LocalConfig.kmk in the root directory of the sources and place the setting there. See for an incomplete list of possible settings.
  1. To build a release package, type kmk. This produces the binaries in out\win.x86\release\bin (or out\win.amd64\release\bin on 64-bit hosts). If you want to build a debug version, enter kmk KBUILD_TYPE=debug.
  1. To create an .msi package, type `kmk packing’.
    This step will fail for a 64-bit (amd64) target if the Guest Additions are part of the build process (which is the default, disable by adding VBOX_WITH_ADDITIONS= and VBOX_WITH_ADDITIONS_PACKING= to LocalConfig.kmk, see ). It will complain about a dependency to VBoxOGL* libraries in out\win.x86\release\bin\additions. In that case, create the 32-bit Guest Additions by executing


    After that, type kmk packing again and it should succeed.

Using Visual C++ 2010 Express

If you don’t have a Visual C++ license you can use Visual C++ 2010 Express. However, you will not be able to build any frontend because the VirtualBox COM API — which all the other front ends program against — requires the Active Template Library (ATL) to build, and unfortunately the express edition doesn’t include this (see ).

When doing the first build step, you have to add —with-VC-Express-Edition to the argument list:

cscript configure.vbs --with-VC-Express-Edition

Excluding certain features from building

Here is an incomplete list of settings which could be added to LocalConfig.kmk to prevent certain features from building / packing:

Don’t build + package the VirtualBox Guest Additions. If only VBOX_WITH_ADDITIONS= is specified then the Guest Additions are not built but the VBoxGuestAdditions.iso file is expected to be present in the ‘out\win.ARCH\release\bin\additions‘ directory.
Build the Guest Additions exclusively.
Don’t build + package the VirtualBox validation kit. The validation kit is not part of the final .msi package anyway.
Don’t build + package the webservices API server.

Disable Windows hardening. Useful for testing. Do not use this setting for production builds! Without hardening the binaries are not signed and VirtualBox.exe can be started straight away from the out\…\bin directory (kmk packing + installation not required).
Please note that it’s still necessary to enablg to be able to start VMs as Windows refuses to load unsigned kernel drivers.

Setting up self signing (64-bit Windows, 32-bit Windows 10)

Setting up test signing will allow to build signed binaries to make Windows happy. To use the test-signed binaries, the target machine has to run in test signing mode and the test certificate has to be installed on the target machine.

Part 1: creating and installing the test certificate

  1. Launch an elevated command line shell (Vista and later).
  2. makecert.exe -r -pe -ss my -eku -n "CN=MyTestCertificate" mytestcert.cer
  3. certmgr.exe -add mytestcert.cer -s -r localMachine root
  4. Start certmgr.exe and check that «MyTestCertificate» is listed both under «Personal» and «Trusted Root Certification Authorities».If you have a self-signed certificate installed and upgrade to Windows 10 it might happen that the certificate is still listed under «Trusted Root Certification Authorities» but not under «Personal» anymore. In that case, remove the old certificate using certmgr.msc and create a new certificate (see above) and install it.
  5. Keep the mytestcert.cer file in a safe place.

Part 2: configuring the system to run test signed code (Vista and later)

  1. Launch an elevated command line shell (Vista and later).
  2. Run Bcdedit.exe -set TESTSIGNING ON on an elevated cmd.exe prompt.
  3. certmgr.exe -add mytestcert.cer -s -r localMachine root
  4. certmgr.exe -add mytestcert.cer -s -r localMachine trustedpublisher
  5. Reboot.
  6. Vista and later: «Test Mode» will appear in all four corners of the desktop and «Microsoft (R) Windows (R) (Build 6000)» will appear on the top. Windows 7 and later: «Test Mode<CR>Windows 7<CR>Build 7600» or equivalent will appear in the lower right corner.

Part 3: building VirtualBox with signing enabled

  1. If you called the certificate something other than MyTestCertificate you’ll have make the appropriate overrides in LocalConfig.kmk. See the Code Signing section of Config.kmk for what can be overridden.
  2. Add VBOX_SIGNING_MODE=test to LocalConfig.kmk.
  3. Build (incremental is sufficient).

Как проверить регистратора и реселлера

Прежде чем проводить действия по регистрации следует самому проверить компанию на порядочность.

Проверка регистратора

  • Проверьте является ли он аккредитованным. Сделать это можно как я писал уже выше на сайте https://cctld.ru/domains/reg/
  • Обязательно читайте отзывы в интернете
  • Проверьте домен регистратора в whois

Проверка реселлера

Здесь немного сложнее. Давайте рассмотрим на примере хостинг-провайдера

  • Уточните в службе поддержки хостинга у какого регистратора будет зарегистрирован домен. Эта информация должна быть на сайте реселлера но как правило чтобы ее найти надо постараться.
  • После того как узнаете обратитесь в службу поддержки самого регистратора и спросите является ли хостинг где собираетесь регистрировать свой домен их партнером.

❓ Часто задаваемые вопросы

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *