Differences between revisions 14 and 15
Revision 14 as of 2014-01-15 23:36:27
Size: 5619
Editor: ?Mempo
Comment:
Revision 15 as of 2014-01-16 10:06:01
Size: 5605
Editor: ?Mempo
Comment:
Deletions are marked like this. Additions are marked like this.
Line 23: Line 23:
 * hardened and verifiable kernel [[ReproducibleBuildsKernel]]  * hardened and verifiable kernel [[SameKernel]]

Mempo Project - Hardened Privacy

Mempo

"⌘ Mempo project aims to provide most secure and yet comfortable out-of-the-box computer for Desktop and Server, to professionals, business, journalists, and every-day users avoiding PRISM-like spying. ⌘"

Mempo is a software project and open team of developers working with Debian and other communities and entities for above mentioned goal.

Mempo system structure:

Mempo system structure

{i} Learn more about it on Mempo webpage.

Done work:

  • ?mempo-deb fixed libpoco debian library

  • ?mempo-deb upgraded gnupg for higher max key length

  • ?mempo-deb extended ?tar for --faketime and --sort-added

Current work (2014-01) includes:

As of 2014-01 it is intended for Mempo to:

  • support and work inside of Debian project
  • in addition release distribution (remix/selection of packages) that includes:
  • - new software that is not yet accepted into Debian
  • - versions newer then in Debian
  • - release often

Mempo aims to be always Open FOSS, and put security as primary matter (e.g. at expense of usability or performance).

Project is in planning and prototyping stage, be patient :)

Contact

Variety of ways, for secure and privacy respecting communication.

Drafts

External:

Wishlist

  • Convince GCC upstream to enable security hardening flags by default
  • - or write wrapper script and set gcc_secure and alike compilers to be used for building sensitive/all packages?
    • see dpkg-buildflags, but that is useless for binaries built by users, the compiler should do hardening by default
  • - anyone has any such flags that could be added to the ?Mempo/mempo-deb package gnupg application and/or libpoco library? If yes then please form the git repo and try it and notify us here+irc.

  • - Same question for kernel flags, is it secure on this front by default? Does grsecurity turn on all the needed falgs, in addition to enabling some static check plugins?

Ideas

sl1nk various ideas (evil made, IP, MitM)

#mempo @ irc.freenode.org

<sl1nk> Meanwhile download Debian, i looked your "Threats to security and
anonymity" (https://rawgithub.com/mempo/*). I saw that you don't have a
solution for Identity Spoofing, Man-in-the-middle attack, Evil Maid attack,
phishing, DNS poisoning.
<sl1nk> That makes three categories of attacks, network, web and password
<sl1nk> There are two ways to stop the “evil maid” attack: keeping your boot
partition on a flash drive you carry at all times, or using a checksum value of
the boot sector and boot partition to detect it and change you passphrase.
<sl1nk> The only totally secure defense is to copy /boot onto a flash drive,
install GRUB on that drive, and debug this until you can boot from the flash
drive with the encrypted disk as the root filesytem.
<sl1nk> IP spoofing is a technique where a host sends out packets which claim
to be from another host. Since packet filtering makes decisions based on this
source address, IP spoofing is uses to fool packet filters. It is also used to
hide the identity of attackers using SYN attacks, Teardrop, Ping of Death and
others...
<sl1nk> The best way to protect from IP spoofing is called Source Address
Verification, and it is done by the routing code, and not firewalling at all.
<sl1nk> turning on Source Address Verification at every boot is the right
solution for you
<sl1nk> To do that, insert the following lines somewhere in your init scripts,
before any network interfaces are initialized http://pastecode.ru/8312/
<iRelay> Title: Pastecode Без названия (at pastecode.ru)
<sl1nk> If you cannot do this, you can manually insert rules to protect every
interface.
<sl1nk> MitM-Attack, uses a technique called ARP spoofing, so you need to
filtre/block it.
<sl1nk> With HTTPS or VPN for example.
<sl1nk> For Phishing and DNS poisoning is other way... ;.;

CategorySystemSecurity