2010년 2월 28일 일요일

Creating a shared and static library with the gnu compiler [gcc]

Creating a shared and static library with the gnu compiler [gcc]

Here's a summary on how to create a shared and a static library with gcc. The goal is to show the basic steps. I do not want to go into the hairy details. It should be possible to use this page as a reference.
These examples were tested and run on cygwin/Windows.
The code for the library
This is the code that goes into the library. It exhibits one single function that takes two doubles and calculates their mean value and returns it.
calc_mean.c

//#include

double mean(double a, double b) {
return (a+b) / 2;
}

The header file
Of course, we need a header file.
calc_mean.h

double mean(double, double);

Creating the static library
A static library is basically a set of object files that were copied into a single file. This single file is the static library. The static file is created with the archiver (ar).
First, calc_mean.c is turned into an object file:

gcc -c calc_mean.c -o calc_mean.o

Then, the archiver (ar) is invoked to produce a static library (named libmean.a) out of the object file calc_mean.o.

ar rcs libmean.a calc_mean.o

Note: the library must start with the three letters lib and have the suffix .a.
Creating the shared library
As with static libraries, an object file is created. The -fPIC option tells gcc to create position independant code which is necessary for shared libraries. Note also, that the object file created for the static library will be overwritten. That's not bad, however, because we have a static library that already contains the needed object file.

gcc -c -fPIC calc_mean.c -o calc_mean.o

For some reason, gcc says:

cc1: warning: -fPIC ignored for target (all code is position independent)

It looks like -fPIC is not necessary on x86, but all manuals say, it's needed, so I use it too.
Now, the shared library is created

gcc -shared -Wl,-soname,libmean.so.1 -o libmean.so.1.0.1 calc_mean.o

Note: the library must start with the three letter lib.
The programm using the library
This is the program that uses the calc_mean library. Once, we will link it against the static library and once against the shared library.
main.c

#include
#include "calc_mean.h"

int main(int argc, char* argv[]) {

double v1, v2, m;
v1 = 5.2;
v2 = 7.9;

m = mean(v1, v2);

printf("The mean of %3.2f and %3.2f is %3.2f\n", v1, v2, m);

return 0;
}

Linking against static library

gcc -static main.c -L. -lmean -o statically_linked

Note: the first three letters (the lib) must not be specified, as well as the suffix (.a)
Linking against shared library

gcc main.c -o dynamically_linked -L. -lmean

Note: the first three letters (the lib) must not be specified, as well as the suffix (.so)
Executing the dynamically linked programm

LD_LIBRARY_PATH=.
./dynamically_linked

Thanks
Thanks to Donn Morrison who helped me improve this page.

2010년 2월 1일 월요일

How to use openssl

Encryption
ex) openssl enc -des3 -salt -k 1234 -in filename -out filename.des3

Decryption
ex) openssl des3 -d -in filename -out filename

Encrypting and decrypting files from command line with gpg

Your Key

Private and public keys are at the heart of gpg’s encryption and decryption processes. The best first step is to create a key pair for yourself.

  1. Generate a private key.

    gpg --gen-key

    You’ll have to answer a bunch of questions:

    1. What kind and size of key you want; the defaults are probably good enough.

    2. How long the key should be valid. You can safely choose a non-expiring key for your own use. If you plan to use a key for public signing, you might want to consider a yearly expiration.

    3. Your real name and e-mail address; these are necessary for identifying your key in a larger set of keys.

    4. A comment for your key, perhaps to distinquish a key used for special tasks like signing software releases. The comment can be empty.

    5. A passphrase. Whatever you do, don’t forget it! Your key, and all your encrypted files, will be useless if you do.

  2. Generate an ASCII public version of your private key.

    gpg --armor --output pubkey.txt --export 'Your Name'

    You can freely distribute this file by sending it to friends, posting it on your web site, or whatever.

  3. You might also want to register your key with public keyservers so that others can retrieve your key without having to contact you directly.

    gpg --send-keys 'Your Name' --keyserver hkp://subkeys.pgp.net

Encrypting a file for personal use

