diff --git a/packages/0.2.3/README.mkd b/packages/0.2.3/README.mkd
new file mode 100644
index 0000000..da3b5f2
--- /dev/null
+++ b/packages/0.2.3/README.mkd
@@ -0,0 +1 @@
+**To save a file** click on the link and click 'View Raw'
diff --git a/packages/0.2.3/udevil-0.2.3-installer.sh b/packages/0.2.3/udevil-0.2.3-installer.sh
new file mode 100644
index 0000000..dea41df
Binary files /dev/null and b/packages/0.2.3/udevil-0.2.3-installer.sh differ
diff --git a/packages/0.2.3/udevil-0.2.3.SHA256.asc b/packages/0.2.3/udevil-0.2.3.SHA256.asc
new file mode 100644
index 0000000..6197397
--- /dev/null
+++ b/packages/0.2.3/udevil-0.2.3.SHA256.asc
@@ -0,0 +1,65 @@
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA256
+
+368a4e761a4bf8d9e8cff8f9cdb14764093f5e9c93e78d8a2c578a8e92fce1dd  udevil-0.2.3.tar.xz
+a18f686a10880039d30b2a1c0659d1b5b21e48ddef80444896a9e1f3b486dfc5  udevil-0.2.3-installer.sh
+64a3be2fc454837d18f4a32aee860afd70c3ced03c9928265041a53b8b210b07  udevil_0.2.3-1_all.deb
+
+#
+# This file (udevil-0.2.3.SHA256.asc) is used to authenticate download of
+# udevil version 0.2.3
+# 
+# Homepage: http://ignorantguru.github.com/udevil/
+# 
+# 
+# Why Authenticate?
+# 
+#   Verifying the authenticity of downloaded files prior to installation is
+#   important to ensure that your download is not corrupt and that no one has
+#   tampered with the server holding the files.
+#
+#
+# 1) If you don't already have IgnorantGuru's CURRENT key on your keyring:
+#
+#   gpg --keyserver keys.gnupg.net --recv-keys 0x7977070A723C6CCB696C0B0227A5AC5A01937621
+#     (if you receive an error, try again)
+#     
+#   Also visually verify that the given fingerprint matches the one shown here:
+#     http://igurublog.wordpress.com/contact-ignorantguru/
+#
+#
+# 2) Download one or more files (the first is required):
+#
+#   wget https://raw.github.com/IgnorantGuru/udevil/master/packages/0.2.3/udevil-0.2.3.SHA256.asc
+#   wget https://raw.github.com/IgnorantGuru/udevil/master/packages/0.2.3/udevil-0.2.3.tar.xz
+#   wget https://raw.github.com/IgnorantGuru/udevil/master/packages/0.2.3/udevil-0.2.3-installer.sh
+#   wget https://raw.github.com/IgnorantGuru/udevil/master/packages/0.2.3/udevil_0.2.3-1_all.deb
+#
+#
+# 3) Check signature and files:
+#
+#   gpg -d udevil-0.2.3.SHA256.asc | sha256sum --check
+#
+#   This should report a good signature and an OK for each file present:  
+#
+#     gpg: Signature made <SIGNATURE DATE> using DSA key ID 01937621    <--
+# --> udevil-0.2.3.tar.xz: OK
+# --> udevil-0.2.3-installer.sh: OK
+# --> udevil_0.2.3-1_all.deb: OK
+# --> gpg: Good signature from IgnorantGuru <EMAIL>
+#     gpg: WARNING: This key is not certified with a trusted signature!
+#     gpg:          There is no indication that the signature belongs to the owner.
+#     sha256sum: WARNING: x lines are improperly formatted
+#
+#   If "BAD signature" or the wrong key ID is reported, or if FAILED appears
+#   next to any file you plan to use, DO NOT USE the file.  A "key is not
+#   certified" warning (shown above) is normal and can be safely ignored if
+#   you visually verified the key fingerprint in step 1.
+#
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+
+iF4EAREIAAYFAk/CcGQACgkQJ6WsWgGTdiHSDgD/UM4f7u76ahS0/+twzkDwqiIq
+5Qee3mnvngZjDBw5OwYBANVHKnanGE66o53rHWOVBpi+mnjKfDpFbxt0H1PN1+Ur
+=kKkf
+-----END PGP SIGNATURE-----
diff --git a/packages/0.2.3/udevil-0.2.3.tar.xz b/packages/0.2.3/udevil-0.2.3.tar.xz
new file mode 100644
index 0000000..7c37e64
Binary files /dev/null and b/packages/0.2.3/udevil-0.2.3.tar.xz differ
diff --git a/packages/0.2.3/udevil_0.2.3-1_all.deb b/packages/0.2.3/udevil_0.2.3-1_all.deb
new file mode 100644
index 0000000..0e42f2c
Binary files /dev/null and b/packages/0.2.3/udevil_0.2.3-1_all.deb differ