Home
last modified time | relevance | path

Searched refs:would (Results 1 – 25 of 911) sorted by relevance

12345678910>>...37

/freebsd/crypto/openssl/doc/designs/quic-design/
H A Dquic-thread-assist.md14 handshake layer, this would require a very large number of code changes to add
25 For locking of API calls the lock would only be held for the separate get and
26 set calls, but the combination of the two would not be safe if the assist thread
33 We would offer something like `SSL_lock()` and `SSL_unlock()`.
35 calls, would be required to take the lock. As a special exemption, an
43 It would also only be required for applications which want to use thread
60 future which would be processed by the handshake layer.
74 handshake completion (which would in itself be highly unusual), we simply
89 thread and may not be touched further. We would need to block all API calls
90 which would forward to the HL after connection commences (specifically, after
[all …]
H A Ddgram-api.md32 which would pollute the environment of applications which include
57 concurrent use on the same BIO. If they read or modify BIO state, they would
59 `BIO_dgram`) would otherwise be a straight system call.
66 them is by copying the data to be sent into a staging buffer. This would
68 zero/single-copy requirements. Moreover, it would lead to extremely
78 - Even if we did support iovecs, we would have to impose a limit
82 would need to be allocated on the stack.
91 this on-demand would require state in the BIO to determine whether this
92 functionality is currently switched on, which would require otherwise
208 - We would need to include the OS headers which provide these
[all …]
/freebsd/contrib/tcsh/
H A DWishList55 Wish "tcsh -l" would accept other flags. At least "-c".
60 would be to not have the different environment for login compared to
61 other shells, but what I would really like is something like...
95 over the last line, and the copy paste it. It would be very nice, if
101 which would insert the last line of output, similarly <M-2> could
123 variable editing to understand string operations. So I would like to
168 A Csh compatability mode would be nice: I know tcsh is supposed to be
215 Wish tcsh would feature fc (fix command) as in bash !Wish tcsh would
221 Functions would be useful! As would being able to redirect stderr (or
233 "complete cd" at the shell prompt nothing is printed. It would be nice
[all …]
/freebsd/tests/sys/kern/tty/
H A Dtest_recanon.orch80 -- Finally, swap VEOF out with ^F; before recent changes, we would remain
81 -- canonicalized at Test^D and the kernel would block on it unless a short
82 -- buffer was used since VEOF would not appear within the canonicalized bit.
/freebsd/usr.bin/indent/tests/
H A Delsecomment.018 /* Old indent would remove the 3 blank lines above, awaiting "else". */
34 else /* Old indent would get very confused here */
H A Delsecomment.0.stdout24 /* Old indent would remove the 3 blank lines above, awaiting "else". */
39 else /* Old indent would get very confused here */
/freebsd/usr.sbin/cron/doc/
H A DMAIL70 This method would prove very helpful for those programs that get started
72 number would specify the base time, and the second number the repetition
98 figured it out ) but a comment feature would SURE BE NICE!.
111 Hi, I do have a BIG one that I would like. I want to log ALL output
114 This would seem to work best if done by cron, as it is now I have a google
148 or second since the command was last run would be pretty hard to
187 Get the picture? This would be compatible with existing versions of
189 that old crontabs would be handled correctly).
207 Log files! It would be nice to be able to specify a log for cron
209 The latter can of course be done with > and 2> but it would be nice if
[all …]
/freebsd/contrib/llvm-project/llvm/lib/Target/SystemZ/
H A DREADME.txt61 part of 128-bit memory operations would probably need to be done
89 but truncating the load would give:
122 address into a register. In many cases it would be better to create
141 that rounded amount. It would be simpler to subtract the unrounded
158 for signed overflow check is currently quite bad. This would improve
/freebsd/libexec/bootpd/
H A DToDo15 would have only one case for each data type instead of one case for
16 every recognized option symbol. Then adding a new tag would involve
18 Hopefully, this would shrink the code a bit too. -gwr
/freebsd/crypto/openssl/doc/designs/
H A Dxof.md96 - A call to EVP_DigestSqueeze() after EVP_DigestFinalXOF() would fail since
98 - A call to EVP_DigestFinalXOF() after the EVP_DigestSqueeze() would fail.
106 - This would separate the XOF operations so that the interface consisted
113 an EVP_MD object. This would then complicate the Signature API also.
114 - Duplication of the EVP_MD code (although all legacy/engine code would be
126 The terms extract and expand are used by HKDF so I think this name would be
214 - This C code also needs to be written in assembler, the logic would also be
217 - The general SHA3 case would be slower unless code was duplicated.
/freebsd/crypto/openssl/crypto/property/
H A DREADME.md15 all of their implemented algorithms. E.g. the FIPS property would be set
47 maintained separately. This cache would be a hash table, indexed by
49 would share their definition structure. Again, reducing space use.
51 * A query cache is desirable. This would be a hash table keyed by the
52 algorithm identifier and the entire query string and it would map to
/freebsd/sys/contrib/openzfs/config/
H A Dax_compare_version.m448 # would both be true.
53 # would both be false.
57 # would be true because it is only comparing two minor versions.
61 # would be true because it is only comparing the lesser number of minor
68 # The author would like to acknowledge Guido Draheim whose advice about
/freebsd/tools/test/stress2/misc/
H A Dradix.sh80 4104, 4105, ... in each of the VM objects. (The sequence would be
83 Each of the VM objects would have only one less interior node in the
/freebsd/contrib/file/magic/Magdir/
H A Dunknown12 # long, as it would be on a VAX. In any case, that could collide with
14 # binaries, so the first 16 bits of the file would contain 0x10B.
/freebsd/share/examples/ipfilter/rules/
H A Dftp-proxy23 then you would do:
34 203.45.67.90, you would do:
/freebsd/sys/contrib/device-tree/Bindings/arm/msm/
H A Dqcom,idle-state.txt14 When the WFI instruction is executed the ARM core would gate its internal
30 sequence and would wait for interrupt, before restoring the cpu to execution
43 into a EL. Failing to do so, would result in a crash enforced by the warm boot
53 of this low power mode would be considered high even though at a cpu level,
/freebsd/sys/contrib/device-tree/Bindings/net/
H A Dmarvell-neta-bm.txt15 Otherwise the driver would adjust a given number or choose default if
19 type is 'short'. For 'long' ones it would be overridden by port's MTU.
/freebsd/crypto/openssl/doc/man3/
H A DX509_check_host.pod32 by default, the host B<name> "www.example.com" would match a
66 currently no B<flags> that would affect the behavior of this call.
118 values which start with ".", that would otherwise match any sub-domain
121 would match a peer certificate with a DNS name of "www.example.com",
122 but would not match a peer certificate with a DNS name of
H A DASYNC_WAIT_CTX_new.pod53 this would have a one-to-one correspondence with an SSL connection.
99 waiting on by calling ASYNC_WAIT_CTX_set_wait_fd(). Typically this would be done
113 An example of typical usage might be an async capable engine. User code would
114 initiate cryptographic operations. The engine would initiate those operations
173 code would initiate cryptographic operations, and the engine code would dispatch
175 code would call ASYNC_pause_job() to return control to the user code. After
/freebsd/contrib/libpcap/
H A DCONTRIBUTING.md25 would not be too intrusive, it would be best to contribute some development time
/freebsd/contrib/ldns/m4/
H A Dax_have_poll.m413 # interface. A neat usage example would be:
25 # AX_HAVE_POLL would succeed if AX_HAVE_PPOLL has, but not the other way
/freebsd/contrib/libder/
H A DREADME.md7 re-encode the resulting tree would apply any normalization expected by a DER
27 present it to the application in that way. It would be normalized on
/freebsd/crypto/openssl/
H A DREADME-ENGINES.md76 would help make this happen.
190 following code would load and use it (NB: obviously this code has no
200 of thing. For example the above code excerpt would achieve much the
218 such commands through to ENGINEs. As such, you would select "dynamic"
219 as the ENGINE to use, and the parameters/commands you pass would
234 value. In such a case, the command would be passed to the ENGINE after
235 it has been initialised for use, and so the "-post" switch would be
248 would have to use "dynamic" to load any such ENGINE - but on the other
249 hand such applications would only have the memory footprint of any
294 before. 'gcc' on Linux, for example, would use the following syntax;
/freebsd/usr.bin/indent/
H A DREADME28 | the public domain. I knew I would be sorry I made that posting.
34 | code. It had a bunch of different options that would let you format
77 comp.sources.unix. I would suggest that with the permission of you
89 me know that 4.3 version is off-limits, in which case we would probably
/freebsd/sys/contrib/device-tree/Bindings/arm/
H A Dsecure.txt9 space, or visible in both. (One example of that situation would be a
16 instance "secure-foo" would override "foo". For property names with
17 a vendor prefix, the Secure variant of "vendor,foo" would be

12345678910>>...37