1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
|
# Description
Magma was originally designed and developed by Ladar Levison for lavabit.com. The current release is currently under heavy development, and some of the features and functions contained herein are unstable. The SMTP, POP, and IMAP protocol handlers are reasonably mature. The DMTP, DMAP and HTTP implementations (along with the bundled webmail system) are still in development. Happy hacking.
# Downloads
##### Magma
https://github.com/lavabit/magma/archive/develop.tar.gz
##### Magma Development Machine, v1.0.0
The development machine is a pre-built virtual machine with a graphical desktop and various development tools, and dependencies installed.
https://darkmail.info/downloads/dark-mail-development-machine-1.0.0.tar.gz
https://darkmail.info/downloads/dark-mail-development-machine-1.0.0.tar.gz.sha256
33808e4ed81859cb076ae879fed7ad85164a2561a1b1cd96f66f65f7e3bf7bd7
##### Magma Build Machines
For those looking for a slim virtual machine pre-configured to build and run magma, consider the following Vagrant boxes which have been created specifically for that purpose. Images have been created to support the VirtualBox, Hyper-V, VMware, and libvirt Vagrant providers. An official Docker image is on the roadmap, but for the time being you might want to consider one of the community supported images. Use the appropriate command below to download and provision a Vagrant instance.
```shell
# VMware
vagrant init lavabit/magma; vagrant up --provider vmware_desktop
# VirtualBox
vagrant init lavabit/magma; vagrant up --provider virtualbox
# libvirt
vagrant init lavabit/magma; vagrant up --provider libvirt
# Hyper-V
vagrant init lavabit/magma; vagrant up --provider hyperv
```
Images are available for alternate platforms [here](https://app.vagrantup.com/lavabit).
# Credits
- Ladar Levison
- Greg Brown
- Ivan Tolkachev
- Princess Levison
- Ryan Crites
- Sean Benson
- Stephen Watt
- Jacob Adkins
And the army of Kickstarter supporters who contributed to this project.
# Tarball Contents
```
magma/
check/
dev/
docs/
scripts/
tools/
cryptex/
mason/
pwtool/
rand/
runner/
stringer/
testde/
lib/
res/
sandbox/
src/
web/
COPYRIGHT
INSTALL
LICENSE
Makefile
README.md
```
# Installation Instructions
These instructions are targeted at systems running CentOS 6.
### Prerequisites
Install the dependencies (make sure that EPEL is enabled):
```shell
yum -y install gcc make autoconf automake binutils bison flex gcc-c++ gettext libtool make patch pkgconfig mysql-server memcached gettext-devel patch perl perl-Time-HiRes check check-devel ncurses-devel libbsd-devel zlib-devel valgrind valgrind-devel
```
**MySQL**
To start MySQL and configure the magma username run the commands below. The supplied password should be replaced with value unique to your environment. You may also want to limit the permissions of the magma database user to the database it will need to access. The global permission is only needed to setup the table schema.
```shell
chkconfig mysqld on && service mysqld start
echo "CREATE USER 'magma'@'localhost' IDENTIFIED BY 'volcano';" | mysql -u root
echo "GRANT ALL PRIVILEGES ON *.* TO 'magma'@'localhost' WITH GRANT OPTION;" | mysql -u root
```
**Memcached**
To start Memcached run the commands below.
```shell
chkconfig memcached on && service memcached start
```
### Compiling (The Short Way)
```shell
make all
```
### Compiling (The Long Way)
To link up the development and build scripts run the linkup.sh. This will create a bin folder in your home directory, if it doesn't already exist, and create symbolic links to the scripts and tools used to build, run and test magma. The commands below assume the bin directory is in your PATH. If it isn't, or you simply don't want to create the symbolic links, you can also run the shell scripts directly from their location in the dev/scripts folder. To execute the linkup.sh script:
```shell
magma/dev/scripts/linkup.sh
```
To build the dependencies and create the magmad.so library separately, run the build.lib script. Run the script without any parameters to see the possible command line options. To compile and combine all of dependencies in a single operation:
```shell
build.lib all
```
The bundled Makefile can be used to compile magma. It will detect when the dependencies haven't been compiled and run the preceeding step automatically, if necessary, as the Makefile looks for required header files in folders created by the previous step. If the Makefile has trouble finding the necessary include files, odds are its because the previous step didn't run properly. Assuming the dependencies are available, you can compile magmad and magmad.check using:
```shell
build.magma
build.check
```
To setup a sandbox database which can be used to run the unit tests, or experiment with magma, run (assuming the development userid is setup with permission to your database):
```shell
schema.reset
```
To launch the magma unit tests, or magma using the sandbox configuration, run:
```shell
check.run
magma.run
```
To download the ClamAV virus definitions into the sandbox environment, run:
```shell
freshen.clamav
```
### Deploying
To deploy magma, run the INSTALL script. Note the INSTALL script is out of date, and will need to tweaking to operate perfectly against a copy of the current magma development branch cloned directly via git. Pull requests welcome.
```shell
./INSTALL -d ~/ -u magma -p volcano -s Lavabit
```
### Development
The best way to get an issue fixed is to create a pull request with a unit test added to the check folder which reproduces the issue and checks for the expected output. In general, please be sure to run the check.vg and magma.vg scripts before creating a pull request to make sure the newly submitted code doesn't introduce a memory leak, or invalid memory operation.
# Webmail
Inside the res/pages/webmail directory is a compiled copy of the webmail code. Locate script.js file and change the magma.portalUrl = true variable to false, and it will use a set of hard coded test requests/responses. These hard coded requests, and responses are useful for checking/developing the webmail code without a running version of the magma server. Currently the files are configured to access the JSON-RPC interface using the hostname "localhost" and the HTTP port 10000. This should work using the default magma.config and magma.sandbox.config files.
The static files inside the res/pages/webmail folder are compiled using the files inside the web directory. See the web/WORKFLOW.md file for details.
|
