Home
last modified time | relevance | path

Searched refs:work (Results 1 – 25 of 55) sorted by relevance

123

/lib/zlib/
A Dinftrees.c34 unsigned short FAR *work) in inflate_table() argument
143 if (lens[sym] != 0) work[offs[lens[sym]]++] = (unsigned short)sym; in inflate_table()
180 base = extra = work; /* dummy value--not used */ in inflate_table()
213 if (work[sym] + 1 < match) { in inflate_table()
215 this.val = work[sym]; in inflate_table()
216 } else if (work[sym] >= match) { in inflate_table()
217 this.op = (unsigned char)(extra[work[sym] - match]); in inflate_table()
218 this.val = base[work[sym] - match]; in inflate_table()
249 len = lens[work[sym]]; in inflate_table()
A Dinftrees.h55 unsigned FAR *bits, unsigned short FAR *work));
A Dinflate.h113 unsigned short work[288]; /* work area for code table building */ member
A Dinflate.c652 &(state->lenbits), state->work); in inflate()
719 &(state->lenbits), state->work); in inflate()
728 &(state->next), &(state->distbits), state->work); in inflate()
/lib/lwip/lwip/contrib/apps/LwipMibCompiler/SharpSnmpLib/
A Dlicense.txt111 "work based on the library" and a "work that uses the library". The
130 Library" means either the Library or any derivative work under
136 "Source code" for a work means the preferred form of the work for
163 of it, thus forming a work based on the Library, and copy and
167 a) The modified work must itself be a software library.
190 These requirements apply to the modified work as a whole. If
243 work, in isolation, is not a derivative work of the Library, and
268 Any executables containing that work also fall under Section 6,
273 work containing portions of the Library, and distribute that work
286 a) Accompany the work with the complete corresponding
[all …]
/lib/mbedtls/external/mbedtls/library/
A Dpkcs5.c277 unsigned char work[MBEDTLS_MD_MAX_SIZE]; in pkcs5_pbkdf2_hmac() local
306 if ((ret = mbedtls_md_hmac_finish(ctx, work)) != 0) { in pkcs5_pbkdf2_hmac()
314 memcpy(md1, work, md_size); in pkcs5_pbkdf2_hmac()
333 mbedtls_xor(work, work, md1, md_size); in pkcs5_pbkdf2_hmac()
337 memcpy(out_p, work, use_len); in pkcs5_pbkdf2_hmac()
351 mbedtls_platform_zeroize(work, MBEDTLS_MD_MAX_SIZE); in pkcs5_pbkdf2_hmac()
/lib/mbedtls/external/mbedtls/
A DLICENSE43 "Work" shall mean the work of authorship, whether in Source or
45 copyright notice that is included in or attached to the work
56 "Contribution" shall mean any work of authorship, including
186 APPENDIX: How to apply the Apache License to your work.
279 refers to any such program or work, and a "work based on the Program"
281 that is to say, a work containing the Program or a portion of it,
289 is covered only if its contents constitute a work based on the
305 of it, thus forming a work based on the Program, and copy and
328 These requirements apply to the modified work as a whole. If
369 The source code for a work means the preferred form of the work for
[all …]
A Ddco.txt21 (b) The contribution is based upon previous work that, to the best
24 work with modifications, whether created in whole or in part
A DREADME.md50 …, IAR 8 and Visual Studio 2017. More recent versions should work. Slightly older versions may work.
55 * Doxygen 1.8.11 or later (if building the documentation; slightly older versions should work).
162 CC=your_cc` will *not* work (similarly with `CFLAGS` and other variables).
302 …ryptographic accelerators, secure elements and random generators. This is work in progress. Please…
/lib/mbedtls/external/mbedtls/tests/git-scripts/
A DREADME.md7 …hooks` to `<Mbed TLS root>/tests/git-scripts`, in order to make the hook scripts successfully work.
14 **Note: Currently the Mbed TLS git hooks work only on a GNU platform. If using a non-GNU platform, …
/lib/mbedtls/external/mbedtls/docs/
A Ddriver-only-builds.md75 work in the same way as if the mechanisms where built-in, except as documented
93 APIs), as well as X.509 and TLS, will work as usual, except that direct calls
119 `MBEDTLS_MD_C` and still getting crypto operations, X.509 and TLS to work as
179 In such builds, all crypto operations via the PSA Crypto API will work as
293 `MBEDTLS_PKCS1_V21`, and RSA will still work in PSA Crypto.
298 PSA Crypto works. In particular, PK, X.509 and TLS will _not_ work with
376 - `MBEDTLS_CIPHER_C`: the `mbedtls_cipher_xxx()` APIs will only work with
380 - `MBEDTLS_PKCS5_C`: encryption/decryption (PBES2, PBE) will only work with
382 - PEM decryption will only work with ciphers that are built-in.
423 algorithm) in order to work with a driver.
[all …]
/lib/mbedtls/external/mbedtls/docs/architecture/psa-migration/
A Dmd-cipher-dispatch.md12 A difference between the original strategy and the current one is that in this work, we are not tre…
56 …this work is to arrange for more non-PSA interfaces to use PSA interfaces under the hood, without …
90 In this work, we want two things:
105 For the purposes of this work, three domains emerge:
115 Hashes and HMAC (after the work on driver-only hashes):
129 Symmetric ciphers and AEADs (before work on driver-only cipher):
207 …ve a fallback) if their caller is not in the PSA domain and the PSA call is not guaranteed to work.
235 Let us work through the example of RSA-PSS which calculates a hash, as in [see issue \#6497](https:…
298 * Mixed-domain code can assume that PSA buffer calculations work correctly for all algorithms that …
357 …xtend it to other block ciphers at the moment), while GCM and CCM need to work with 3 block cipher…
[all …]
A Dstrategy.md21 As of early 2023, work towards G5 is in progress: Mbed TLS 3.3 and 3.4 saw
83 It will then require follow-up work to make use of the new PSA APIs in
89 TLS, X.509 or PK. We can try to work around that by calling (the relevant
95 auto-enable the latter, as it won't build or work out of the box on all
96 platforms. There are two kinds of things we'd need to do if we want to work
247 We can roughly divide the work needed to get there in the following steps:
270 work is divided into PRs, sometimes not. For example, in situations where it's
349 we're making some part of the library work with hashes provided only by
393 Unfortunately that's unlikely to fully work. For example, the MD layer uses the
A Dpsa-limitations.md9 is, of course, to actually do the migration work.
77 when moving to PSA. Server-side would work as above; unfortunately
81 the one that requires the most work, but it would deliver value beyond PSA
/lib/lwip/lwip/src/netif/
A DFILES17 protocol. It requires a sio (serial I/O) module to work.
/lib/mbedtls/external/mbedtls/docs/architecture/psa-thread-safety/
A Dpsa-thread-safety.md7 Summary of recent work:
27 * The [Future work](#future-work) section outlines our long-term goals for thread-safety; it also a…
78 …work. Implementations which only ever call PSA functions from a single thread, or which protect al…
255 It is now possible for individual tests to spin up multiple threads. This work has made the global …
261 Our testing is a work in progress. It is not feasible to run our traditional, single-threaded, test…
273 Through future work on testing, it would be good to:
288 ## Future work
292 …m to make the entirety of the PSA API thread-safe. This will build on the work that we have alread…
316 …ion requirements](#long-term-key-destruction-requirements). Destruction would then work as follows:
335 ### Future driver work argument
[all …]
/lib/mbedtls/external/mbedtls/3rdparty/everest/
A DREADME.md5 …ms are supported, although the version in `everest/library/legacy` should work on most systems. Th…
/lib/mbedtls/external/mbedtls/tests/suites/
A Dtest_suite_psa_crypto_low_hash.function54 * guaranteed to work: the core must pass a sufficiently large
143 * guaranteed to work: the core must pass a sufficiently large
/lib/mbedtls/external/mbedtls/docs/architecture/testing/
A Dinvasive-testing.md20 …s what the crypto/keystore and X.509 parts of the library are about. More work is needed to fully …
88 * Portability: tests should work on every platform. Skipping tests on certain platforms may hide er…
89 …hould only enforce the documented behavior of the product, to avoid extra work when the product's …
180 …thing we currently do). Another limitation is that this approach does not work for users who patch…
189 | | ~ Doesn't work if the users rewrite an internal module |
197 * This does not work for platform-dependent properties unless we have a formal model of the platfor…
218 | | ~ Doesn't work if the users rewrite an internal module |
296 …in the PSA key store code, in particular that `psa_close_key` and `psa_destroy_key` work correctly.
/lib/lwip/lwip/src/apps/http/makefsdata/
A Dreadme.txt20 manually download minizip.c for this to work. As an alternative, you can additionally
/lib/lzma/
A Dhistory.txt11 - The BUG in LZMA SDK 9.* was fixed: LZMA2 codec didn't work,
163 previous versions could work incorrectly,
/lib/mbedtls/external/mbedtls/docs/proposed/
A Dpsa-driver-integration-guide.md4 **This is a specification of work in progress. The implementation is not yet merged into Mbed TLS.**
/lib/lwip/lwip/
A DUPGRADING3 application written for an older version of lwIP to correctly work
252 * added autoip_set_struct() and dhcp_set_struct() to let autoip and dhcp work
275 * Use macros defined in ip_addr.h to work with IP addresses
/lib/mbedtls/external/mbedtls/scripts/data_files/
A Dquery_config.fmt84 * WARNING: This does not work for expanding function-like macros. However,
/lib/mbedtls/external/mbedtls/docs/architecture/
A Dalternative-implementations.md22 …ot currently support alternative implementations. If this module does not work on your platform, d…
54 …anagement that can move objects on the heap.) That is, call sequences like the following must work:

Completed in 46 milliseconds

123