Downloading Byzantium: Difference between revisions
From HacDC Wiki
Haxwithaxe (talk | contribs) No edit summary |
No edit summary |
||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[http://byzantium.virtadpt.net/byzantium.pubkey Byzantium Project] public PGP key. | |||
* [http://linuxtracker.org/ | {|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0" border="1" cellpadding="5" | ||
* [http://byzantium.virtadpt.net/ byzantium.virtadpt.net] | !Version | ||
* [https://s3.amazonaws.com/byzantium- | !Codename | ||
!Released | |||
* [http:// | !Fitness* | ||
* or | !Torrent | ||
!Direct DL | |||
!PGPSign | |||
!Comments | |||
|- | |||
|0.1a | |||
|Scarab | |||
|2012/01/11 | |||
|0 | |||
| | |||
*[http://linuxtracker.org/download.php?id=fcc7607270ba48897ff865ed5361013554a659eb&f=Byzantium%20Linux%20v0.1a.torrent Linux Tracker] | |||
*[https://thepiratebay.se/torrent/7074687 The Pirate Bay] | |||
| | |||
* [http://linuxfreedom.com/byzantium Linux Freedom] | |||
* [http://byzantium.virtadpt.net/v0.1a/ byzantium.virtadpt.net] | |||
* [https://s3.amazonaws.com/byzantium/byzantium-curent.iso haxwithaxe's S3] | |||
| | |||
*[https://s3.amazonaws.com/byzantium/byzantium-current.iso.asc haxwithaxe's S3] | |||
*[http://byzantium.virtadpt.net/v0.1a/byzantium-v0.1a.iso.asc byzantium.virtadpt.net] | |||
| | |||
*current version. | |||
*EXTREME ALPHA!! | |||
*focusing on functionality ''NOT security'' | |||
|- | |||
|} | |||
`*Fitness is a score from 0 to 5 indicating the fitness of a release for use as an '''Emergency''' networking aid. Do not let this put you off downloading it to try it out or help us by finding and reporting bug and feature requests. In order to make it to a level 5 fitness we need as many people to use it as possible so we are more likely to find bugs before they end up causing trouble for people who expect our livedistro to work in an emergency. | |||
*0 = completely unfit (likely to do more harm than good in any emergency) | |||
*1 = still mostly unfit (unless you are an active developer on the project you won't likely benefit from this in an emergency) | |||
*2 = works well enough to provide basic connectivity with minimal configuration. (yeh! we're a little bit fit now! which is not to say we're fit enough to run a marathon, so don't expect to be able to do much without a regular internet connection or some sysadmin skills) | |||
*3 = in addition to qualifying for level 2 fitness this has basic intermesh services like a built in chat server, microblog server and similar user oriented services ready to run with minimal configuration. (still needs a service to tell other mesh users and end users about the services on the mesh, aka our DNSless service distribution). | |||
*4 = fully featured and works well enough to be used in friendly network conditions (you aren't in jeopardy of getting arrested/attacked for using it for things that are considered legal where you are using it) | |||
*5 = fully featured and setup with best effort secure defaults and possibly other security features (this by no means should suggest that it is safe to use in an environment where there is a government or government like entity is actively trying to suppress network connectivity by means other than denial standard network connectivity) | |||
*6 = if we find the magic sauce that can make it super hard to find users if you aren't a user and reasonably impossible to detect or decrypt traffic not sent to you, then you will see this magic number as the fitness score. Until then it is the metaphorical unicorn. It doesn't exist. | |||
You may have noticed that the fitness list doesn't ever say it's safe to use in a hostile network. That's because it won't likely ever be safe to use in a hostile network. The best we can do is to set reasonably secure defaults and policies and try to educate users on internet hygiene so they don't let people rub malware in their face if they go someplace we can't protect them. | |||
{{Template:Byzantium}} | |||
Latest revision as of 09:22, 3 April 2012
Byzantium Project public PGP key.
| Version | Codename | Released | Fitness* | Torrent | Direct DL | PGPSign | Comments |
|---|---|---|---|---|---|---|---|
| 0.1a | Scarab | 2012/01/11 | 0 |
|
`*Fitness is a score from 0 to 5 indicating the fitness of a release for use as an Emergency networking aid. Do not let this put you off downloading it to try it out or help us by finding and reporting bug and feature requests. In order to make it to a level 5 fitness we need as many people to use it as possible so we are more likely to find bugs before they end up causing trouble for people who expect our livedistro to work in an emergency.
- 0 = completely unfit (likely to do more harm than good in any emergency)
- 1 = still mostly unfit (unless you are an active developer on the project you won't likely benefit from this in an emergency)
- 2 = works well enough to provide basic connectivity with minimal configuration. (yeh! we're a little bit fit now! which is not to say we're fit enough to run a marathon, so don't expect to be able to do much without a regular internet connection or some sysadmin skills)
- 3 = in addition to qualifying for level 2 fitness this has basic intermesh services like a built in chat server, microblog server and similar user oriented services ready to run with minimal configuration. (still needs a service to tell other mesh users and end users about the services on the mesh, aka our DNSless service distribution).
- 4 = fully featured and works well enough to be used in friendly network conditions (you aren't in jeopardy of getting arrested/attacked for using it for things that are considered legal where you are using it)
- 5 = fully featured and setup with best effort secure defaults and possibly other security features (this by no means should suggest that it is safe to use in an environment where there is a government or government like entity is actively trying to suppress network connectivity by means other than denial standard network connectivity)
- 6 = if we find the magic sauce that can make it super hard to find users if you aren't a user and reasonably impossible to detect or decrypt traffic not sent to you, then you will see this magic number as the fitness score. Until then it is the metaphorical unicorn. It doesn't exist.
You may have noticed that the fitness list doesn't ever say it's safe to use in a hostile network. That's because it won't likely ever be safe to use in a hostile network. The best we can do is to set reasonably secure defaults and policies and try to educate users on internet hygiene so they don't let people rub malware in their face if they go someplace we can't protect them.