Ç¥ÁØÈ­ Âü¿©¾È³»

TTAÀÇ Ç¥ÁØÇöȲ

Ȩ > Ç¥ÁØÈ­ °³¿ä > TTAÀÇ Ç¥ÁØÇöȲ

Ç¥ÁعøÈ£ TTAK.KO-10.1182 ±¸Ç¥ÁعøÈ£
Á¦°³Á¤ÀÏ 2019-12-11 ÃÑÆäÀÌÁö 19
ÇѱÛÇ¥Áظí ÀÎÁõ¼­ ±â¹Ý ¼­¸íÀ» À§ÇÑ À¥ API
¿µ¹®Ç¥Áظí Web API for certificate based signing
Çѱ۳»¿ë¿ä¾à º» Ç¥ÁØÀº ±¹³»¿Ü ´Ù¾çÇÑ À¥ ȯ°æ¿¡¼­ ÇÊ¿ä·Î ÇÏ´Â ÀÎÁõ¼­ ±â¹Ý ÀüÀÚ¼­¸í ±â´ÉÀ» Ç¥ÁØÀ¸·Î Á¦°øÇÏ¿© ÇÁ·Î±×·¥ ¼³Ä¡ ¾øÀÌ µ¿ÀÏÇÑ ¹æ½ÄÀ¸·Î ´Ù¾çÇÑ Ç÷§Æû¿¡¼­ ÀüÀÚ ¼­¸í ±â´ÉÀ» Á¦°øÇÏ´Â °ÍÀ» ¸ñÀûÀ¸·Î ÇÑ´Ù.
W3C Web Cryptography API´Â ÀüÀÚ¼­¸íÀ» À§ÇØ ÇÊ¿äÇÑ ±âº»ÀûÀÎ ±â´ÉÀ» Á¦°øÇÏÁö¸¸ SOP(Same Origin Policy) Á¦¾àÀ¸·Î ÀÎÇÏ¿© »çÀÌÆ®¸¶´Ù º°µµÀÇ °³ÀÎÅ°¿Í °ø°³Å°¸¦ »ý¼ºÇؼ­ »ç¿ëÇØ¾ß ÇÑ´Ù´Â Á¡°ú °³ÀÎÀ» ½Äº°ÇÒ ¼ö ¾ø´Ù´Â ´ÜÁ¡ÀÌ ÀÖ´Ù.
º» Ç¥ÁØÀº °³ÀÎÀ» ½Äº°ÇÒ ¼ö ÀÖ´Â ÀÎÁõ¼­¸¦ ±â¹ÝÇÑ ÀüÀÚ¼­¸í ±â´ÉÀ» Á¦°øÇÏ¿© °ø°øÀ̳ª ¹Î°£ À¥¼­ºñ½ºµé¿¡¼­ °³ÀÎÀ» ÀÎÁõÇÏ´Â ±â´ÉÀ̳ª ºÎÀκÀ¼â µî ´Ù¾çÇÑ ÀüÀÚ¼­¸í ±â´ÉµéÀ» ¼Õ½±°Ô »ç¿ëÇÒ ¼ö ÀÖµµ·Ï ÇÏ´Â °ÍÀ» ¸ñÇ¥·Î ÇÑ´Ù.
À̸¦ À§Çؼ­ º» Ç¥ÁØ¿¡¼­´Â »ç¿ëÀÚ ½Ã½ºÅÛ¿¡ ÀúÀåµÈ ÀÎÁõ¼­¿Í °³ÀÎÅ°¸¦ ¿©·¯ °¡Áö ¿É¼ÇÀ» ÅëÇÏ¿© »ç¿ëÀÚ°¡ ¼±ÅÃÇÏ°í ÀüÀÚ¼­¸íÀ» ¼öÇàÇϴ ǥÁØ API¸¦ Á¦°øÇÑ´Ù.
¿µ¹®³»¿ë¿ä¾à The standard provides digital signature function on web platforms without installing any program by providing certificate-based digital signature function required in various web environments at home and abroad.
W3C Web Cryptography API provide basic functionality for digital signature but there is an issue that can¡¯t share the private key / public key among the sites due to the SOP (Same Origin Policy) constraint and identify the individual.
Therefore, the standard aims to make it easy to use various digital signature functions such as authentication and denial of service in public or private web services by providing digital signature function based on certificate that can identify individuals.
To do this, the standard provides API that signs the messages using the certificate and private key that user choose in the user system via several options.
±¹Á¦Ç¥ÁØ
°ü·ÃÆÄÀÏ TTAK.KO-10.1182.pdf TTAK.KO-10.1182.pdf            

ÀÌÀü
Áö´ÉÇü ·Îº¿À» À§ÇÑ ¾ó±¼ ÀÎ½Ä ÄÄÆ÷ÅÏÆ® API
´ÙÀ½
·Îº¿¿¡¼­ÀÇ À½¼º ÀνÄ/ÅëÈ­¸¦ À§ÇÑ ¸¶ÀÌÅ© ¼º´É Æò°¡ ôµµ