[Tails-dev] Nym Network and Tails
Hi guys, As a former contributor to Tails and current contributor to the Nym network (https://nymtech.net/) I am looking into the possibility of integrating both tools. Nym provides a mixnet as an alternative to Tor for sending Internet traffic. Its Open Source and its supported by a cryptocurrency (nym). The aim of the project would be to add the Nym software to Tails so users are able to send blockchain traffic through Nym (For instance Bitcoin/Electrum traffic), while other usual traffic keeps flowing through Tor. I would like to work on this and the Nym network is open to support it. My questions would be: what do you think about it? Is Tails open to integrate and maintain such project (with Nym support)? Or let me maintain it for Tails? On the other hand if Tails is not interested on integrating and maintaining Nym, what do you thing about the feasibility of having it as a Tails derivative? How expensive would be to independently maintain such project? thanks a lot in advance, kurono ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Reproduction of Tails 3.2~rc1 successful
Hi it worked :) sha512sum tails-amd64-3.2~rc1.iso a98fe45a03bcfc688948b526b6d0d7bbd5a0c9268b8c193616a2635f998eeb5d402405754378add5d048e20ba33f59f67cf7abe5e516fa47e2dd878791e502cc tails-amd64-3.2~rc1.iso I am sending the required info. cheers, Kurono system-info.txt.bz2 Description: application/bzip signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Reproduction of Tails 3.2~alpha2 failed
Hi, > 3. run the documented diffoscope command line and share its output > again ah my bad, now it makes more sense :) I have attached the new files. On 09/10/2017 12:14 PM, kurono wrote: > Hi, > > here the link to diffoscope.html.bz2: > https://share.riseup.net/#6-l9v5guXSmMgUEhZyilXw > > I hope it helps, > kurono > diffoscope.html.bz2 Description: application/bzip diffoscope.txt.bz2 Description: application/bzip system-info.txt.bz2 Description: application/bzip signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Reproduction of Tails 3.2~alpha2 failed
Hi, here the link to diffoscope.html.bz2: https://share.riseup.net/#6-l9v5guXSmMgUEhZyilXw I hope it helps, kurono system-info.txt.bz2 Description: application/bzip signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Create random seed at installation time with Tails Installer
On 07/22/2017 03:13 PM, intrigeri wrote: > kurono: >> * The natural place to put it is in the usual seed file, inside the >> Tails file system (filesystem.squashfs). But this would imply to extract >> the image, change the file, and create a new image, which would be a lot >> of extra work. Another disadvantage is that it makes any further file >> integrity checking impossible. > > Ouch, no, let's not do that. > ok :) >> * The other option is to locate it outside of the tails file system, > > You mean in the FAT filesystem that Tails Installer creates, right? > If yes, then this seems like the best option. Another option would be > somewhere in the GPT (IIRC someone researched that). > Yes I meant the FAT filesystem. According to this: https://labs.riseup.net/code/issues/7675 The conclusion was that the GPT space is too small and "storing it on the FAT32 filesystem is certainly easier to do and less prone to accidents." >> let say the "binary" part, and link the random init script to this >> file, only if we are creating it by the installer. > > I guess checking for this file's existence is enough. > ok. >> I don't know if this last option is even possible. >> Are there already some examples of it? Maybe the syslinux, etc? > > Yes, Tails Installer already creates / renames / mangles files in the > FAT filesystem after extracting the content of the ISO filesystem. > ok great. I am still trying to get an idea of how to do this, but I think we could create a script in config/chroot_local-includes/lib/live/config/ where the early boot stuff is done. That script would copy the random-seed from the FAT filesystem, to the actual /var/lib/systemd/random-seed file. > Just curious: > > * When do we update the content of this file? AFAIK, it only has to be updated when shutting down the machine. The idea is that this file can not be equal for all the Tails installations and neither all the Tails booting processes. The idea with the installer was to solve the first problem, but maybe we also can solve the second. > * What's the plan for upgrades of the Tails USB stick? If the upgrade is done with the installer, I guess the process is the same. If the upgrade is done internally by Tails, it depends if we manage to implement a solution for the second problem. Regarding the blueprint I can use the same we already had. https://tails.boum.org/blueprint/randomness_seeding/ Or should I use other? cheers, kurono > > Cheers, > signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Create random seed at installation time with Tails Installer
Hi, I have been analyzing how to implement this: https://labs.riseup.net/code/issues/11897 and the difficult point here is where to locate the seed file on installation time. I see two options: * The natural place to put it is in the usual seed file, inside the Tails file system (filesystem.squashfs). But this would imply to extract the image, change the file, and create a new image, which would be a lot of extra work. Another disadvantage is that it makes any further file integrity checking impossible. * The other option is to locate it outside of the tails file system, let say the "binary" part, and link the random init script to this file, only if we are creating it by the installer. I don't know if this last option is even possible. Are there already some examples of it? Maybe the syslinux, etc? cheers, kurono signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Intrusion detection and behavior analysis in secure OS
Hi, I have been looking for information on Intrusion detection systems (or similar) used in secure OS like Tails and others, without much success. Aren't them been used? If that is the case what might be the reason? I could imagine that using some system to monitor "anomalous" stuff in the file system and Tor connections from withing the OS may be useful. cheers, kurono signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Improve Tails Installer UX
Hi intirgeri intrigeri: > hi, > > kurono wrote (18 May 2016 16:22:45 GMT) : >> Regarding https://labs.riseup.net/code/issues/9005 and several related >> tickets: #8861, #8860, #8859, #9006, I think its time to ask for >> feedback > > What kind of feedback do you want? (It's not obvious to me given the > cross-post.) > > Do you want code reviews, or shall we wait for the GUI design bits to > be reviewed first? Since these tickets are very related, and mostly about GUI improvement, then I would like feedback on the GUI design first. Let me now if I can make it easier (Screen shots, package installer, etc) > > Cheers, > Cheers, kurono signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Improve Tails Installer UX
Hi! Regarding https://labs.riseup.net/code/issues/9005 and several related tickets: #8861, #8860, #8859, #9006, I think its time to ask for feedback even if I know there still things to do (Like deleting *-launcher stuff). But anyway, it would be nice to add changes and fixes before it gets finished. Thanks, kurono signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [review'n'merge:1.4.1] feature/5623-Installer-should-refuse-empty-device
Hi guys, Could you please review the new iteration? Ticket: https://labs.riseup.net/code/issues/5623 Branch: https://git-tails.immerda.ch/kurono/liveusb-creator/commit/?h=feature/5623-Installer-should-refuse-empty-deviceid=ce0f3ac974a7b9f6e18071f01731e1d7edab0678 Thanks a lot! El 06/05/15 a las 17:39, kurono escribió: Hi, Could you please review the text introduced in the liveusb-creator for this ticket? https://labs.riseup.net/code/issues/5623 The modified branch is here: https://git-tails.immerda.ch/kurono/liveusb-creator/log/?h=feature/5623-Installer-should-refuse-empty-device Many thanks, kurono El 06/05/15 a las 12:17, intrigeri escribió: kurono wrote (05 May 2015 18:36:38 GMT) : Could you please review and merge? Thanks! Initial review done on the ticket. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Question regarding Tails build
I followed this manual: https://tails.boum.org/contribute/build/ Beforehand I just had upgraded from Wheezy to Jessie. At the end I had the same error described here: https://mailman.boum.org/pipermail/tails-dev/2014-July/006258.html https://labs.riseup.net/code/issues/8086 Many thanks On 05/22/15 11:24, anonym wrote: On 05/22/2015 09:43 AM, kurono wrote: Hi, If I understand it correctly, the only current way of building Tails now is manually as described here: https://tails.boum.org/contribute/build/ right? Or is there another way that works? Using the Vagrant method also works both in Debian Wheezy and Jessie (proof: I use it). Please let us know if the existing instructions for installing the dependencies do not work. Cheers! ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Question regarding Tails build
It works indeed thanks! El 22/05/15 a las 13:37, Adam Burns escribió: kurono, During the meanwhilst, you may want to take a look at this https://labs.riseup.net/code/issues/8304 to get your build working with a suitable Vagrant version. On 05/22/2015 01:31 PM, Adam Burns wrote: I've taken a very quick look at this. As the ticket #8086 suggests, it is an issue in the way Rake is used with a Monkey-patched Vagrant to build TAILS. Although the devs are keen to move to some other tech (Docker was mentioned), I'm looking at removing Rake (and thus the Vagrant library calls) from the build process if relatively easy to do so. I suspect rake was used to front end Vagrant in earlier days when perhaps Vagrant was less complete, but from quick examination, I don't think Rake is required now (nor I suspect the patching). It would simplify things enormously and bring wider Vagrant version compatibility across (including non-Debian) build OS environments. Comments on this welcome, because as I said, I've only started to scratch the surface. Regards, Adam. On 05/22/2015 12:15 PM, kurono wrote: I followed this manual: https://tails.boum.org/contribute/build/ Beforehand I just had upgraded from Wheezy to Jessie. At the end I had the same error described here: https://mailman.boum.org/pipermail/tails-dev/2014-July/006258.html https://labs.riseup.net/code/issues/8086 Many thanks On 05/22/15 11:24, anonym wrote: On 05/22/2015 09:43 AM, kurono wrote: Hi, If I understand it correctly, the only current way of building Tails now is manually as described here: https://tails.boum.org/contribute/build/ right? Or is there another way that works? Using the Vagrant method also works both in Debian Wheezy and Jessie (proof: I use it). Please let us know if the existing instructions for installing the dependencies do not work. Cheers! ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [review'n'merge:1.4.1] feature/5623-Installer-should-refuse-empty-device
Thanks!. The branch is ready for QA. El 06/05/15 a las 19:36, sajolida escribió: kurono: Hi, Could you please review the text introduced in the liveusb-creator for this ticket? https://labs.riseup.net/code/issues/5623 The modified branch is here: https://git-tails.immerda.ch/kurono/liveusb-creator/log/?h=feature/5623-Installer-should-refuse-empty-device The string in question is: « The selected device does not have a Tails installation, it is required for the upgrade process. » I'd rather say: « The destination device is not a Tails device. You can only upgrade an already installed Tails device. » We're in the process of rethinking the terminology around Tails devices and the installation process. For example we might stop saying devices at some point. But right now the strings in Tails Installer are quite a mess so let's not be too picky and stick with what's currently used in the code. Thanks for asking for reviews of your user strings. Don't hesitate to do that more often. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [review'n'merge:1.4.1] feature/5623-Installer-should-refuse-empty-device
Hi, Could you please review the text introduced in the liveusb-creator for this ticket? https://labs.riseup.net/code/issues/5623 The modified branch is here: https://git-tails.immerda.ch/kurono/liveusb-creator/log/?h=feature/5623-Installer-should-refuse-empty-device Many thanks, kurono El 06/05/15 a las 12:17, intrigeri escribió: kurono wrote (05 May 2015 18:36:38 GMT) : Could you please review and merge? Thanks! Initial review done on the ticket. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] [review'n'merge:1.4.1] feature/5623-Installer-should-refuse-empty-device
Hi, Ticket: https://labs.riseup.net/code/issues/5623 Feature branch: https://git-tails.immerda.ch/kurono/liveusb-creator/log/?h=feature/5623-Installer-should-refuse-empty-device Could you please review and merge? Thanks, kurono ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] [review'n'merge:1.4] feature/9130-tails-installer-notify-on-small-device
Hi, Ticket: https://labs.riseup.net/code/issues/9130 Feature branch: https://git-tails.immerda.ch/kurono/liveusb-creator/log/?h=feature/9130-tails-installer-notify-on-small-device Could you please review and merge? Thanks, kurono ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] [review'n'merge:1.3] bugfix/8691-Installer-lists-devices
Hi, Ticket: https://labs.riseup.net/code/issues/8691 Branch: https://git-tails.immerda.ch/kurono/liveusb-creator/log/?h=bugfix/8691-Installer-lists-devices Cheers, Kurono ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [review'n'merge:1.2.2] bugfix/6538-Tails-Installer-tries-to-install-to-too-small-devices
Ok, ready for the next iteration: https://git-tails.immerda.ch/kurono/liveusb-creator/commit/?h=bugfix/6538-Tails-Installer-tries-to-install-to-too-small-devices Cheers. El 13/01/15 16:03, intrigeri escribió: Alan wrote (12 Jan 2015 12:10:35 GMT) : I reviewed the new patch but had a few concerns with it. Please have a look at https://labs.riseup.net/code/issues/6538 Ok I have made the required changes. Thanks! I'm not sure to have time to take care of that in the next few days thought. If someone else feels like it, don't hesitate. Done, review posted on Redmine = postponed to 1.3. Cheers, ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [review'n'merge:1.2.1] bugfix/7678-Tails-Installer-crashes-on-upgrade
Hi, this branch was obviously not tested in its proposed form, as it breaks at least the Clone and upgrade feature that it's supposed to improve = postponed to Tails 1.3. See details on Redmine. Sorry for the very dummy error, I tested and it works now. Cheers, Kurono ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Bug #7880 Problems with Persistent setup on 1024x600 display
Hi, I think this ticket is duplicated https://labs.riseup.net/code/issues/7880, since there is another very similar ticket https://labs.riseup.net/code/issues/5458, that we already fixed in https://git-tails.immerda.ch/persistence-setup/commit/?id=b86aa443770c2a129b20335ec3cdac9c25fe7458 If it is a different issue please let me know. Cheers. Kurono ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [review'n'merge:1.2.1] bugfix/7678-Tails-Installer-crashes-on-upgrade
Hi, I confirm the patch fixes the issue. A tiny comment though: as @toplevels@ is only used once, so why not to write one less line: pre -toplevels = config['liveos_toplevel_files'] - for f in toplevels: +for f in config['liveos_toplevel_files']: /pre Ok the new version is in http://git.tails.boum.org/kurono/liveusb-creator/ the branch is the same bugfix/7678-Tails-Installer-crashes-on-upgrade. Cheers. ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [review'n'merge:1.2.2] bugfix/6538-Tails-Installer-tries-to-install-to-too-small-devices
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I reviewed the new patch but had a few concerns with it. Please have a look at https://labs.riseup.net/code/issues/6538 Ok I have made the required changes. Cheers. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlSsU1gACgkQ94rPTJlzoM4OqAD/cqjjUC9wALFn4EGSWNn/sylh zmESEoQOSnx9K6FuD0QA/1k3y2tiJ9YeyiHan/UlV+6IArLtGe1X9hEq9dcyrNLo =gHwa -END PGP SIGNATURE- ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [review'n'merge:1.2.2] bugfix/6538-Tails-Installer-tries-to-install-to-too-small-devices
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I am sending a patch again, since I could not access the repo (It
does not recognize my public key, maybe its my fault :/).
I think you need to initialize it by pushing something to it once,
before you can fetch from your repo.
No, I think thats not the problem, since I am not allowed to push
changes to the other repos as well. Maybe I am missing something.
I was able to do it before.
Besides, I am not sure about the smallest required size for the
USB stick, I wrote a kind of arbitrary size:
+'min_device_size': 2.8,
Should be enough technically, but then the persistence partition
would be tiny, and I've never heard of media suitable for Tails
between 2 and 4 GB (exclusive) = 4 GB should be the lower limit,
IMO (take the interpretation of GB that gives the smaller
result).
I've therefore marked this ticket as needs more dev. Soon there!
:)
Ok done, I attached a new patch.
Cheers,
Kurono
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlSJ7R0ACgkQ94rPTJlzoM6AYwD+OcLnVuRrkkTN98+ltp4V14LK
Gcso6AnYO+2J1PGS2ZgBAIdLcqv5aiiHI1T5e55DXLbiLSgQ3YWN31FRM3lT1VPS
=GHBc
-END PGP SIGNATURE-
From 5f6fa3cba6409193f50c345fdad02ad360a5371c Mon Sep 17 00:00:00 2001
From: Tails developers ta...@boum.org
Date: Thu, 11 Dec 2014 20:06:16 +0100
Subject: [PATCH]
bugfix/6538-Tails-Installer-tries-to-install-to-too-small-devices
---
liveusb/config.py | 1 +
liveusb/creator.py | 5 +
2 files changed, 6 insertions(+)
diff --git a/liveusb/config.py b/liveusb/config.py
index e3e1b40..8854acf 100644
--- a/liveusb/config.py
+++ b/liveusb/config.py
@@ -9,6 +9,7 @@ config_files = [ os.path.join('/', 'etc', 'liveusb-creator', f )
# XXX: move defaults to a proper defaults.ini file?
default_config = {
+'min_device_size': 4.0,
'main_liveos_dir': 'live',
'running_liveos_mountpoint': '/lib/live/mount/medium',
'liveos_toplevel_files': [ 'autorun.bat', 'autorun.inf', 'boot', '.disk',
diff --git a/liveusb/creator.py b/liveusb/creator.py
index 20981d6..c9c0c34 100755
--- a/liveusb/creator.py
+++ b/liveusb/creator.py
@@ -674,6 +674,11 @@ class LinuxLiveUSBCreator(LiveUSBCreator):
self.log.debug('Skipping device without size: %s' % device)
continue
+# Skip devices that are too small
+if (data['size']/10.0**9) config['min_device_size']:
+self.log.warning('Skipping too small device: %s' % device)
+continue
+
parent = dev.Get(device, 'PartitionSlave')
if parent and parent != '/':
data['parent'] = str(dbus.Interface(self._get_device(parent),
--
1.8.3.2
6538-install-to-too-small-devices.patch.sig
Description: PGP signature
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
[Tails-dev] [review'n'merge:1.2.2] bugfix/6538-Tails-Installer-tries-to-install-to-too-small-devices
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Ticket: https://labs.riseup.net/code/issues/6538
I am sending a patch again, since I could not access the repo (It does
not recognize my public key, maybe its my fault :/). Besides, I am not
sure about the smallest required size for the USB stick, I wrote a
kind of arbitrary size:
+'min_device_size': 2.8,
based on the ticket and this document:
https://tails.boum.org/contribute/design/installation/
Any feedback is very welcome.
Cheers,
kurono
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlSHVq0ACgkQ94rPTJlzoM4uJgEAhQBV8OIXo5QcTnuwjVUWFjmR
KKiGsRuetFBkoXIwqzoA/3EDjSQFy1w3Z2VNxm9oTbWIIQBPJmu02oTHnn6wUFBz
=BdSh
-END PGP SIGNATURE-
From c9bc0857003e997a1cc31bb3753e3908d880f77d Mon Sep 17 00:00:00 2001
From: Tails developers ta...@boum.org
Date: Tue, 9 Dec 2014 20:44:48 +0100
Subject: [PATCH]
bugfix/6538-Tails-Installer-tries-to-install-to-too-small-devices
---
liveusb/config.py | 1 +
liveusb/creator.py | 5 +
2 files changed, 6 insertions(+)
diff --git a/liveusb/config.py b/liveusb/config.py
index e3e1b40..cd60f20 100644
--- a/liveusb/config.py
+++ b/liveusb/config.py
@@ -9,6 +9,7 @@ config_files = [ os.path.join('/', 'etc', 'liveusb-creator', f )
# XXX: move defaults to a proper defaults.ini file?
default_config = {
+'min_device_size': 2.8,
'main_liveos_dir': 'live',
'running_liveos_mountpoint': '/lib/live/mount/medium',
'liveos_toplevel_files': [ 'autorun.bat', 'autorun.inf', 'boot', '.disk',
diff --git a/liveusb/creator.py b/liveusb/creator.py
index 20981d6..c9c0c34 100755
--- a/liveusb/creator.py
+++ b/liveusb/creator.py
@@ -674,6 +674,11 @@ class LinuxLiveUSBCreator(LiveUSBCreator):
self.log.debug('Skipping device without size: %s' % device)
continue
+# Skip devices that are too small
+if (data['size']/10.0**9) config['min_device_size']:
+self.log.warning('Skipping too small device: %s' % device)
+continue
+
parent = dev.Get(device, 'PartitionSlave')
if parent and parent != '/':
data['parent'] = str(dbus.Interface(self._get_device(parent),
--
1.8.3.2
6538-install-to-too-small-devices.patch.sig
Description: PGP signature
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
[Tails-dev] [review'n'merge:1.2.1] bugfix/7678-Tails-Installer-crashes-on-upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Ticket: https://labs.riseup.net/code/issues/7678 I don't have yet a liveusb-creator repo yet, (If I remember correctly already sent the requirement). So I am attaching the patch. Cheers, kurono -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF0EAREIAAYFAlR3hMQACgkQ94rPTJlzoM5NawD2Po5iGFlDVEeDQSJBhyyyZZL/ 2NcVcRqI1UQzIcR6vQD+PAwhiLFebeA5j2eDat23JXq15OhCnQdHkryZzhLXWlM= =TXwo -END PGP SIGNATURE- From 3d3dabddc765592c9ff01d74cd6c31dad9b01625 Mon Sep 17 00:00:00 2001 From: Tails developers ta...@boum.org Date: Thu, 27 Nov 2014 20:50:30 +0100 Subject: [PATCH] bugfix/7678-Tails-Installer-crashes-on-upgrade --- liveusb/source.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/liveusb/source.py b/liveusb/source.py index 3f93c1e..fba0843 100644 --- a/liveusb/source.py +++ b/liveusb/source.py @@ -7,6 +7,7 @@ import subprocess from stat import ST_SIZE from liveusb import _ from liveusb.releases import releases +from liveusb.config import config from liveusb.utils import (_to_unicode, _dir_size, iso_is_live_system, unicode_to_utf8, _set_liberal_perms_recursive, underlying_physical_device) @@ -85,7 +86,8 @@ class RunningLiveSystemSource(Source): self.size = _dir_size(self.path) self.dev = underlying_physical_device(self.path) def clone(self, destination): -for f in os.listdir(self.path): +toplevels = config['liveos_toplevel_files'] +for f in toplevels: src = os.path.join(self.path, f) dst = os.path.join(destination, f) if os.path.isfile(src): -- 1.8.3.2 7678-Tails-Installer-crashes-on-upgrade.patch.sig Description: PGP signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
