Lines Matching full:sector

55  * HMAC has to be stored in the same place (namely in the same sector) to make
60  * Let's store HMAC in sector. This is a must. This leaves us 480 bytes for
62  * sector size). We need another sector from where we take only 32 bytes of data
64  * original provider at the input and leaves us one sector of authenticated data
66  * Now, let's assume, we want to create provider with 4096 bytes sector.
68  * need nine 512-bytes sectors at the input to get one 4096-bytes sector at the
69  * output. That's better. With 4096 bytes sector we can use 89% of size of the
71  * The reliability comes from the fact, that every HMAC stored inside the sector
72  * is calculated only for the data in the same sector, so its impossible to
90  * PS. You can use any sector size with geli(8). My example is using 4kB,
104  * Here we generate key for HMAC. Every sector has its own HMAC key, so it is
106  * We cannot depend on fact, that every sector has its own IV, because different
155 		/* Which relative sector this request decrypted. */  in g_eli_auth_read_done()
186 		/* Number of data bytes in one encrypted sector, eg. 480. */  in g_eli_auth_read_done()
192 		/* Last sector number in every big sector, eg. 9. */  in g_eli_auth_read_done()
215 		/* Number of data bytes in one encrypted sector, eg. 480. */  in g_eli_auth_read_done()
221 		/* Last sector number in every big sector, eg. 9. */  in g_eli_auth_read_done()
236 				 * this is the first corrupted sector and  in g_eli_auth_read_done()
467 	/* Number of data bytes in one encrypted sector, eg. 480. */  in g_eli_auth_run()
473 	/* Last sector number in every big sector, eg. 9. */  in g_eli_auth_run()
522 			 * Last encrypted sector of each decrypted sector is  in g_eli_auth_run()
531 			 * per-sector data size is rounded down to ensure that  in g_eli_auth_run()
533 			 * padding.  In this case, each sector contains unused  in g_eli_auth_run()