Searched refs:dht (Results 1 – 9 of 9) sorted by relevance
/third_party/ffmpeg/libavcodec/ |
D | mjpega_dump_header_bsf.c | 38 unsigned dqt = 0, dht = 0, sof0 = 0; in mjpega_dump_header() local 69 case DHT: dht = i + 46; break; in mjpega_dump_header() 73 bytestream_put_be32(&out_buf, dht); /* huff off */ in mjpega_dump_header()
|
D | vaapi_encode_mjpeg.c | 185 JPEGRawHuffmanTableSpecification *dht = &priv->huffman_tables; in vaapi_encode_mjpeg_write_extra_buffer() local 201 ht = &dht->table[2 * t]; in vaapi_encode_mjpeg_write_extra_buffer() 208 ht = &dht->table[2 * t + 1]; in vaapi_encode_mjpeg_write_extra_buffer()
|
D | cbs_jpeg.c | 317 SEGMENT(DHT, JPEGRawHuffmanTableSpecification, dht, NULL); in cbs_jpeg_read_unit() 373 SEGMENT(DHT, dht); in cbs_jpeg_write_segment()
|
D | cbs_jpeg_syntax_template.c | 102 static int FUNC(dht)(CodedBitstreamContext *ctx, RWContext *rw, in FUNC() argument
|
/third_party/node/deps/npm/node_modules/safe-buffer/ |
D | README.md | 412 #### [`bittorrent-dht`](https://www.npmjs.com/package/bittorrent-dht) 416 [`bittorrent-dht`](https://www.npmjs.com/package/bittorrent-dht). The bug would allow 417 anyone on the internet to send a series of messages to a user of `bittorrent-dht` and get 421 [the commit](https://github.com/feross/bittorrent-dht/commit/6c7da04025d5633699800a99ec3fbadf70ad35… 530 This solves the core problem that affected `ws` and `bittorrent-dht` which is 564 - [Node Security Project disclosure for`bittorrent-dht`](https://nodesecurity.io/advisories/68) 569 The original issues in `bittorrent-dht`
|
/third_party/node/deps/npm/node_modules/tar/node_modules/safe-buffer/ |
D | README.md | 412 #### [`bittorrent-dht`](https://www.npmjs.com/package/bittorrent-dht) 416 [`bittorrent-dht`](https://www.npmjs.com/package/bittorrent-dht). The bug would allow 417 anyone on the internet to send a series of messages to a user of `bittorrent-dht` and get 421 [the commit](https://github.com/feross/bittorrent-dht/commit/6c7da04025d5633699800a99ec3fbadf70ad35… 530 This solves the core problem that affected `ws` and `bittorrent-dht` which is 564 - [Node Security Project disclosure for`bittorrent-dht`](https://nodesecurity.io/advisories/68) 569 The original issues in `bittorrent-dht`
|
/third_party/node/deps/npm/node_modules/npm-registry-fetch/node_modules/safe-buffer/ |
D | README.md | 412 #### [`bittorrent-dht`](https://www.npmjs.com/package/bittorrent-dht) 416 [`bittorrent-dht`](https://www.npmjs.com/package/bittorrent-dht). The bug would allow 417 anyone on the internet to send a series of messages to a user of `bittorrent-dht` and get 421 [the commit](https://github.com/feross/bittorrent-dht/commit/6c7da04025d5633699800a99ec3fbadf70ad35… 530 This solves the core problem that affected `ws` and `bittorrent-dht` which is 564 - [Node Security Project disclosure for`bittorrent-dht`](https://nodesecurity.io/advisories/68) 569 The original issues in `bittorrent-dht`
|
/third_party/node/deps/npm/node_modules/string_decoder/node_modules/safe-buffer/ |
D | README.md | 414 #### [`bittorrent-dht`](https://www.npmjs.com/package/bittorrent-dht) 418 [`bittorrent-dht`](https://www.npmjs.com/package/bittorrent-dht). The bug would allow 419 anyone on the internet to send a series of messages to a user of `bittorrent-dht` and get 423 [the commit](https://github.com/feross/bittorrent-dht/commit/6c7da04025d5633699800a99ec3fbadf70ad35… 532 This solves the core problem that affected `ws` and `bittorrent-dht` which is 566 - [Node Security Project disclosure for`bittorrent-dht`](https://nodesecurity.io/advisories/68) 571 The original issues in `bittorrent-dht`
|
/third_party/openh264/res/ |
D | Cisco_Absolute_Power_1280x720_30fps.yuv | 2311 …75+! "!!"#"#&'**)*,,-+*-/.-/00///0121/135767768<;:;;<<>AB@@@DGILNOT^dht��������������������…
|