ISO7816 状态字含义 SW1 SW2

所需积分/C币:49 2015-01-06 15:59:34 3.3MB PDF
收藏 收藏
举报

ISO7816 状态字含义 SW1 SW2,包括ISO7816 CLA INS SW1 SW2,如9000,6A82,6500等。
2014/12/6 Iso 7816-4(ISo7816 part 4 section 5) Smart card standard, Basic Organizations Within each EF of linear structure, the logical positions shall be sequentially assigned when writing or appending i.e in the order of creation. Therefore the first created record is in the first logical position Within each EF of cyclic structure the logical positions shall be sequentially assigned in the opposite order, i.e, the most recently created record is in the first logical position The follow in g additional rules arc dcfined for lincar structures and for cydic structures The first occurrence shall be the record with the specified identifier and in the first logical position the last occurrence shall be the record with the specified identifier and in the last logical position When there is no current record, the next occurrence shall be equivalent to the first occurrence. The previous occurren ce shall be cquvalent to the last occurrence When there is a current record the next occurrence shall be the closest record with the specified identifier but in a greater logical position than the current record. The previous occurrence shall be the closest record with the specified identifier but in a smaller logical position than the current record The value 00 shall refer to the first last, next and previous record in the num bering sequence in dependently from the record identifier Referencing by record number- within each EF of record structure, the record numbers are unique and sequential Within each EF of linear structure, the record numbers shall be sequentially assigned when writing or appending, e in the order of creation. Therefore the first record (record number one, #1)is the first created record Within each EF of cyclic structure, the record numbers shall be sequentially assigned in the opposite order i.e. the first record (record number one, #1) is the most recently created record The following additional rule is defined for linear structures and for cyclic structures The value 00 shall refer to the current record, i. e. that record fixed by the record pointer. 5.1.4.2 Data unit referencing Within each EF of tran parent structure each data unit can be referenced by an offset (e. g in READ BINARY command) It is an unsigned integer, lim ited to either 8 or 15 bits according to an option in the respective command valued to d for the first data un it of the Ef, the offeset is incremented by 1 for every subsequent data unit. By default, L.e. If the card gives no indication the size of the date unit is one byte NOTES 1. An EF of record structure may support data unit referencing and in case it does data units may contain structural information along with data, e.g. record numbers in a linear structure Within an eF of record structure, data unit referen cin g may not provide the intended result because the storage order of the records in the ef is not kn own e.g. storage order in a cyclic structure. 5.1. 4.3 Data object referencing Each data object (as defined in 1.4.4)is headed by a tag which references it. Tags are specified in this part and other parts of ISO/IEC 7816 5.1.5 File control information The file control information(FCI) is the string of data bytes available in response to a SELECT FILE command. The file control information may be present for any file. Table 1 introduces 3 tem plates inten ded for conveying file control information when coded as BER-TLV data objects The FCp template is intended for conveying file control parameters( FCP), i.e. any BER-TLV data objects defined in The fMd template is intended for conveying file managerment data(FMD),i. e BER-TLV data objects specified in other clauses of this part or in other parts of ISo/IEC 7816(e. g application label as defined in part 5 and application expiration data as defined in part 6) The FCI template is intended for convey ing file control parameters and file management data Tag Values 62 File control parameters(FCP template) 64' File management data(FMD template) 6F File control information(FCI template) Table 1- plate relevant to FCI The 3 templates may be retrieved according to selection options of the select elle command. If the fcp or FMd option is set then the use of the corresponding template is mandatory If the fci option is set then the use of the fci template is option al Part of the file control information may addition ally be present in a working ef under control of an application and referenced under tag 87. The use of the FCP or FCI template is mandatory for the coding of file control information in File control information not coded according to this part of iso/IEC 7816 may be introduced as follows o0'or any value higher then '9F- The coding of the su bsequent string of bytes is proprietary. Tag=53-The value field of the data object consists of discretionary data not coded in TL Tag=73-The value field of the data object consists of dicretionary BER-tLv data object. Table 2-File control parameters http://www.cardwerk.com/smartcards/smartcardstandardiso7816-45basicorganizationsaspx#fchap541 3/14 2014/12/6 Iso 7816-4(ISo7816 part 4 section 5) Smart card standard, Basic Organizations Tag Value Applies to Number of data bytes in the file excluding structural in formation Transparent EFs INumber of data bytes in the file, including structural information if any Any file File descriptor byte(see table 3) Any file File descriptor byte followed by data coding byte(see table 86) 82 or 4 File descriptor byte followed by data coding byte and maximum record EFs with record ructure 83 ile identifie Any file 1 to DF name 16 DFS 85 va厂 Proprietary information Any file var. Security attributes(coding outside the scope of this part of ISO/IEC 7816)Any file Identifier of an ef containing an extension of the fcl Any file 188 to RFU 9E 9FXY Table 3-File descriptor byte b8 b7 b6 b5 b4 b3 b2 b1 Meaning File accessibility Not shareable file 01- Shareable filc 0--xxX 000 Working EF 0-001- Internal eF 0--010 0-011--- 0--100 prietary 0-10 110 of EFs 0-111- EF structure 0---000 INo information given --001 ransparent 0----010 Linear fixed, no further info 011 Linear fixed SIMPLE-TLV ---100 Linear variable. no further in 000 -101 Linear variable SIMPLE-TLV Cyclic,no further info 111 Cyclic, SIMPLE-TLV 1xXXXXXX RFU Shareable means that the file supports at least concurrent access on different logical channels 5.2 Security architecture of the card This clause describes the following features 5.2.1 Security status 5.2. 2 Security attributes 5.2.3 Security mechanisms Sccurity attributes arc compared with the sccurity status to cxccutc command and/or to acccss filc 5.2.1 Security status Security status represents the current state possibly achieved after completion of answer to reset(aTR)and possible protocol type selection(Pis)/o a single command or a sequence of commands possibly perform ing authentication procedures. he security status may also result from the com pletion of a security procedure related to the identification of the involved entities, if any by proving the knowledge of a password (e. g. using a VERIFY command by proving the knowledge of a key (e. g. using a GET CHALLANGE command followed by an EXTERNAL AUTHENTICAT by secure messaging(e. g. message authentication Three security statuses are considerd: Global security status- It may be modified by the completion of an MF-related authentication prucedure(e.g entity authentication by a password or by a key attached to the mF) File-specific security status- It may be modified by the completion of a DF-related authentication procedure (e. g. entity authentication by a password or by a key attached to the specific DF). It may be maintained recovered or lost by file selection(see 6. 10.2)this modification may be relevant only for the application to which the http://www.cardwerk.com/smartcards/smartcardstandardiso7816-45basicorganizationsaspx#fchap541 4/14 2014/12/6 Iso 7816-4(ISo7816 part 4 section 5) Smart card standard, Basic Organizations authentication procedure belongs Command-specific status- It only exists during the execution of a cammand involving authentication using secure messaging(see 1.6): such a command may leave the other security status unchanged If the concept of logical channels is applied, the file specify security status may depend on the logical channel (see 1.5.1) 5. 2. 2 Security attributes The security attributes when they exist define the allowed actions and the procedures to be performed to com plete such actions Security attibutes may be associated with each file and fix the security con ditions that shall be satisfied to allow operations on the file. The security attributes of file depend on its category(DF or EF), tional parameters in its file control information and/ or in that of its parent file(s. NOTE- Security attributes may also be associated to other objects(e.g. keys) 5.2.3 Security mechanisms This part of ISo/IEC 7816 defines the following security mechanisms Entity authentication with password- The card compares data received from the outside world with secret internal data. This mechan ism may be used for protecting the right of the user. Entity authentication with key -The entity to be authenticated has to prove the knowledge of the relevant key in an authentication procedure(.g. using a GET CHALLENGE command followed by an EXTERNAL AUTHENTICATE Data authentication -using intemal data either secret or public, the card checks redundant data recived from the outside world. Alternately using secret internal data, the card computes a data element(cryptographic checksum or digital signature)and inserts it in the data sent to the outside world this mechanism may be used for protecting the rights of a provider. Data encipherment -Using secret internal data, the card deciphers a cryptogram received in a data field Alternately using internal data, either secret or public, the card computes a cryptogram and inserts it in a data field, possibly together with other data. this mechanism may be used to provide a confidentiality service e g for key management and conditional access. In addition to the cryptogram mechanism data confidentiality can be achieved by data concealment. In this case the card computes a string of con cealing bytes and adds it by exclusive-or to data bytes received from or sent to the outside world. This mech an ism may be used for protecting privacy and for reducing the possibilities of message filtering The result of an authentication may bc logged in an intcrnal eF according to the rcqurcments of the application 5.3 APDU message structure A step in an application protocol consists of sending a command processin g it in the receiving entity and sending back the response. Therefore a spcecific response corresponds to a specific command, referred to as a command -response pair. 5.3.1 Command APDu 5.3.2 Decoding convention for command bodies 5.3.3 Response APDU An application protocol data unit (APDu) contains either a command message or a response message, sent from the interface device to the card or con In a command-response pair, the command message and the response message may contain data, thus inducing four cases which are summarised by table 4 Table 4-Data within a command-response pair Case command data Expected response data No data No data Data No data Data Data 5.3.1 Command APDU Illustrated by figure 3(see also table 6), the command apdu defined in this part of iso/IEC 7816 consists of a mandatory header of 4 bytes( CLA INS P1 P2) a conditional body of variable length Header Body CLA INS P1 P2 [Lc field] [Data field] [Le field] Figure 3-Command APDU structure The num ber of bytes present in the data field of the command apdu is denoted by lc. The maximum number of bytes expected in the data field of the response apdu is denoted by le dlength of expected data). When the le field contains only zeros, the maximum number of available data bytes is requested Figure 4 shows the 4 structures of command APDUs according to the 4 cases defined in table 4 IMAGE4 http://www.cardwerk.com/smartcards/smartcardstandardiso7816-45basicorganizationsaspx#fchap541 5/14 2014/12/6 Iso 7816-4(ISo7816 part 4 section 5) Smart card standard, Basic Organizations Figure 4- the 4 structures of command APDUs In case 1 the length Lc is null; therefore the Lc field and the data field are empty. the length Le is also nul; therefore the Le field is empty. Consequently the body is empty. In case 2, the length Lc is null; therefore the Lc field and the data field are empty. The length of Le is not nu; therefore the le field is present. Consequently the body consists of the le field In case 3, the length Lc is not nu therefore the lc field is present and the data field consists of the lc su bsequent bytes. The len gth Le is null; therefore the Le field is empty. Con sequently, the body consists of the Lc field followed by the data In case 4, the length Lc ls not nul; therefore the Lc field is present and the data field consists of the Lc subsequent bytes. The length Le is also niot null therefore the Le field is also present. Consequently the body consists of the Lc field followed by the data field and the le field 5.3.2 Decoding conventions for command bodies In case 1, the body of the command aPDu is empty. Such a command aPDU carries no length field In cases 2 3 and 4 the body of the command aPDU consists of a string of l bytes denoted by bl lo bl as illustraled by figure 5. Such a body carries 1 or 2 length fields; B1 is [part of] the first length field Command body B1 B2(L bytes) Figure 5- Not empty bady In the card capabilities(see 8.3.6), the card states that, within the command APDU, the Lc field and Le field either shall be short (one byte, defau lt value or may be extended (explicit statement) Consequently, the cases 2, 3 and 4 are either short (one byte for each length field)or extended(B1 is valued to 00 and the value of each length is coded on 2 other bytes ). Table 5 shows the decoding of the command apdus according to the four cases defined in table 4 and figure 4 and according to the possible extension of lc and le. Table 5- Decoding of the command APDUs Conditions Casel L-0 Decoding conventions for Le If the value of Le is coded in 1(or 2)byte(s)where the bits are not all null, then the value of le is equal to the value of the byte(s)which lies in the range from 1 to 255 or 65535); the null value of all the bits means the maximum value of Le:256(or55536) The first 4 cases apply to all cards. Case 1-L=0: the body is empty. No byte is used for Lc valued to O no data byte is present. No byte is used for Le valued to 0 Case 2s-L=1 No byte is used for Lc valued to u No data byte is present. B1 codes Le valued from 1 to 256 Case 3s-L-1+(B1)and (B1)!=0 B2 to Bl are the Lc bytes of the data field no byte is used for Le valued to o Case 4s-L=2+(B1)and (B1)!= 0 Bl codes Lc(=o valued from 1 to 255 B2 to Bl-1 are the Lc bytes of the data field BI codes le from 1 to 256 For cards indicat ing the extension of Lc and Le (see 8.3.8 card capabilities), the next 3 cases also apply Case 2E-L=3 and(B1)=0 No byte is used for Lc valued to O No data bytes is present The le field consists of the 3 bytes where B2 and B3 code le valued from 1 to 65536 Cae3E-L=3+(B2|B3).(B1)=0and(B2||B3)=0 The lc field consists of the first 3 bytes where B2 and B3 code Lc(=0)valued from 1 to 65536 4 and B2 are the lc bytes of the data field No byte is used for Le valued to o http://www.cardwerk.com/smartcards/smartcardstandardiso7816-45basicorganizationsaspx#fchap541 6/14 2014/12/6 Iso 7816-4(ISo7816 part 4 section 5) Smart card standard, Basic Organizations Case4-L=5+(B2|1B3),(B1)=0and(B2|B3)=0 The Lc field consists of the first 3 bytes where B2 and B3 code Lc(=0) valued from 1 to 65535 B4 to bl-2 are the lc bytes of the data field The Le field consists of the last 2 bytes bl-1 and bl which code le valued from 1 to 65536 For each transmission protocol defined in part 3 of Iso/IEC 7816 an annex attached to th is part (one per protocol) specifies the transport of the APDUs of a command-response pair for each of the previous 4 cases. 5.3.3 Response APDU Illustrated by figure 6(see also table Z), the response APDU defined in this part of Iso/IEC 7816 consists of a con ditional body of variable length a mandatory trailer of 2 bytes(sw1 SW2) Bod Trailer [Data field ]sw1 sW The number of bytes present in the data field af the response apdu is denoted by Lr The trailer codes the status of the receiving entity after processing the command-response pair NOTE- If the command is aborted, then the response APDU is a trailer coding an error condition on 2 status bytes. 5. 4 Coding conventions for command headers data fields and response trailers 5,4. 1 Class byte 5.4.2 Instruction bvte Table 5 shows the contents of the command Apdu Table 6- command ApDu contents Code[NameLLength Description CLA Class of in struction Instruction 1 Instruction code P1 Parameter Instruction parameter 1 Parameter nstruction parameter 2 Lc field Length ariable 1 or 3 Number of bytes present in the data field of the command Data variable =Lc String of bytes sent in the data field of the command Le field Length ariable l or Maximum number of bytes expected in the data field of the response to the command Table 7 shows the contents of the response APDU. Table 7-response APDU content Name Length Description Data field Data variable-Lr string of bytes received in the data field of the response sW1 Status byte 11 Command processing status sW2 Status byte 2 Command processing qualifier The subsequent clauses specify coding conventions for the class byte the instruction byte, the parameter bytes, the data field bytes and the status byte. Unless otherwise specified, in those bytes rfu bits are coded zero and rFu bytes are coded 00 5.4.1 Class byte According to table 8 used in conjunction with table 9, the class byte Cla of a command is used to indicate to what extent the command and the response comply w ith this part of ISO/IEC 7816 and when applicable (scc tablc 9), the format of sccure messaging and the logical channel numbcr. Table 8-Coding and meaning of CLA Value Meaning ox structure and coding of command and response according to this part of ISO/IEC 7816( for coding of X see table 10 to RFU 8X,Structure of com mand and response according to this part of ISO/IEC 7816. Except for 'X'(for coding, see table X 9), the coding and meaning of command and response are proprietary Ax Unless otherwise specified by the application context, structure and coding of command and response according to this part of iso/IEC 7816(for coding of X, see table 9) BO to Structure of command and response according to this part of ISO/IEC 7816 http://www.cardwerk.com/smartcards/smartcardstandardIso7816-45basicorganizations.aspx#chap54_1 7/14 2014/12/6 Iso 7816-4(ISo7816 part 4 section 5) Smart card standard, Basic Organizations Do to proprietary structure and coding of command and response FE FF Reserved for Pts Table 9-Coding and meaning of nibble x when CLA=oX,8x, 9X'or 'AX b4 b3 b2 Meaning x----Secure messaging(SM)format 0x---No SM or SM not according to 1.6 00 No sm or no sm indication 01----Proprietary SM]format 1x--secure messaging according to 1.6 10 Com mand header not authenticated 11 Command header authenticated (see 1.6.3. 1 for command header usage) Logical channel number (according to 1.5)(b2 b1=00 when logical channels are not used or when logical channel to is selected 5.4.2 Instruction byte The instruction byte INs of a command shall be coded to allow transmission with any of the protocols defined in part 3 of ISO/IEC 7816. Table 10 shows the INs codes that are consequently in valid Table 10- Invalid INs codes b8 b7 b6 b5 b4 b3 b2 b1 Meaning Odd values 0110xxxx 1001xxxx I'9X Table 11 shows the INS codes defined in this part of ISO/IEC 7816. when the value of CLa lies within the range from 00 to ' 7F, the other values of INs codes are to be assigned by ISO/IEC JTC 1 SC17 Table 11-INS codes defined in this part of ISO/IEC 7816 Value Command name clause OE'ERASE BINARY 20 VERIF 5.12 70'MANAGE CHANNEL 616 82'EXTERNAL AUTHENTICATE514 84 GET CHALLENGE 6.15 88INTERNAL AUTHENTICATE613 SELECT FILE 6.11 Bo′ READ BINARY 61 B2′ READ RECORD(s COGET RESPONSE 7.1 C2'ENVELOPE CAGET DATA 5.9 DO' WRITE BINARY D2'WRITE RECORD 5.6 D6′‖ UPDATE BINARY 53 DAPUT DATA 6,10 DC JUPDATE DATA 68 E2 PPEND RECORD 5.7 5.4.3 Parameter bytes The parameter bytes p1-P2 of a command may have any value if a parameter byte provides no further qualification, then it shall be set to 0c 5.4.4 Data field bytes Each data field shall have one of the following three structures Each TLV-coded data field shall consist of one or more tlv-coded data objects. Each non TLV-coded data field shall consist of one or more data elements, according to the specifications of the respective command. The structure of the proprietary-coded data fields is not specified in ISO/TEC 78 16 This part of ISO/IEC 7816 supports the follow ing two types of TLv-coded data objects in the data fields BER-TLV data objects SIMPLE-TLV data object http://www.cardwerk.com/smartcards/smartcardstandardiso7816-45basicorganizationsaspx#fchap541 8/14 2014/12/6 Iso 7816-4(ISo7816 part 4 section 5) Smart card standard, Basic Organizations TSO/TEC 7816 uses neither 00'nor 'FFas tag value Each BER-TLv data object shall consists of 2 or 3 consecutive fields (see ISO/EC 8825 and annex D) The tag field T consists of one or more consecutive bytes. It encodes a class, a type and a number. The length field consists of one or more consecutive bytes. It encodes an integer L If L is not null, then the value field v consists of L consecutive bytes. If L is null, then the data abject is em pty: there is no value field Each SIMPLE-TLV data object shall con sist of 2 or 3 consecutive fields. The tag field t consists of a single byte en coding only a number from 1 to 254(e.g. a record identifier). It codes no class and no construction-type The length field consists of 1 or 3 consecutive bytes. If the leading byte of the length field is in the range from 00 to FE, then the length field consists of a single byte encoding an integer L valued from 0 to 254. If the leading byte is equal to FF, then the length field continues on the two subsequent bytes which encode an integer L with a value from to 65535 If L in not null, then the value field V consists of consecutive bytes. If L is null, then the data object is empty: there s no value field The data fields of some commands(e.g. SELECT FILE ) the value fields of the SIMPLE-TLv cata object and the value field of the some prImitive BER-TLV data objects are inten ded for encoding one or more data elements. The data flelds of some other commands(e. g. record-orlented commands) and the value flelds of the other primitive BEr TLV data objects are intended for encoding one or more SIMPLE-TLV data objects. The data fields of some other commands (e.g. object-oriented commands)and the value fields of the constructed BER-TLV data abjects are intended for encoding one or more BER-TLV data objects NOTE-Before between or after TLV-coded data objects, 00'or'FF bytes without any meaning may occur(e.g. due to erase or modified TLV-coded data objects) 5.4.5 Status bytes The status bytes sw1-SW2 of a response denote the processing state in the card. Figure 7 shows the structural scheme of the values defined in this part of iso/ IEC 7816. FIGURE7 Figure 7- Structural scheme of status bytes NOTE-When SW1=63 or 65 the state of the non-volatile memory is changed. when SW1=6X except 63 and 65 the state of the non-volatile memory is unchanged Due to specifications in part 3 of ISO/IEC 7816, this part does not define the following values of sw1-sw2 60XX 67XX, 6BXX, 6DXX,6EXX,6FXX, in each case if XX=00 ·9XXX,i"xxx"!='000 The follow ing values of SW1-sW2 are defined whichever protocol is used (see examples in annex a). If a command is aborted with a response where sw1=6c, then sw2 indicates the value to be given to the short e field (exact length of requested data when re-issuing the same command before issu ing any other command If a command (wh ich may be of case 2 or 4, see table 4 and figure 4)is processed with a response where SW1=61 then Sw2 indicates the maximum value to be given to the short Le field (length uf extra data still available )in a gET RESPONSE command issued before issuing any other command E-A functionality similar to that offered by 61xX may be offered at application level by 9FXX'. However, applications use '9FXX' for other purposes Table 12 completed by tables 13 to 18 shows the general meanings of the values of Sw1-Sw2 defined in this part of ISO/IEC 7816. For each command, an appropriate clause provides more detailed meanings Tables 13 to 18 specify values of sw2 when SW1 is valued to 62,63,65,68,69and 6A. The values of sW2 not defined in tables 13 to 18 are RFU, except the values from 'Foto FF which are not defined in this part of ISO/IEC 7816 Table 12- Coding of sw1-SWw2 sw1-SW2 Meaning Normal processing INo further qualification 61XX sw2 indicates the number of response bytes still available(see text below) Warn ing processings 62XX State of non-volatile memory unchanged (further qualification in SW2, see table 13) 63XX State of non-volatile memery changed(further qualification in SW2, see table 14) Execution errors 64XXState of non-volatile memory unchanged (SW2='00, other values are RFU) 65XX State of non-volatile memory changed(further qualification in SW2, see table 15) 66XX' Reserved for security-related issues(not defined in this part of ISO/IEC 7816) Checking errors 6700 Wrong length 68×X Functions in CLA not supported(further qualification in SW2, see table 16) Command not allowed (further qualification in Sw2 see table 17) http://www.cardwerk.com/smartcards/smartcardstandardiso7816-45basicorganizationsaspx#fchap541 9/14 2014/12/6 Iso 7816-4(ISo7816 part 4 section 5) Smart card standard, Basic Organizations 6AXX Wrong parameter(s) P1-P2(further qualification in SW2, see table 18) rong parameter(s)P1-P2 6CXX Wrong length Le: SW2 indicates the exact length(see text below) 6D00 Instruction code not supported or invalid 6E00 Class not supported FoO No precise diagnasis Table 13-Coding of sw2 when SW1=62 sw2 Meaning 00' NO information given '81Part of returned data may be corrupted 82End of file/ record reached before reading Le byles 83'Selected file invalidated 84'FCI not formatted according to 1.1.5 Table 14- Coding of sw2 when SW1=63 Sw2 Meaning 00' No information given 81 File filled up by the last write I'Cx' counter provided by X(valued from 0 to 15)(exact mean ing depending an the command) Table 15-Coding of sw2 when SW1=65 SW2 Meaning 00 No information given 81'Memory failure Table 16-Coding of sw2 when Sw1=68 w2 g I, No information given 81'Logical channel not supported 82Secure messaging not support Table 17-Coding of sw2 when SW1=69 sw2 Meaning 00'No information given 81 Com mand incompatible with file structure 82 Security status not satisfied 83'Authentication method blocked 84'Referenced data invalidated 85Con ditions of use not satisfied 86 Com mand not allowed (no current EF) 87 Expected SM data objects missing 88 sM data objects incorrect Table 18-Coding of sw2 when SW1=6A sW2 Meaning 100'No information given 80 Incorrect parameters in the data field 81 Function not supported 82 File not found 83'Record not found 84Not enough memory space in the file '85 Lc in con sistent with TLV structure 86'Incorrect parameters P1-P2 87'Lc in con sistent with P1-P2 88'Referenced data not found 5.5 Logical channels http://www.cardwerk.com/smartcards/smartcardstandardiso7816-45basicorganizationsaspx#fchap541 1014

...展开详情
试读 14P ISO7816 状态字含义 SW1 SW2
立即下载 低至0.43元/次 身份认证VIP会员低至7折
一个资源只可评论一次,评论内容不能少于5个字
decipleliuxia 没多大用处,还不如去看7861-3
2017-12-29
回复
  • 分享王者

    成功上传51个资源即可获取
关注 私信 TA的资源
上传资源赚积分,得勋章
最新推荐
ISO7816 状态字含义 SW1 SW2 49积分/C币 立即下载
1/14
ISO7816 状态字含义 SW1 SW2第1页
ISO7816 状态字含义 SW1 SW2第2页
ISO7816 状态字含义 SW1 SW2第3页

试读结束, 可继续读2页

49积分/C币 立即下载 >