<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pkgsrc/security/hydan, branch pkgsrc_2008Q2</title>
<subtitle>[no description]</subtitle>
<id>https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2008Q2</id>
<link rel='self' href='https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2008Q2'/>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/'/>
<updated>2006-03-04T21:28:51Z</updated>
<entry>
<title>Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no</title>
<updated>2006-03-04T21:28:51Z</updated>
<author>
<name>jlam</name>
<email>jlam</email>
</author>
<published>2006-03-04T21:28:51Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=48ff096d36ac47701672a4f682e7c4ebafea1eb9'/>
<id>urn:sha1:48ff096d36ac47701672a4f682e7c4ebafea1eb9</id>
<content type='text'>
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
</content>
</entry>
<entry>
<title>Create directories before installing files into them.</title>
<updated>2005-06-17T03:50:19Z</updated>
<author>
<name>jlam</name>
<email>jlam</email>
</author>
<published>2005-06-17T03:50:19Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=f7a31a0cbc0ecfc696537d41c2c5bf92b2bac14c'/>
<id>urn:sha1:f7a31a0cbc0ecfc696537d41c2c5bf92b2bac14c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add RMD160 digests.</title>
<updated>2005-02-24T12:51:41Z</updated>
<author>
<name>agc</name>
<email>agc</email>
</author>
<published>2005-02-24T12:51:41Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=2eb256146fa3337f8d832db9d8f9f3f5f1978821'/>
<id>urn:sha1:2eb256146fa3337f8d832db9d8f9f3f5f1978821</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add patches to work around compile problems for this package on</title>
<updated>2004-09-16T16:12:57Z</updated>
<author>
<name>he</name>
<email>he</email>
</author>
<published>2004-09-16T16:12:57Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=66dfb6e4a54623f5f902fd1864a423f5f80544a1'/>
<id>urn:sha1:66dfb6e4a54623f5f902fd1864a423f5f80544a1</id>
<content type='text'>
NetBSD-1.6.2_STABLE.  Gets rid of a parse error when only one
argument is given to HDN_WARN, which leaves us with "fprintf(fp, arg, )".
This may be a failure of the compiler on this platform to properly
do varargs macros, but the changes are noops and gets it building there.
</content>
</entry>
<entry>
<title>Initial import of hydan-0.13 into the Packages Collection.</title>
<updated>2004-08-13T10:26:03Z</updated>
<author>
<name>agc</name>
<email>agc</email>
</author>
<published>2004-08-13T10:26:03Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=760b77592c0896b57fefbfbc4a77d22b1ad78cfb'/>
<id>urn:sha1:760b77592c0896b57fefbfbc4a77d22b1ad78cfb</id>
<content type='text'>
Hydan steganographically conceals a message into an application.  It
exploits redundancy in the i386 instruction set by defining sets of
functionally equivalent instructions.  It then encodes information in
machine code by using the appropriate instructions from each set.

Features:
       - Application filesize remains unchanged
       - Message is blowfish encrypted with a user-supplied
	 passphrase before being embedded
       - Encoding rate: 1/110

Primary uses for Hydan:
       - Covert Communication:  embedding data into binaries creates a
	 covert channel that can be used to exchange secret messages.
       - Signing:  a program's cryptographic signature can be embedded
	 into itself.  The recipient of the binary can then verify
	 that it has not been tampered with (virus or trojan), and is
	 really from who it claims to be from.  This check can be
	 built into the OS for user transparency.
       - Watermarking:  a watermark can be embedded to uniquely
	 identify binaries for copyright purposes, or as part of a DRM
	 scheme.  Note:  this usage is not recommended as Hydan
	 implements fragile watermarks.
</content>
</entry>
</feed>
