Oracle에선 참 여러가지 기능들을 제공하는데
제대로 알고 있는게 없으니 몸이 고생하네 ㅠㅠ

기록이라도 해놔야지..


※ 원문 링크 : 대보름님 블로그
Snapshot vs Materialized View

관리상의 이점 밖에는(?) 없다고 생각했었던 패키지였는데
성능상의 이점도 존재한단다.
(작은 규모의 시스템에서는 별로 상관 없을 듯 하지만,)

프로시져나 펑션 작성시 패키지를 사용한 적이 손으로 꼽을 정도로 적은데,
앞으로 사용하는 습관을 들이도록 해야겠다.


※ 원문 링크 : 욱짜의 Oracle 블로그
오라클 패키지의 마법을 풀어봅시다. 1편
오라클 패키지의 마법을 풀어봅시다. 2편

Network Working Group                                         B. Kaliski
Request for Comments: 5208                                           EMC
Category: Informational                                         May 2008


             
Public-Key Cryptography Standards (PKCS) #8:
Private-Key Information Syntax Specification Version 1.2

Status of This Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

IESG Note

   The IESG thanks RSA Laboratories for transferring change control to
   the IETF.  Enhancements to this specification that preserve backward
   compatibility are expected in an upcoming IETF standards track
   document.

Abstract

   This document represents a republication of PKCS #8 v1.2 from RSA
   Laboratories' Public Key Cryptography Standard (PKCS) series.  Change
   control is transferred to the IETF.  The body of this document,
   except for the security considerations section, is taken directly
   from the PKCS #8 v1.2 specification.

   This document describes a syntax for private-key information.

Table of Contents

   1. Introduction ....................................................2
   2. Definitions .....................................................2
   3. Symbols and Abbreviations .......................................2
   4. General Overview ................................................2
   5. Private-Key Information Syntax ..................................3
   6. Encrypted Private-Key Information Syntax ........................4
   7. Security Considerations .........................................4
   Appendix A. ASN.1 Syntax ...........................................5
   Informative References .............................................6









Kaliski                      Informational                      [Page 1]

 
RFC 5208    PKCS #8: Private-Key Information Syntax Standard    May 2008


