이런건 보관해놓자.
'開發 - Computer/Interest'에 해당되는 글 16건
- 2012.05.24 User Icon
- 2011.06.14 Samsung Galaxy tab 7.0" Model names
- 2011.06.07 Installing Visual Studio 6 on Windows7
- 2011.05.23 CMLA에서 Right Issuer 인증서 발급받는 절차
- 2011.04.12 the most used preprocessor macros
- 2011.04.08 Determine whether the byte ordering is big endian or little endian
- 2011.03.31 Hexadecimal Addition in C (Simple)
- 2011.03.31 Hexadecimal Multiplication in C (simple)
- 2011.02.07 class SafeData
- 2011.01.23 개발자용 폰트 : NHN 나눔고딕 + Vera Bitstream Sans Mono (Plain/Bold)
GT-P1000 (GSM)
GT-P1010 (Wi-Fi Model)
SHW-M180W (Wi-Fi Model, Korea only)
SHW-M180S (SKT)
SHW-M180K (KTF)
SHW-M180L (LGU+)
SCH-I800 (Verizon, US Cellular)
SPH-P100 (Sprint)
SGH-I987 (AT&T)
SGH-T849 (T-Mobile)
SC-01C (NTT DoCoMo)
2. 되도록 가상 드라이브는 사용하지 말고, ISO를 임시경로에 풀어서 설치하자.
3. Setup.exe를 이용해서 설치하려면 SETUPSIZ.INI에서 vmpath를 Oracle의 java.exe로 바꿔주자.
4. 구성요소 선택할 때 OLE object viewer를 제거하고 설치하자.
5. 아래 커맨드가 가장 무난히 설치된다.
D:\vs6pro\SETUP\acmsetup.exe /t VS98PRO.STF /s D:\vs6pro /n "NAME /o "COMPANY" /k "0000000000"
11. Rights Issuer Certification
As a prerequisite for issuing a Rights Issuer certificate for the Service Provider, it is assumed that the Service Provider has already generated a Rights Issuer RSA key pair in an environment that satisfies the security requirements stipulated by the Rights Issuer Robustness Rules, another prerequisite is for the Service Provider to have fulfilled the Exhibit G of the Service Provider Agreement and to have communicated it to CMLA.. After that has been done, the first time certification and subsequent re-certifications are done as defined below.
1.
Service Provider creates
self-signed DER encoded PKCS#10 certificate request [PKCS#10], burns a DVD-R
containing the request, and sends the DVD-R to CMLA. This request SHALL be
signed using sha-1WithRSAEncryption as defined in [RFC3279].
The file naming convention is “Rights_Issuer_*_##.p10”, where * is replaced with the Service Provider’s name and ## is replaced with a two digit number. The Service Provider also submits the Rights
Issuer Certificate ordering form to CMLA via signed email and the original via
regular courier. . This ordering form will include the SHA1 hash
of the public key (PKCS#1 RSAPublicKey structure in the subjectPublicKey field)
inside the PKCS#10 request PKCS#10 file (20 bytes, encoded in hexadecimal).
2. CMLA will review and verify each request submitted. After verification, CMLA generates an invoice.
3. The Invoice is sent via email and hard copy to the Service Provider.
4. Service Provider makes payment on invoice.
5.
Upon receipt of payment on
invoice, CMLA processes order and responds.
Order processing includes the verification of the hash value provided in
the Rights Issuer Certificate ordering form to the hash value calculated over
the to be certified public key. If none of the verifications fail CMLA creates,
according to the certificate request, a Rights Issuer Certificate and delivers
it with the corresponding Rights Issuer CA Certificate to the Service Provider
in a DVD-R.
The file naming convention for the Rights Issuer Certificate is “Rights_Issuer_*_##.der”, where * is replaced with the Service Provider’s name and ## is replaced with the two digit number. The file
contains the DER encoding of the Rights Issuer Certificate
The file naming convention for the Rights Issuer CA Certificate is “Rights_Issuer_CA_Certs.der”. The file contains the DER encoding of the Rights Issuer CA
Certificate.
6. CMLA registers into certificate database necessary information such as the certificate issued by the RI CA, request data, and certificate delivery data.
CMLA Root CA Certificates are delivered to Service Providers in the same way as to the Client Adopters (check chapter 10.1 step 2 for details).
출처: CMLA Technical Specification V1.31-20101209
아 이거 퍼오는거 불법같은데 하도 답답해서 ㅠ
#ifdef _WIN32 // note the underscore: without it, it's not msdn official!
// Windows (x64 and x86)
#elif __unix__ // all unices
// Unix
#elif __posix__
// POSIX
#elif linux
// linux
#elif __APPLE__
// Mac OS, not sure if this is covered by __posix__ and/or __unix__ though...
#endif
//__MINGW32__
//__GNUC__
// _AIX32, _AIX41, _AIX43, __HOS_AIX__ (_AIX32 (the OS version >= 3.2) maybe useful)
//
ex)
when a binary is complied by GCC 4.4.5 on Ubuntu 10.10
__unix__, linux, __GNUC__ are defined.
Macros for Visual C (+ANSI macros)
Macros for gcc
Determine whether the byte ordering is big endian or little endian
開發 - Computer/Interest 2011. 4. 8. 19:07Simpler:
free(temp);
public:
SafeData();
virtual ~SafeData();
void SetByCopy( Data inData );
void SetByCopy( uint8 *d, int l );
void SetByRef( Data inData );
void SetByRef( uint8 *d, int l );
uint8 *GetData();
int GetLength();
void Clear();
protected:
uint8 *pBuffer;
int length;
};
SafeData::SafeData()
{
pBuffer = NULL;
length = 0;
};
SafeData::~SafeData()
{
Clear();
};
void SafeData::SetByCopy( Data inData )
{
Clear();
pBuffer = new uint8[inData.len];
if( pBuffer==NULL )
return;
length = inData.len;
memcpy( pBuffer, inData.d, length );
}
void SafeData::SetByCopy( uint8 *d, int l )
{
Clear();
pBuffer = new uint8[l];
if( pBuffer==NULL )
return;
length = l;
memcpy( pBuffer, d, length );
}
void SafeData::SetByRef( Data inData )
{
Clear();
pBuffer = inData.d;
length = inData.len;
}
void SafeData::SetByRef( uint8 *d, int l )
{
Clear();
pBuffer = d;
length = l;
}
uint8 *SafeData::GetData() {return pBuffer;}
int SafeData::GetLength() {return length;}
void SafeData::Clear()
{
if( pBuffer )
{
delete [] pBuffer;
pBuffer = NULL;
}
length = 0;
}