The NetBSD Project

CVS log for pkgsrc/security/dhbitty/Makefile

[BACK] Up to [] / pkgsrc / security / dhbitty

Request diff between arbitrary revisions

Default branch: MAIN

Revision 1.4 / (download) - annotate - [select for diffs], Fri Sep 22 07:02:57 2017 UTC (5 years, 8 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2023Q1-base, pkgsrc-2023Q1, pkgsrc-2022Q4-base, pkgsrc-2022Q4, pkgsrc-2022Q3-base, pkgsrc-2022Q3, pkgsrc-2022Q2-base, pkgsrc-2022Q2, pkgsrc-2022Q1-base, pkgsrc-2022Q1, pkgsrc-2021Q4-base, pkgsrc-2021Q4, pkgsrc-2021Q3-base, pkgsrc-2021Q3, pkgsrc-2021Q2-base, pkgsrc-2021Q2, pkgsrc-2021Q1-base, pkgsrc-2021Q1, pkgsrc-2020Q4-base, pkgsrc-2020Q4, pkgsrc-2020Q3-base, pkgsrc-2020Q3, pkgsrc-2020Q2-base, pkgsrc-2020Q2, pkgsrc-2020Q1-base, pkgsrc-2020Q1, pkgsrc-2019Q4-base, pkgsrc-2019Q4, pkgsrc-2019Q3-base, pkgsrc-2019Q3, pkgsrc-2019Q2-base, pkgsrc-2019Q2, pkgsrc-2019Q1-base, pkgsrc-2019Q1, pkgsrc-2018Q4-base, pkgsrc-2018Q4, pkgsrc-2018Q3-base, pkgsrc-2018Q3, pkgsrc-2018Q2-base, pkgsrc-2018Q2, pkgsrc-2018Q1-base, pkgsrc-2018Q1, pkgsrc-2017Q4-base, pkgsrc-2017Q4, pkgsrc-2017Q3-base, pkgsrc-2017Q3, HEAD
Changes since 1.3: +3 -3 lines
Diff to previous 1.3 (colored)

dhbitty: follow redirects

Revision 1.3 / (download) - annotate - [select for diffs], Thu Oct 9 14:06:51 2014 UTC (8 years, 8 months ago) by wiz
Branch: MAIN
CVS Tags: pkgsrc-2017Q2-base, pkgsrc-2017Q2, pkgsrc-2017Q1-base, pkgsrc-2017Q1, pkgsrc-2016Q4-base, pkgsrc-2016Q4, pkgsrc-2016Q3-base, pkgsrc-2016Q3, pkgsrc-2016Q2-base, pkgsrc-2016Q2, pkgsrc-2016Q1-base, pkgsrc-2016Q1, pkgsrc-2015Q4-base, pkgsrc-2015Q4, pkgsrc-2015Q3-base, pkgsrc-2015Q3, pkgsrc-2015Q2-base, pkgsrc-2015Q2, pkgsrc-2015Q1-base, pkgsrc-2015Q1, pkgsrc-2014Q4-base, pkgsrc-2014Q4
Changes since 1.2: +1 -3 lines
Diff to previous 1.2 (colored)

Remove pkgviews: don't set PKG_INSTALLATION_TYPES in Makefiles.

Revision 1.2 / (download) - annotate - [select for diffs], Tue Oct 23 18:16:25 2012 UTC (10 years, 7 months ago) by asau
Branch: MAIN
CVS Tags: pkgsrc-2014Q3-base, pkgsrc-2014Q3, pkgsrc-2014Q2-base, pkgsrc-2014Q2, pkgsrc-2014Q1-base, pkgsrc-2014Q1, pkgsrc-2013Q4-base, pkgsrc-2013Q4, pkgsrc-2013Q3-base, pkgsrc-2013Q3, pkgsrc-2013Q2-base, pkgsrc-2013Q2, pkgsrc-2013Q1-base, pkgsrc-2013Q1, pkgsrc-2012Q4-base, pkgsrc-2012Q4
Changes since 1.1: +1 -2 lines
Diff to previous 1.1 (colored)

Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Revision / (download) - annotate - [select for diffs] (vendor branch), Sat Aug 11 17:43:46 2012 UTC (10 years, 9 months ago) by agc
Branch: TNF
CVS Tags: pkgsrc-base, pkgsrc-2012Q3-base, pkgsrc-2012Q3
Changes since 1.1: +0 -0 lines
Diff to previous 1.1 (colored)

Import dhbitty-20120812 into the Packages Collection.

	dhbitty is a small public key encryption program written in C.  It
	uses elliptic curve Diffie-Hellman in the form of Curve25519 to
	establish a shared secret between two users, and uses that secret to
	symmetrically encrypt and authenticate messages.

	There are no private key files; only passphrases.  Never lose that
	pesky thing again.

	Both the sender and the receiver can decrypt a message.  In fact,
	there is no distinction between sender and receiver.  Both passphrases
	must be strong.

	There is no signing.  A similarly useful form of authentication occurs
	using only DH.  dhbitty attempts to be as simple as possible.  It is
	not optimized, but achieves a comfortable speed for most uses.  It
	does not use floating point numbers, or integers longer than 32 bits.
	It does not contain more algorithms than are needed.

   This is how Alice generates her public key with dhbitty:
$ dhbitty generate alice_public_key.txt
username:passphrase (this is visible!): alice:Keyfiles be damned!

   Bob will do the same thing:
$ dhbitty generate bob_public_key.txt
username:passphrase (this is visible!): bob:Bob's Spectacular Passphrase
   Alice will publish her alice_public_key.txt, and Bob will publish his bob_public_key.txt. They can now access each other's
   public keys. (But they should be careful that Eve cannot surreptitiously replace either public key with her own!)

   Alice wants to send files to Bob. She packages them into a .tar archive (or any other type of archive with timestamps), along
   with her message. Then she uses dhbitty:
$ dhbitty encrypt bob_public_key.txt files_to_bob.tar files_to_bob.tar.dhbt
username:passphrase (this is visible!): alice:Keyfiles be damned!

   Alice sends files_to_bob.tar.dhbt to Bob. Bob will use dhbitty to decrypt this archive:
$ dhbitty decrypt files_to_bob.tar.dhbt files_to_bob.tar
username:passphrase (this is visible!): bob:Bob's Spectacular Passphrase
This is the public key of file's secondary owner:

   Bob can verify that the public key dhbitty just gave him indeed is Alice's public key. He unpacks the now-decrypted archive to
   access the files Alice sent to him.

   In practice, Alice and Bob should use a system like diceware to pick passphrases, in order to be confident of their strength.
   Seven words picked using diceware is a good choice.

Revision 1.1 / (download) - annotate - [select for diffs], Sat Aug 11 17:43:46 2012 UTC (10 years, 9 months ago) by agc
Branch: MAIN

Initial revision

This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.

CVSweb <>