.  Introduction

   This document describes a syntax for private-key information.
   Private-key information includes a private key for some public-key
   algorithm and a set of attributes.  The document also describes a
   syntax for encrypted private keys.  A password-based encryption
   algorithm (e.g., one of those described in [PKCS#5]) could be used to
   encrypt the private-key information.

   The intention of including a set of attributes is to provide a simple
   way for a user to establish trust in information such as a
   distinguished name or a top-level certification authority's public
   key.  While such trust could also be established with a digital
   signature, encryption with a secret key known only to the user is
   just as effective and possibly easier to implement.  A non-exhaustive
   list of attributes is given in [PKCS#9].

.  Definitions

   For the purposes of this document, the following definitions apply.

      AlgorithmIdentifier: A type that identifies an algorithm (by
      object identifier) and any associated parameters.  This type is
      defined in [X.509].

      ASN.1: Abstract Syntax Notation One, as defined in [X.208].

      Attribute: A type that contains an attribute type (specified by
      object identifier) and one or more attribute values.  This type is
      defined in [X.501].

      BER: Basic Encoding Rules, as defined in [X.209].

.  Symbols and Abbreviations

   No symbols or abbreviations are defined in this document.

.  General Overview

   The next two sections specify private-key information syntax and
   encrypted private-key information syntax.

   This document exports two types: PrivateKeyInfo (Section 6) and
   EncryptedPrivateKeyInfo (Section 7).







Kaliski                      Informational                      [Page 2]

 
RFC 5208    PKCS #8: Private-Key Information Syntax Standard    May 2008


.  Private-Key Information Syntax

   This section gives the syntax for private-key information.

   Private-key information shall have ASN.1 type PrivateKeyInfo:

      PrivateKeyInfo ::= SEQUENCE {
        version                   Version,
        privateKeyAlgorithm       PrivateKeyAlgorithmIdentifier,
        privateKey                PrivateKey,
        attributes           [0]  IMPLICIT Attributes OPTIONAL }

      Version ::= INTEGER

      PrivateKeyAlgorithmIdentifier ::= AlgorithmIdentifier

      PrivateKey ::= OCTET STRING

      Attributes ::= SET OF Attribute

   The fields of type PrivateKeyInfo have the following meanings:

      version is the syntax version number, for compatibility with
      future revisions of this document.  It shall be 0 for this version
      of the document.

      privateKeyAlgorithm identifies the private-key algorithm.  One
      example of a private-key algorithm is PKCS #1's rsaEncryption
      [PKCS#1].

      privateKey is an octet string whose contents are the value of the
      private key.  The interpretation of the contents is defined in the
      registration of the private-key algorithm.  For an RSA private
      key, for example, the contents are a BER encoding of a value of
      type RSAPrivateKey.

      attributes is a set of attributes.  These are the extended
      information that is encrypted along with the private-key
      information.












Kaliski                      Informational                      [Page 3]

 
RFC 5208    PKCS #8: Private-Key Information Syntax Standard    May 2008


.  Encrypted Private-Key Information Syntax

   This section gives the syntax for encrypted private-key information.

   Encrypted private-key information shall have ASN.1 type
   EncryptedPrivateKeyInfo:

      EncryptedPrivateKeyInfo ::= SEQUENCE {
        encryptionAlgorithm  EncryptionAlgorithmIdentifier,
        encryptedData        EncryptedData }

      EncryptionAlgorithmIdentifier ::= AlgorithmIdentifier

      EncryptedData ::= OCTET STRING

   The fields of type EncryptedPrivateKeyInfo have the following
   meanings:

      encryptionAlgorithm identifies the algorithm under which the
      private-key information is encrypted.  Two examples are PKCS #5's
      pbeWithMD2AndDES-CBC and pbeWithMD5AndDES-CBC [PKCS#5].

      encryptedData is the result of encrypting the private-key
      information.

   The encryption process involves the following two steps:

      1. The private-key information is BER encoded, yielding an octet
         string.

      2. The result of step 1 is encrypted with the secret key to give
         an octet string, the result of the encryption process.

.  Security Considerations

   Protection of the private-key information is vital to public-key
   cryptography.  Disclosure of the private-key material to another
   entity can lead to masquerades.  The encryption algorithm used in the
   encryption process must be as 'strong' as the key it is protecting.












Kaliski                      Informational                      [Page 4]

 
RFC 5208    PKCS #8: Private-Key Information Syntax Standard    May 2008


Appendix A.  ASN.1 Syntax

PKCS-8 {iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-8(8)
         modules(1) pkcs-8(1)}

-- $Revision: 1.5 $

-- This module has been checked for conformance with the ASN.1
-- standard by the OSS ASN.1 Tools

DEFINITIONS IMPLICIT TAGS ::=

BEGIN

-- EXPORTS All --
-- All types and values defined in this module is exported for use in
-- other ASN.1 modules.

IMPORTS

informationFramework
         FROM UsefulDefinitions {joint-iso-itu-t(2) ds(5) module(1)
                                 usefulDefinitions(0) 3}

Attribute
         FROM InformationFramework informationFramework

AlgorithmIdentifier, ALGORITHM-IDENTIFIER
         FROM PKCS-5 {iso(1) member-body(2) us(840) rsadsi(113549)
         pkcs(1) pkcs-5(5) modules(16) pkcs-5(1)};

-- Private-key information syntax

PrivateKeyInfo ::= SEQUENCE {
   version Version,
   privateKeyAlgorithm AlgorithmIdentifier {{PrivateKeyAlgorithms}},
   privateKey PrivateKey,
   attributes [0] Attributes OPTIONAL }

Version ::= INTEGER {v1(0)} (v1,...)

PrivateKey ::= OCTET STRING

Attributes ::= SET OF Attribute







Kaliski                      Informational                      [Page 5]

 
RFC 5208    PKCS #8: Private-Key Information Syntax Standard    May 2008


-- Encrypted private-key information syntax

EncryptedPrivateKeyInfo ::= SEQUENCE {
    encryptionAlgorithm AlgorithmIdentifier {{KeyEncryptionAlgorithms}},
    encryptedData EncryptedData
}

EncryptedData ::= OCTET STRING

PrivateKeyAlgorithms ALGORITHM-IDENTIFIER ::= {
     ... -- For local profiles
}

KeyEncryptionAlgorithms ALGORITHM-IDENTIFIER ::= {
     ... -- For local profiles
}

END

Informative References

   [PKCS#1]  RSA Laboratories. PKCS #1: RSA Encryption Standard. Version
             1.5, November 1993.

   [PKCS#5]  RSA Laboratories. PKCS #5: Password-Based Encryption
             Standard. Version 1.5, November 1993.

   [PKCS#9]  RSA Laboratories. PKCS #9: Selected Attribute Types.
             Version 1.1, November 1993.

   [X.208]   CCITT. Recommendation X.208: Specification of Abstract
             Syntax Notation One (ASN.1). 1988.

   [X.209]   CCITT. Recommendation X.209: Specification of Basic
             Encoding Rules for Abstract Syntax Notation One (ASN.1).
             1988.

   [X.501]   CCITT. Recommendation X.501: The Directory - Models. 1988.

   [X.509]   CCITT. Recommendation X.509: The Directory - Authentication
             Framework. 1988.










Kaliski                      Informational                      [Page 6]

 
RFC 5208    PKCS #8: Private-Key Information Syntax Standard    May 2008


Author's Addresses

   Burt Kaliski
   EMC Corporation
   176 South Street
   Hopkinton, MA  01748
   USA

   EMail: kaliski_burt@emc.com










































Kaliski                      Informational                      [Page 7]

 
RFC 5208    PKCS #8: Private-Key Information Syntax Standard    May 2008


Full Copyright Statement

   Copyright (C) The IETF Trust (2008).

   This document is subject to the rights, licenses and restrictions
   contained in BCP 78, and except as set forth therein, the authors
   retain all their rights.

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.












Kaliski                      Informational                      [Page 8]

*
Eclipse로 개발을 하다가 라이브러리의 소스 내용을 보고 싶을 때,

1. 윈도우 탐색기 열고
2. 해당 라이브러리 폴더 찾고
3. jar 파일 압축 풀고
4. class 파일 찾고
5. cmd 창 열고
6. jad 실행

하~ 번거롭다..
이런 번거로움을 해결하기 위한 플러그인이 JadClipse이다.


*
먼저 Jad를 다운로드(http://www.varaneckas.com/jad) 하여 적당한 폴더에 저장한 후
Jadclipse를 다운로드(http://sourceforge.net/projects/jadclipse)하여
사용중인 eclipse/plugins 폴더에 저장한다.

이 때, 유의해야 할 사항은 Eclipse와 JadClipse의 버전 매칭인데,
그냥 속편하게 둘 다 최신 버전으로 사용하자 -_-;;
(현재 Eclipse 3.5 + JadClipse 3.3 조합으로 잘 사용중~)


*
필요한 파일 다운로드가 끝나면 Eclipse를 실행하여
Jad가 저장된 경로를 설정하여야 한다.
Window - Preferences - Java - JadClipse 메뉴에 들어가서
Path to decompilerd에 다운로드 받은 Jad의 경로를 적어준다.

그 밑에 temp 폴더 설정과 기타 옵션들을 적당히 맞춰주면 세팅 끝~~!!


*
이제 어떤 라이브러리든 Ctrl + 클릭 한번으로 소스 내용을 볼 수 있다. ^______^

내년부터 시행되는 전자세금계산서 관련 사업을 위해
회사에서 올해 7월부터 대략 3개월간  전자세금계산서 송수신 엔진을 만들다가
드디어 오늘 인증 심사를 시작했는데...

'1호 인증'을 받아야 한다며,
아침에 30분 일찍 출근해서 새로고침 수백번 누르고,  인증 업무 시작과 동시에 '인증신청' 버튼 누르고,
미리 준비했던 시나리오대로 분노의 마우스 놀림을 선보이며  5분만에 초스피드로 인증시험을 마친 후
내심 '나의 마우스 놀림을 따라올 자는 없다. 내가 1등이야!' 라고 생각했지만..

한가지 간과한 것이 있었으니,
인증시스템을 구축한 업체인 케이엘넷 !!
자기들이 인증받는 시스템을 만들었으니 당연히 1호 인증도 그쪽으로 넘어가고..

'그래도 2등이 어디야..' 라고 애써 위로해 보지만,
1등은 이미 약속 되어 있는데 괜히 혼자 똥빠지게 삽질한 기분... -_-;;

어쨌든 인증 통과~ -_-!!





※ 이.. 이거슨.. 자랑스러운 2호 인증서!!



p.s. 절대 실장님 지시로 제목에 회사 이름을 넣은 것은 아님!!! ㅋㅋㅋ