Encrypting files for your personal use is quite easy.

  1. Encrypt a file called foo.txt. The argument to the --recipient option should be the all or part of the name you used when generating your private key.

    # the long version
    gpg --encrypt --recipient 'Your Name' foo.txt

    # using terse options
    gpg -e -r Name foo.txt

    The encrypted version of the file will by default be named foo.txt.gpg. You can modify that behavior using the --output (-o) option.

  2. Decrypt the encrypted file. You’ll be asked to provide the passphrase you used when generating your private key. If you don’t use the --output option, the contents of the encrypted file will be sent to standard output.

    gpg --output foo.txt --decrypt foo.txt.gpg

If foo.txt is a file that you think you’ll want to edit and/or view on a regular basis, you might consider using make to reduce the amount of typing you’ll have to do. Here’s an example Makefile (to use it, you’ll need to make sure that the leading whitespace in the targets is composed of Tabs, not ordinary spaces).

# example Makefile for viewing/editing an encrypted file
GPGID = you@your.address
FILEPLAIN = foo.txt
FILECRYPT = $(FILEPLAIN).gpg

GPG = gpg
RM = /bin/rm -i
VI = vim

all:
@echo ""
@echo "usage:"
@echo ""
@echo "* make view -- to see $(FILEPLAIN)"
@echo "* make edit -- to edit $(FILEPLAIN)"
@echo ""

edit:
@umask 0077;\
$(GPG) --output $(FILEPLAIN) --decrypt $(FILECRYPT)
@$(VI) $(FILEPLAIN)
@umask 0077;\
$(GPG) --encrypt --recipient $(GPGID) $(FILEPLAIN)
@$(RM) $(FILEPLAIN)

view:
@umask 0077; $(GPG) --decrypt $(FILECRYPT) | less

Encrypting a file for someone else

The really cool thing about GnuPG is that you can safely encrypt files for others using publicly available keys.

  1. Import your friend’s key, which you might have received via e-mail or on a floppy. If the file is named key.asc, then just use the --import option to add it to your keyring:

    gpg --import key.asc

    That’s it! You can verify the import using the --list-keys option.

  2. Alternatively, you might be able to find your friend’s key on a public keyserver.

    gpg --search-keys 'myfriend@his.isp.com' \
    --keyserver hkp://subkeys.pgp.net

    Here’s what a session looks like when someone searches for my key.

    $ gpg --search-keys heinlein@madboa
    gpgkeys: WARNING: this is an *experimental* HKP interface!
    gpgkeys: searching for "heinlein@madboa" from HKP server
    subkeys.pgp.net
    Keys 1-5 of 5 for "heinlein@madboa"
    (1) Paul Heinlein
    1024 bit DSA key 8F54CA35, created 2000-11-10
    (2) Paul Heinlein
    1024 bit DSA key 8F54CA35, created 2000-11-10
    (3) Paul Heinlein
    1024 bit DSA key 8F54CA35, created 2000-11-10
    (4) Paul Heinlein
    1024 bit DSA key 8F54CA35, created 2000-11-10
    (5) [user attribute packet]
    1024 bit DSA key 8F54CA35, created 2000-11-10
    Enter number(s), N)ext, or Q)uit > 1
    gpgkeys: WARNING: this is an *experimental* HKP interface!
    gpg: key 8F54CA35: public key "Paul Heinlein "
    imported
    gpg: Total number processed: 1
    gpg: imported: 1

    You’ll note that my key has four different e-mail addresses attached to it. That’s perfectly normal.

  3. Once you’ve got the other person’s public key, encrypt a file using it.

    gpg --encrypt --recipient 'myfriend@his.isp.net' foo.txt

    You’ll end up with a file called foo.txt.gpg that you can send as an e-mail attachment or make available for downloading via ftp or the web.

Decrypting a file from someone else

If someone sends you an encrypted file, the file has typically been encrypted using your public key. Decrypting it is no different than decrypting a file you’ve encrypted for your own use.

gpg --output foo.txt --decrypt foo.txt.gpg

Basic Key Management

After a while, you will probably have several keys in your ring. It’s easy to list them all:

gpg --list-keys

Should you lose trust in or contact with a person with a key in your ring, you’ll want to delete it:

gpg --delete-key 'myfriend@his.isp.com'

sublime close without confirmation

  Close without confirm   Yes, you can just write a plugin to set the view as scratch and close it. Then create a keybinding for that c...