Home
last modified time | relevance | path

Searched refs:Windows (Results 1 – 25 of 420) sorted by relevance

12345678910>>...17

/src/sbin/pfctl/
H A Dpf.os121 # OS - OS genre (Linux, Solaris, Windows)
134 # you don't have a precise match, but can tell it's Windows or FreeBSD
381 # ----------------- Windows -----------------
383 # Windows TCP/IP stack is a mess. For most recent XP, 2000 and
386 # seem. Luckily for us, almost all Windows 9x boxes have an
390 8192:32:1:44:M*: Windows:3.11::Windows 3.11 (Tucows)
391 S44:64:1:64:M*,N,W0,N,N,T0,N,N,S: Windows:95::Windows 95
392 8192:128:1:64:M*,N,W0,N,N,T0,N,N,S: Windows:95:b:Windows 95b
395 # Windows 98 it is no longer possible to tell them from each other
399 S44:32:1:48:M*,N,N,S: Windows:98:lowTTL:Windows 98 (low TTL)
[all …]
/src/crypto/heimdal/doc/
H A Dwin2k.texi4 @node Windows compatibility, Programming with Kerberos, Kerberos 4 issues, Top
6 @chapter Windows compatibility
8 Microsoft Windows, starting from version 2000 (formerly known as Windows NT 5), implements Kerberos…
10 issues between Heimdal and various Windows versions.
12 The big problem with the Kerberos implementation in Windows
20 * Configuring Windows to use a Heimdal KDC::
21 * Inter-Realm keys (trust) between Windows and a Heimdal KDC::
25 * Quirks of Windows 2000 KDC::
26 * Useful links when reading about the Windows::
29 …ode Configuring Windows to use a Heimdal KDC, Inter-Realm keys (trust) between Windows and a Heimd…
[all …]
H A Dheimdal.texi72 * Windows compatibility::
116 Windows compatibility
118 * Configuring Windows to use a Heimdal KDC::
119 * Inter-Realm keys (trust) between Windows and a Heimdal KDC::
123 * Quirks of Windows 2000 KDC::
124 * Useful links when reading about the Windows::
/src/contrib/file/magic/Magdir/
H A Dwindows4 # windows: file(1) magic for Microsoft Windows
7 # using them are run almost always on MS Windows 3.x or
8 # above, or files only used exclusively in Windows OS,
10 # For example, even though WinZIP almost run on Windows
97 # Summary: Windows crash dump
104 # Note: called "Windows memory dump" by TrID
105 # and verified by like Windows Kit `Dumpchk.exe 043022-18703-01.dmp`
110 >4 string DUMP MS Windows 32bit crash dump
172 # Note: called "Windows 64bit Memory Dump" by TrID
174 >4 string DU64 MS Windows 64bit crash dump
[all …]
H A Dmsdos45 # MEXW32:MATLAB Windows 32bit compiled function https://en.wikipedia.org/wiki/MATLAB
46 # MEXW64:MATLAB Windows 64bit compiled function https://en.wikipedia.org/wiki/MATLAB
104 >>>(0x3c.l+0x36) byte 2 for MS Windows
182 # 1~IMAGE_SUBSYSTEM_NATIVE device drivers and native Windows processes
187 >>>0 default x for MS Windows
193 # - NT kernel drivers: Windows/System32/drivers/*.sys
203 # 2~IMAGE_SUBSYSTEM_WINDOWS_GUI The Windows graphical user interface (GUI) subsystem
208 >>>0 default x for MS Windows
226 # 3~IMAGE_SUBSYSTEM_WINDOWS_CUI The Windows character subsystem
231 >>>0 default x for MS Windows
[all …]
/src/crypto/openssl/doc/designs/ddd/
H A DWINDOWS.md1 Windows-related issues
4 Supporting Windows introduces some complications due to some "fun" peculiarities
5 of Windows socket API.
7 In general, Windows does not provide a poll(2) system call. WSAPoll(2) was introduced
10 finally fixed this bug in a build of Windows 10. So WSAPoll(2) is a viable
11 method, but only on fairly new versions of Windows.
15 platforms select() accepts a bitmask of FDs, on Windows select() accepts a
17 because sockets are NT kernel handles on Windows and thus are not allocated
18 contiguously like FDs. As such, Windows select() is actually very similar to
19 POSIX poll(), making select() a viable option for polling on Windows.
[all …]
/src/contrib/llvm-project/llvm/lib/Support/Windows/
H A DWatchdog.inc1 //===--- Windows/Watchdog.inc - Windows Watchdog Implementation -*- C++ -*-===//
9 // This file provides the generic Windows implementation of the Watchdog class.
15 // on Windows. Roughly, a Windows implementation would use CreateWaitableTimer
H A DCOM.inc1 //==- llvm/Support/Windows/COM.inc - Windows COM Implementation -*- C++ -*-===//
9 // This file implements the Windows portion of COM support.
14 //=== WARNING: Implementation here must contain only Windows code.
/src/contrib/ncurses/
H A DREADME.MinGW34 works at least on the Windows Console.
48 To build ncurses for native Windows with support for the new Windows 10 Virtual
51 required Windows SDK level. Please note that some of the Linux distributions
53 not be able to properly build the libraries for current Windows 10 using these
54 toolchains. Although it is a bit slow, MSYS2 on Windows 10 64-Bit is the
58 heavily UNIX based sourcebase to native Windows. The goal is of course
60 common traditional development environments on Windows, mainly with
63 The TERM environment variable must be set especially to activate the Windows
67 Beginning with build 17763 (Fall 2018 update), Windows 10 supports ANSI escape
69 Windows 10 version, the interpretation of the implicit TERM setting (which
[all …]
/src/crypto/krb5/src/windows/
H A DREADME1 Building & Running Kerberos 5 on Windows
4 This file documents how to build MIT Kerberos for Windows.
5 The MIT Kerberos for Windows distribution contains additional components
9 To build Kerberos 5 on Windows, you will need the following:
35 * To build an MSI installer, the Windows Installer XML (WiX) toolkit,
49 The krb5 source tree may be obtained either directly on the Windows
52 copied over, such as from a VM host onto a Windows VM. If you are
63 Runtime library, which is not found on most Windows systems unless
99 6) nmake -f Makefile.in prep-windows # Create Makefile for Windows
125 WARNING: Despite its name, this is not a Windows .ini file.
[all …]
/src/crypto/openssl/doc/man7/
H A DOSSL_STORE-winstore.pod5 OSSL_STORE-winstore - OpenSSL built in OSSL_STORE for Windows
9 The OSSL_STORE implementation for Windows provides access to Windows' system
32 =head2 Windows certificate store features
35 Windows certificate store also has the ability to associate additional
/src/crypto/krb5/src/windows/installer/wix/
H A Dmsi-deployment-guide.txt2 Kerberos for Windows
36 Beginning with "Kerberos for Windows" version 2.6.5, a MSI installer
37 option is available for those who wish to use "Windows Installer"
46 scripts so that machines where "Kerberos for Windows" is already
52 distributed with "Kerberos for Windows" releases from 2.6.5 and
57 Authoring a "Windows Installer" transform requires additional
60 which are included in the Windows Platform SDK ("Windows Installer"
66 For general information about "Windows Installer", refer to :
75 authoring transforms. While the MSDN documentation for Windows
100 distributed as part of the "Windows Installer" SDK (which in turn is
[all …]
/src/contrib/llvm-project/lld/docs/
H A Dwindows_support.rst14 Windows support
17 LLD supports Windows operating system. When invoked as ``lld-link.exe`` or with
18 ``-flavor link``, the driver for Windows operating system is used to parse
38 :good:`Done`. The format of static library (.lib) on Windows is actually the
47 Windows resource files support
66 The Windows version of LLD is included in the `pre-built binaries of LLVM's
/src/contrib/wpa/wpa_supplicant/
H A DREADME-Windows.txt1 wpa_supplicant for Windows
12 Supplicant on Windows. The current port requires that WinPcap
17 mainly on Windows XP (SP2) with limited set of NDIS drivers. In
18 addition, the current version has been reported to work with Windows
37 cross-compiling from Linux to MinGW/Windows. It should also be
38 possible to build this under Windows using the MinGW tools, but that
124 Using wpa_supplicant for Windows
130 version of wpa_supplicant, wpasvc.exe, which can be used as a Windows
137 Windows NDIS/WinPcap uses quite long interface names, so some care
194 the native build for Windows uses named pipes and the contents of the
[all …]
/src/crypto/openssl/Configurations/platform/Windows/
H A Dcppbuilder.pm1 package platform::Windows::cppbuilder;
5 require platform::Windows::MSVC;
H A DMSVC.pm1 package platform::Windows::MSVC;
9 require platform::Windows;
/src/crypto/openssl/
H A DNOTES-WINDOWS.md1 Notes for Windows platforms
11 There are various options to build and run OpenSSL on the Windows platforms.
13 "Native" OpenSSL uses the Windows APIs directly at run time.
78 - `perl Configure VC-WIN64-ARM` if you want Windows on Arm (win-arm64)
80 - `perl Configure VC-WIN64-CLANGASM-ARM` if you want Windows on Arm (win-arm64)
82 - `perl Configure VC-CLANG-WIN64-CLANGASM-ARM` if you want Windows on Arm (win-arm64)
108 constant defines. On Windows platforms however, installation directories are
135 A summary table of behavior on Windows platforms
143 Special notes for Universal Windows Platform builds, aka `VC-*-UWP`
185 * Usually the build is done on Windows in a GNU-like environment called MSYS2.
[all …]
/src/contrib/libpcap/doc/
H A DREADME.windows.md1 Building libpcap on Windows with Visual Studio
4 Unlike the UN*Xes on which libpcap can capture network traffic, Windows
26 such as a requirement to support versions of Windows earlier than
27 Windows Vista, which is the earliest version supported by Npcap.
44 Building libpcap on Windows requires Visual Studio 2015 or later. The
49 Windows with which those tools, and other tools, can be installed; it
75 runs on UN\*Xes and on Windows and that can generate project files for
93 for Windows" is installed.
105 expressions. Windows versions of Flex and Bison can be downloaded from
119 provided as an optional installation component, "Git for Windows", with
[all …]
/src/crypto/openssl/doc/man3/
H A DOpenSSL_version.pod167 The Windows install context.
168 The Windows install context is used to compute the OpenSSL registry key name
169 on Windows. The full registry key is
172 number and the Windows install context, respectively.
212 separator is C<:>) or C<%PATH%> on Windows (where the separator is
225 The Windows install context.
226 The Windows install context is used to compute the OpenSSL registry key name
227 on Windows. The full registry key is
230 number and the Windows install context, respectively.
/src/contrib/llvm-project/llvm/include/llvm/BinaryFormat/
H A DMinidumpConstants.def105 HANDLE_MDMP_PLATFORM(0x0000, Win32S) // Win32 on Windows 3.1
106 HANDLE_MDMP_PLATFORM(0x0001, Win32Windows) // Windows 95-98-Me
107 HANDLE_MDMP_PLATFORM(0x0002, Win32NT) // Windows NT, 2000+
108 HANDLE_MDMP_PLATFORM(0x0003, Win32CE) // Windows CE, Windows Mobile, "Handheld"
/src/contrib/libfido2/
H A DNEWS12 ** Support for linking against OpenSSL on Windows; gh#668.
86 ** Fixed detection of Windows's native webauthn API; gh#382.
91 ** Support for Windows's native webauthn API.
153 ** Hardened Windows build.
217 ** Command-line tools for Windows.
223 ** Windows: fix contents of release file.
229 ** Native HID support on Linux, MacOS, and Windows.
/src/contrib/bc/
H A Dbuild.rig36 if OS == "Windows" && bool(config["lto"])
38 error("Link-time optimization is not supported on Windows");
43 if OS != "Windows" && NLS_ENABLED != "0"
116 if OS != "Windows" && sym(config["history"]) != @none
187 if OS != "Windows" && !bool(config["debug"]) && !macos && bool(config["strip"])
225 else if OS == "Windows"
298 if OS != "Windows" && bool(config["install_manpages"])
313 if OS != "Windows" && bool(config["install_manpages"])
373 if OS != "Windows"
/src/contrib/unifdef/
H A DINSTALL24 Unlike the Unix Makefile, the Windows builds do not automatically
28 part of GitHub for Windows - http://windows.github.com/
34 as Windows that don't have them built in.
/src/contrib/tcpdump/cmake/Modules/
H A DFindPCAP.cmake13 # Building for Windows.
15 # libpcap isn't set up to install .pc files or pcap-config on Windows,
23 # for shared and static, Windows uses .lib both for import libraries
66 # We need to look for wpcap.dll in \Windows\System32\Npcap first,
71 # \Windows\System32, only in \Windows\System32\Npcap;
74 # API-compatible Mode", so the wpcap.dll in \Windows\System32
78 # it), and that's in \Windows\System32\Npcap;
81 # \Windows\System32 and \Windows\System32\Npcap have an Npcap
84 # Unfortunately, Windows has no notion of an rpath, so we can't
85 # set the rpath to include \Windows\System32\Npcap at link time;
[all …]
/src/contrib/expat/
H A DChanges72 #1032 Windows: Normalize .bat files to CRLF line endings
132 #1007 CMake|Windows: Fix -DEXPAT_MSVC_STATIC_CRT=ON
133 #1013 Windows: Drop support for Visual Studio <=16.0/2019
158 #1013 CI|Windows: Get off of deprecated image "windows-2019"
233 #944 Windows: Fix installer target location of file xmlwf.xml
235 #953 Windows: Address warning -Wunknown-warning-option
257 #791 #946 CI: Make GitHub Actions build using MSVC on Windows and
258 produce 32bit and 64bit Windows binaries
347 #741 Windows: Drop support for Visual Studio <=15.0/2017
457 against static libexpat using pkg-config on Windows
[all …]

12345678910>>...17