Наверное я не очень хорошо сформулировал вопрос. Допустим есть приложение которое берет пароли в зашифрованном виде (обычного пользователя же не будешь заставлять разбираться с ключами), поэтому хотел узнать где принято хранить ключ локально.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for ar... ar
checking the archiver (ar) interface... ar
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for ANSI C header files... no
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.20... yes
checking for egrep... (cached) /bin/grep -E
checking for a sed that does not truncate output... (cached) /bin/sed
checking whether g++ supports C++11 features by default... yes
checking for __attribute__((format))... yes
checking for REVENGE... yes
checking for LIBXML... yes
checking for ICU... yes
checking for boost/algorithm/string.hpp... yes
checking for boost/cstdint.hpp... yes
checking for boost/lexical_cast.hpp... yes
checking for boost/optional.hpp... yes
checking for boost/phoenix.hpp... yes
checking for boost/spirit/include/qi.hpp... yes
checking for CPPUNIT... yes
checking for REVENGE_STREAM... yes
checking for REVENGE_GENERATORS... yes
checking for native Win32... no
checking for Win32 platform in general... no
checking for -fvisibility=hidden compiler flag... yes
checking for doxygen... no
configure: WARNING: *** Could not find doxygen in your PATH.
configure: WARNING: *** The documentation will not be built.
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/conv/Makefile
config.status: creating src/conv/raw/Makefile
config.status: creating src/conv/raw/vsd2raw.rc
config.status: creating src/conv/raw/vss2raw.rc
config.status: creating src/conv/svg/Makefile
config.status: creating src/conv/svg/vsd2xhtml.rc
config.status: creating src/conv/svg/vss2xhtml.rc
config.status: creating src/conv/text/Makefile
config.status: creating src/conv/text/vsd2text.rc
config.status: creating src/conv/text/vss2text.rc
config.status: creating src/fuzz/Makefile
config.status: creating src/lib/Makefile
config.status: creating src/lib/libvisio.rc
config.status: creating src/test/Makefile
config.status: creating inc/Makefile
config.status: creating inc/libvisio/Makefile
config.status: creating build/Makefile
config.status: creating build/win32/Makefile
config.status: creating docs/Makefile
config.status: creating docs/doxygen/Makefile
config.status: creating libvisio-0.1.pc
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
configure:
==============================================================================
Build configuration:
debug: no
docs: no
fuzzers: no
tests: yes
tools: yes
werror: no
weffc: yes
wparanoic: no
==============================================================================
pindschik, а виртуализацию вы имеете ввиду посредством Vmvare, vbox и т.д. или есть более легкие способы для создания нескольких виртуальных сетевых адаптеров?
Постараюсь на конкретном примере описать ситуацию, допустим создаем виртуальную машину в vmvare, дальше создаем в ней три сетевых адаптера и получается так, что компьютер может находится в трех разных сетях одновременно, и я хотел узнать есть ли ПО для физических машин, чтобы создавать такие адаптеры.