Re: [Tails-dev] [review'n'merge:1.2] feature/7916-i2p_remove_ssl_outproxy
Kill Your TV wrote (23 Sep 2014 02:47:57 GMT) : Also, maybe the design doc needs to be updated accordingly. Perhaps the updates made in feature/7725-i2p-browser are sufficient? If not I can update it further. I'll let the reviewer (anonym) judge. I was just noting that in the current state of this (feature/7916-i2p_remove_ssl_outproxy) branch, the design doc seemed to be out-of-date, so if for some reason we can merge it but not feature/7725-i2p-browser for 1.2, then we may have a (probably minor) problem. Cheers, -- intrigeri ___ 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] Add tool: Exploit Pack - Exploit Framework
Quick description: Exploit pack is an open source GPLv3 exploit framework. It includes, autopwn, graphical module editor, rat sessions, project management and more. It is 100% GPLv3, so if anyone feels like coding, he or she can checkout the code and go for it. This tool was made thinking on the end-user, it's not going to replace any other security tool on the market, but it's for sure a must-have for every security enthusiast, researcher or paranoid user. Video review: https://www.youtube.com/embed/qD9KcXM_oKA?autoplay=1 Presented in Black hat 2014 - Europe - HITB and Chaos Computer Club. Steps To Reproduce Install JAVA 8 Double click the jar file Additional Information This new version includes several new features not included in other tools of Kali linux, for example: - Graphical exploit editor - Graphical autopwn - RAT session wizard - RAT session manager - Syntax highlight - Graphical pentest manager - and more. ___ 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] Alvaro1Adriano enviou um convite para você
Alvaro1Adriano enviou um convite para você Através do Twitter você fica conectado ao que está acontecendo neste momento com as pessoas e organizações que lhe interessam. Aceitar convite https://twitter.com/i/62683167-360e-46a3-841f-53499ebd671b -- You can unsubscribe from receiving email notifications from Twitter at anytime. For general inquiries, please visit us at Twitter Support. Remover inscrição: https://twitter.com/i/o?t=1iid=9b9ec3a01ea04a52a6a9532e4cd4fb66uid=0c=VQTNdFAG9yF6FFsFV6KFfFzl3trqymFTnid=244+26 Precisa de ajuda? https://support.twitter.com___ 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] feature/5373-replace-truecrypt
Hi, On Mon, 22 Sep 2014 09:58:59 -0700 intrigeri intrig...@boum.org wrote: sajol...@pimienta.org wrote (20 Sep 2014 14:36:55 GMT) : See 6c266c5. I think you forgot to push = reassigning the ticket to you. I assigned https://labs.riseup.net/code/issues/5932 and https://labs.riseup.net/code/issues/7739 to me *but* it looks they are not actually ready to review as they depend on https://labs.riseup.net/code/issues/6052 (the documentation) which doens't look ready yet. I few comments however, as of commit 82722e8: - code looks good to me ; - the part about setting up a loopback device in the documentation is useless, it works well without it as of my tests ; - I tested feature and the warning and it works well. Please ping me when the doc is ready so that I can actually merge the branch. 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] Add tool: Exploit Pack - Exploit Framework
Juan Sacco: Quick description: Exploit pack is an open source GPLv3 exploit framework. It includes, autopwn, graphical module editor, rat sessions, project management and more. It is 100% GPLv3, so if anyone feels like coding, he or she can checkout the code and go for it. This tool was made thinking on the end-user, it's not going to replace any other security tool on the market, but it's for sure a must-have for every security enthusiast, researcher or paranoid user. Video review: https://www.youtube.com/embed/qD9KcXM_oKA?autoplay=1 Presented in Black hat 2014 - Europe - HITB and Chaos Computer Club. Steps To Reproduce Install JAVA 8 Double click the jar file Additional Information This new version includes several new features not included in other tools of Kali linux, for example: - Graphical exploit editor - Graphical autopwn - RAT session wizard - RAT session manager - Syntax highlight - Graphical pentest manager - and more. (copying from an older email of intrigeri, slightly altered) If you want to see Exploit Pack in Tails, the first step is to have it available in Debian sid, then Debian testing, and then in wheezy-backports. Once this is done, Tails users may choose to add Exploit Pack to their addional software packages [1] persistence configuration, use it, and report back about how it works in the context of Tails. Then only, we might decide to include Exploit Pack by default in Tails. [1] https://tails.boum.org/doc/first_steps/persistence/configure/#index13h2 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] Jessie session localization (#7897)
Hi, I'm giving up on https://labs.riseup.net/code/issues/7897: Fix localization of GNOME session. We have a working workaround but I can't find a proper fix after hours of research and tests. Would someone please have a look? Should we ask GNOME developers? Consider the fix good enough? Thanks by advance, 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 and merge feature/7461-persistence.conf-in-whisperback
intrigeri wrote: sajol...@pimienta.org wrote (21 Sep 2014 18:09:13 GMT) : Branch: feature/7461-persistence.conf-in-whisperback into devel Ticket: https://labs.riseup.net/code/issues/7461 This file doesn't always exist, and I'm not sure if/how WhisperBack deals with tails-debugging-info returning a non-zero exit code. So, I think I have to ask: did you test this branch *without* having persistence enabled? I think that the right long-term solution would be to have debug_file() skip non-existing files; it would be nice, but IMO that's not a must to merge this branch. I tried to add a dummy file to the list (persistence.dummy) and the output in the logs was an empty entry for that file: a header but no content. Now I tried without persistence and it does the same. -- sajolida ___ 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] feature/5373-replace-truecrypt
Hi, Alan wrote (23 Sep 2014 12:12:37 GMT) : - code looks good to me ; OK. - the part about setting up a loopback device in the documentation is useless, it works well without it as of my tests ; sajolida, do you want to update the doc accordingly, or should I? - I tested feature and the warning and it works well. Great. Please ping me when the doc is ready so that I can actually merge the branch. I suggest you ignore the documentation (that's being reviewed and discussed separatedly). Since you've reviewed and tested the code, and apparently are only blocking on the documentation for merging, I'll do the merge myself once sajolida and I complete the documentation back'n'forth. Thanks! Cheers, -- intrigeri ___ 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 and merge doc/dotfiles
intrigeri wrote: Hi, merged, thanks! While reviewing it, I noticed that we currently say the hidden configuration files in the root of your home directory, like ~/.git and ~/.bashrc; I don't think that ~/.git is a good example. Maybe ~/.gitconfig instead? Sure! Done with commit b2ed325. -- sajolida ___ 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] Redmine: possible usage clarification and improvements
BitingBird wrote: The real solution would be to allow multiple values for Categories. That's more like tag system with predefined value. Does this exist in Redmine? The notion of Category is pretty bad anyway for picky people like us... Nope, this is not possible in Redmine. However, custom fields (e.g. the one we're using for Type of work) *can* have multiple values allowed, so we could possibly create another custom field and entirely replace our usage of categories with it. That would be great. However, I couldn't find how one can fully disable the Category field, so it would be confusing. :( With this in mind, and my above note about the field of expertise (sic, IMO), I think the best we can do is to: 1. use the Category field for generic, transversal type of issues (e.g. accessibility, i18n, hardware support, persistence); 2. create a dedicated custom field called Subsystem or Affected Tool or similar. I really, really love this solution and think it would improve the situation :) I'm not 100% convinced by the taxonomy of those two fields. But I'm very happy to start with something that looks reasonable like this. I'm fine with their names (Category and Affected tool). And we will surely adjust their content later on as needed. -- sajolida ___ 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] Add tool: Exploit Pack - Exploit Framework
flapflap wrote: (copying from an older email of intrigeri, slightly altered) If you want to see Exploit Pack in Tails, the first step is to have it available in Debian sid, then Debian testing, and then in wheezy-backports. Once this is done, Tails users may choose to add Exploit Pack to their addional software packages [1] persistence configuration, use it, and report back about how it works in the context of Tails. Then only, we might decide to include Exploit Pack by default in Tails. [1] https://tails.boum.org/doc/first_steps/persistence/configure/#index13h2 Yeap: https://tails.boum.org/support/faq/#new_software -- sajolida ___ 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] feature/5373-replace-truecrypt
intrigeri wrote: Hi, Alan wrote (23 Sep 2014 12:12:37 GMT) : - code looks good to me ; OK. - the part about setting up a loopback device in the documentation is useless, it works well without it as of my tests ; Tested. I somehow convinced myself during my first tests that it was needed but I tried again and it is not. sajolida, do you want to update the doc accordingly, or should I? I did with commit 6e1c2d2. -- sajolida ___ 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] Fwd: 7.7 planning
FYI, the next Wheezy point release is scheduled just a few days *after* our 1.2 release. So, the question is: do we want to enable stable-proposed-updates in the 1.2 build, to get the package updates that will be in the Wheezy point-release, or not? ---BeginMessage--- On Tue, 2014-09-23 at 12:56 +0100, Neil McGovern wrote: On Tue, Sep 23, 2014 at 08:38:37AM +0200, Ansgar Burchardt wrote: Adam D. Barratt a...@adam-barratt.org.uk writes: We're (over)due another wheezy point release; this time, 7.7. I propose we go for one of: 11/12 October 18/19 October 25/26 October All of these are still good for me. All fine for me too. Thanks for the responses. Based on those and comments on IRC, I'm going for the 18th / 19th. I'll get a proper announcement sent out soon. Regards, Adam -- To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1411499625.18186.65.ca...@jacala.jungle.funky-badger.org ---End Message--- -- intrigeri ___ 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] feature/5373-replace-truecrypt
Hi, sajol...@pimienta.org wrote (23 Sep 2014 19:09:04 GMT) : - the part about setting up a loopback device in the documentation is useless, it works well without it as of my tests ; Tested. I somehow convinced myself during my first tests that it was needed but I tried again and it is not. sajolida, do you want to update the doc accordingly, or should I? I did with commit 6e1c2d2. Great, but now I'm in doubt: the rationale for explicitly discussing file-backed TrueCrypt volumes was that it's the most common usecase. And now, the doc only speaks of *devices*, as in Replace [device] with the name of the device. I'm not sure whether anyone will guess that they can as well pass the name of a regular file, as opposed to a device name. How about Replace [device] with the name of the device or file that contains your TrueCrypt volume, or similar? I'm reassigning to you once more, then. I reviewed the rest, and it looks good. Cheers, -- intrigeri ___ 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] Reviews'n'merges needed for 1.2 [Was: Release schedule for Tails 1.2]
Hi, anonym wrote (12 Sep 2014 15:18:55 GMT) : I'll be the release manager for Tails 1.2, scheduled to be released on 2014-10-14. Here's the preliminary release schedule: 2014-09-28 Feature freeze This is in 5 days, and we have 19 tickets waiting to be reviewed'n'merged. I'm concerned that there won't be much time, if any, for improving these branches in time if they're not perfect out-of-the-box. So, anyone willing to do part of the review'n'merge work, I guess anonym won't mind a hand. Alan, bertagaz? People who haven't the commit bit can help too! Testing the corresponding changes (either in an ISO built from the feature branch, or from an experimental nightly built ISO) would be a nice start. Looking at the code changes in Git would be very helpful too :) Cheers! -- intrigeri ___ 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.
