[Tails-dev] english not stong -trying to set up non pubilc tor adress in tails-se pastebin
2 time attcheent does not show here is pastebin trying to set up tnon public tor address in tails https://paste.debian.net/1087288 thankyou___ 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] trying to set up non pubilc address in tails
english is not strong trying to set up non piublic tor address in tails Untitled Document 1 Description: Binary data ___ 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.
Re: [Tails-dev] problems creating usb stick for tails 1.7
Here is a update log to my previous post showing more deatils.
I followed the set up of tails on a usb drive as per the tails web site ,
however since I have a UFEI BIOS-(windows 10) then the universal usb installer
will not work
The alternative it seems is to use a software called Rufus 2.5.799
Here are the options that I think may be correct. please find log at foot of
this email.
Divce:
maas 8gb
Partition scheme and target system type:
MBR partition scheme for BIOS or UFEI
File system:
FAT32(default)
Cluster size:
4096 bytes (default)
new volume label
tails 1.7
create a bootable disk using:
ISO image
there are other options to choose from which I did not take advantage of just
yet
Here is the log which stops at the last entry for some reason:
Found USB 2.0 device 'Lexar USB Flash Drive USB Device' (05DC:A81D)
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 974, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x0031A317
Drive has a Syslinux Master Boot Record
Partition 1:
Type: FAT32 (0x0b)
Size: 7.5 GB (8015314944 bytes)
Start Sector: 2048, Boot: No, Recognized: Yes
Scanning image...
ISO analysis:
Image is an ISO9660 image
Will use '/isolinux/isolinux.cfg' for Syslinux
Detected Syslinux version: 6.03/20150326 (from '/EFI/BOOT/isolinux.bin')
Disk image analysis:
Image has an unknown Master Boot Record
Image is a bootable disk image
ISO label: 'TAILS 1.7 - 20151103'
Size: 1052835840 bytes
Has a >64 chars filename: No
Has Symlinks: No
Has a >4GB file: No
Uses Bootmgr: No
Uses EFI: Yes
Uses Grub 2: No
Uses Grub4DOS: No
Uses isolinux: Yes (6.03)
Uses KolibriOS: No
Uses ReactOS: No
Uses WinPE: No
Using image: tails-i386-1.7.iso
Computing checksum for 'C:\Users\akincana\Downloads\tails-i386-1.7.iso'...
MD5: dfbc1337a118a2fc87e7bfeaf8e8870e
SHA1: b53fb15773da339a16595c047b71ffd9a88255da
SHA256: 372ba423c46ce76393f5e8cd64136e5e9c4a806def993951fe8dbf7d93be2546
Downloading 'ldlinux.sys' from
http://rufus.akeo.ie/files/syslinux-6.03/20150326/ldlinux.sys
Unable to access file: 404
Extended version was not found, trying main version
Downloading 'ldlinux.sys' from
http://rufus.akeo.ie/files/syslinux-6.03/ldlinux.sys
File length: 68599 bytes
Successfully downloaded 'ldlinux.sys'
Downloading 'ldlinux.bss' from
http://rufus.akeo.ie/files/syslinux-6.03/20150326/ldlinux.bss
Unable to access file: 404
Extended version was not found, trying main version
Downloading 'ldlinux.bss' from
http://rufus.akeo.ie/files/syslinux-6.03/ldlinux.bss
File length: 512 bytes
Successfully downloaded 'ldlinux.bss'
Format operation started
Requesting disk access...
Opened drive \\.\PHYSICALDRIVE1 for write access
Will use 'G:' as volume mountpoint
I/O boundary checks disabled
Analyzing existing boot records...
Drive has a Syslinux Master Boot Record
Volume has an unknown Partition Boot Record
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (FAT32)...
Using cluster size: 4096 bytes
Slow format was selected
Creating file system...
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Set bootable USB partition as 0x80
Using Syslinux MBR
Found volume GUID \\?\Volume{ac77ce43-9b11-11e5-9bef-0c5b8f279a64}\
Installing Syslinux 6.03...
Using existing './rufus_files/syslinux-6.03/20150326/ldlinux.sys'
Using existing './rufus_files/syslinux-6.03/20150326/ldlinux.bss'
Successfully wrote 'ldlinux.sys'
Opened drive \\?\Volume{ac77ce43-9b11-11e5-9bef-0c5b8f279a64} for write access
Successfully wrote Syslinux boot record
Successfully remounted Volume{ac77ce43-9b11-11e5-9bef-0c5b8f279a64}\ on G:\
Copying ISO files...
Extracting files...
libcdio: Found Extension: Joliet Level 3
Image is an ISO9660 image
This image will be extracted using Joliet extensions (if present)
Extracting: G:\.disk\archive_trace (1 bytes)
Extracting: G:\.disk\info (80 bytes)
Extracting: G:\EFI\BOOT\bootia32.efi (294.5 KB)
Extracting: G:\EFI\BOOT\bootx64.efi (175.1 KB)
Extracting: G:\EFI\BOOT\bootx64.png (7.1 KB)
Extracting: G:\EFI\BOOT\cat.c32 (2.3 KB)
Extracting: G:\EFI\BOOT\chain.c32 (27.7 KB)
Extracting: G:\EFI\BOOT\cmd.c32 (1.8 KB)
Extracting: G:\EFI\BOOT\cmenu.c32 (5 KB)
Extracting: G:\EFI\BOOT\config.c32 (2.1 KB)
Extracting: G:\EFI\BOOT\cptime.c32 (5.2 KB)
Extracting: G:\EFI\BOOT\cpu.c32 (5.5 KB)
Extracting: G:\EFI\BOOT\cpuid.c32 (2.4 KB)
Extracting: G:\EFI\BOOT\cpuidtest.c32 (3.5 KB)
Extracting: G:\EFI\BOOT\debug.c32 (2.2 KB)
Extracting: G:\EFI\BOOT\dhcp.c32 (5.2 KB)
Extracting: G:\EFI\BOOT\disk.c32 (2.7 KB)
Extracting: G:\EFI\BOOT\dmi.c32 (10 KB)
Extracting: G:\EFI\BOOT\dmitest.c32 (14.1 KB)
Extracting: G:\EFI\BOOT\elf.c32 (4.2 KB)
Extracting: G:\EFI\BOOT\ethersel.c32 (3.7 KB)
Extracting: G:\EFI\BOOT\f1.txt (841 bytes)
Extracting: G:\EFI\BOOT\f10.txt (728 bytes)
[Tails-dev] problems crsting usb stick for tails 1.7
I followed the set up of tails on a usb drive as per the tails web site , however since I have a UFEI BIOS-(windows 10) then the universal usb installer will not work The alternative it seems is to use a software called Rufus 2.5.799 Here are the options that I think may be correct. please find log at foot of this email. Divce: maas 8gb Partition scheme and target system type: MBR partition scheme for BIOS or UFEI File system: FAT32(default) Cluster size: 4096 bytes (default) new volume label tails 1.7 create a bootable disk using: ISO image there are other options to choose from which I did not take advantage of just yet Here is the log which stops at the last entry for some reason: Found USB 2.0 device 'Lexar USB Flash Drive USB Device' (05DC:A81D) 1 device found Disk type: Removable, Sector Size: 512 bytes Cylinders: 974, TracksPerCylinder: 255, SectorsPerTrack: 63 Partition type: MBR, NB Partitions: 1 Disk ID: 0x001D5769 Drive has a Syslinux Master Boot Record Partition 1: Type: FAT32 LBA (0x0c) Size: 7.5 GB (8015314944 bytes) Start Sector: 2048, Boot: Yes, Recognized: Yes Found USB 2.0 device 'Lexar USB Flash Drive USB Device' (05DC:A81D) 1 device found Disk type: Removable, Sector Size: 512 bytes Cylinders: 974, TracksPerCylinder: 255, SectorsPerTrack: 63 Partition type: MBR, NB Partitions: 1 Disk ID: 0x001D5769 Drive has a Syslinux Master Boot Record Partition 1: Type: FAT32 LBA (0x0c) Size: 7.5 GB (8015314944 bytes) Start Sector: 2048, Boot: Yes, Recognized: Yes Found USB 2.0 device 'Lexar USB Flash Drive USB Device' (05DC:A81D) 1 device found Disk type: Removable, Sector Size: 512 bytes Cylinders: 974, TracksPerCylinder: 255, SectorsPerTrack: 63 Partition type: MBR, NB Partitions: 1 Disk ID: 0x001D5769 Drive has a Syslinux Master Boot Record Partition 1: Type: FAT32 LBA (0x0c) Size: 7.5 GB (8015314944 bytes) Start Sector: 2048, Boot: Yes, Recognized: Yes Scanning image... ISO analysis: Image is an ISO9660 image Will use '/isolinux/isolinux.cfg' for Syslinux Detected Syslinux version: 6.03/20150326 (from '/EFI/BOOT/isolinux.bin') Disk image analysis: Image has an unknown Master Boot Record Image is a bootable disk image ISO label: 'TAILS 1.7 - 20151103' Size: 1052835840 bytes Has a >64 chars filename: No Has Symlinks: No Has a >4GB file: No Uses Bootmgr: No Uses EFI: Yes Uses Grub 2: No Uses Grub4DOS: No Uses isolinux: Yes (6.03) Uses KolibriOS: No Uses ReactOS: No Uses WinPE: No Using image: tails-i386-1.7.iso Found USB 2.0 device 'Lexar USB Flash Drive USB Device' (05DC:A81D) 1 device found Disk type: Removable, Sector Size: 512 bytes Cylinders: 974, TracksPerCylinder: 255, SectorsPerTrack: 63 Partition type: MBR, NB Partitions: 1 Disk ID: 0x001D5769 Drive has a Syslinux Master Boot Record Partition 1: Type: FAT32 LBA (0x0c) Size: 7.5 GB (8015314944 bytes) Start Sector: 2048, Boot: Yes, Recognized: Yes Downloading 'ldlinux.sys' from http://rufus.akeo.ie/files/syslinux-6.03/20150326/ldlinux.sys Network is unavailable: Internet has not be initialized. Could not download the file - cancelling Found USB 2.0 device 'Lexar USB Flash Drive USB Device' (05DC:A81D) 1 device found Disk type: Removable, Sector Size: 512 bytes Cylinders: 974, TracksPerCylinder: 255, SectorsPerTrack: 63 Partition type: MBR, NB Partitions: 1 Disk ID: 0x001D5769 Drive has a Syslinux Master Boot Record Partition 1: Type: FAT32 LBA (0x0c) Size: 7.5 GB (8015314944 bytes) Start Sector: 2048, Boot: Yes, Recognized: Yes Found USB 2.0 device 'Lexar USB Flash Drive USB Device' (05DC:A81D) 1 device found Disk type: Removable, Sector Size: 512 bytes Cylinders: 974, TracksPerCylinder: 255, SectorsPerTrack: 63 Partition type: MBR, NB Partitions: 1 Disk ID: 0x001D5769 Drive has a Syslinux Master Boot Record Partition 1: Type: FAT32 LBA (0x0c) Size: 7.5 GB (8015314944 bytes) Start Sector: 2048, Boot: Yes, Recognized: Yes Found USB 2.0 device 'Lexar USB Flash Drive USB Device' (05DC:A81D) 1 device found Disk type: Removable, Sector Size: 512 bytes Cylinders: 974, TracksPerCylinder: 255, SectorsPerTrack: 63 Partition type: MBR, NB Partitions: 1 Disk ID: 0x001D5769 Drive has a Syslinux Master Boot Record Partition 1: Type: FAT32 LBA (0x0c) Size: 7.5 GB (8015314944 bytes) Start Sector: 2048, Boot: Yes, Recognized: Yes Found USB 2.0 device 'Lexar USB Flash Drive USB Device' (05DC:A81D) 1 device found Disk type: Removable, Sector Size: 512 bytes Cylinders: 974, TracksPerCylinder: 255, SectorsPerTrack: 63 Partition type: MBR, NB Partitions: 1 Disk ID: 0x001D5769 Drive has a Syslinux Master Boot Record Partition 1: Type: FAT32 LBA (0x0c) Size: 7.5 GB (8015314944 bytes) Start Sector: 2048, Boot: Yes, Recognized: Yes Found USB 2.0 device 'Lexar USB Flash Drive USB Device' (05DC:A81D) 1 device found Disk type: Removable, Sector Size: 512 bytes Cylinders: 974, TracksPerCylinder: 255, SectorsPerTrack: 63 Partition type:
Re: [Tails-dev] Jenkins build is back to normal : build_Tails_ISO_feature-jessie #309
PASSWORD REQUIRED? tim Gesendet:Donnerstag, 29. Januar 2015 um 16:50 Uhr Von:tails-sysadm...@boum.org An:tails-dev@boum.org Betreff:[Tails-dev] Jenkins build is back to normal : build_Tails_ISO_feature-jessie #309 See https://jenkins.tails.boum.org/job/build_Tails_ISO_feature-jessie/309/changes ___ 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: [T(A)ILS-dev] about Tails doc
I hope this idea might help if not tell what I could sothat it might come to fruition. Ask the main tor people Rodger Dingledine etc to promote tails in there web site and tell more people about it. tim Original-Nachricht Datum: Thu, 17 Feb 2011 10:19:56 +0100 Von: sajolida sajol...@pimienta.org An: tails-dev@boum.org Betreff: [T(A)ILS-dev] about Tails doc Hello people, Here are couple of notes from a discussion we had about the Tails documentation. The discussion arose when someone proposed to write an FAQ for Tails and we felt the need to think more globally about the documentation. FAQ --- Someone proposed to write a FAQ for Tails. Here are a couple of comments on that. - The FAQ could be a list of common questions but the answers should point to more complete answers in the real doc. - It could be possible to give several answers to the same question. - Some questions will surely go beyond the scope of Tails so in this case we should rather point to other references (eg. Wikipedia) than rewrite things that are already existing. - We need to write a big warning to the FAQ to say that people need to face the truth: - It is not possible to give a simple answer to a complex question - It is not possible to protect from bad uses of Tails - To summer up: the FAQ should be see as another entry point to the doc, another format to explore the same content without simplifying or duplicating what's in the real doc. Content --- Here are a couple of comments about the documentation in general. - The most important would be to be clear about what Tails doesn't protect you against : - Doesn't protect you from a targeted attack against a specific person for example in the case of confirmation attacks, if the two ends of a connection are analysed, if your connection is being monitored or analysed. - Doesn't protect you against MitM with fake certificates or if you don't pay enough attention. - It makes it clear that you are using Tor and probably Tails. It doesn't make you look like any random Internet user. - Doesn't clear the metadata of your images for you (eg. the serial number of your digital camera). - Doesn't makes your crappy passwords stronger. - Doesn't magically separte your different virtual identities if used in parallel in the same session. - Doesn't protect you from a global adversary. - We should reuse as much as possible the Tor documentation. - We should base our work on the walktrough: correct it, split it, complete it. Miscellaneous - - When writing doc on software included in Tails we could try to push it upstream, just as we're doing for code. - When should also try to push upstream the translation of docs that we produce. - For screenshots it looks alright to use a 800×600 screen resolution and reduce it afterwards by 75% (like done in the new doc on USB install). JPG should be lighter that PNG. Structure of the doc **Getting started…**, a page that would present a possible path to using Tails a bit like the beginning of the overview of Tor's documentation, see http://www.torproject.org/docs/documentation.html.en - Overview - Warning… - Install + Check your Tails' integrity + Stay tuned - Doc, FAQ, Reference manual - Found a bug? - Talk **Support**, with pointers to : - Documentation - FAQ - Found a bug? - Talk **Documentation** - Introduction → Overview - Warnings! - Installing Tails - Downloading (link) - Verify the image integrity - Installing onto a USB stick - Virtualization - Stay up to date Found a problem? → suppressed! Possible first steps forward - Integrate in the walkthough the doc about installing - Write something for the Getting started… - Write something for the Warning part Hi everybody, Here are couple of notes from a discussion we had about the Tails documentation. The discussion arose when someone proposed to write an FAQ for Tails and we felt the need to think more globally about the documentation. FAQ --- Someone proposed to write a FAQ for Tails. Here are a couple of comments on that. - The FAQ could be a list of common questions but the answers should point to more complete answers in the real doc. - It could be possible to give several answers to the same question. - Some questions will surely go beyond the scope of Tails so in this case we should rather point to other references (eg. Wikipedia) than rewrite things that are already existing. - We need to write a big warning to the FAQ to say that people need to face the truth: - It is not possible to give a simple answer to a complex question - It is not possible to protect from bad uses of Tails - To summer up: the FAQ should be see as another entry point to
Re: [T(A)ILS-dev] truecrypt-whats the alternative
My view is that you cannot say: This means that you should not create new TrueCrypt media if you intend to stay with T(A)ILS with giving some alternative. tim Original-Nachricht Datum: Wed, 26 Jan 2011 22:28:43 +0100 Von: intrigeri intrig...@boum.org An: The T\\(A\\)ILS public development discussion list tails-dev@boum.org Betreff: Re: [T(A)ILS-dev] truecrypt-whats the alternative Hi, tim smy wrote (26 Jan 2011 18:59:42 GMT) : In the future, we would like to provide proper alternatives and stop distributing TrueCrypt. This means that you should not create new TrueCrypt media if you intend to stay with T(A)ILS in the long run What are the alternatives? It would be nice to give some It depends on what part of the TrueCrypt feature set we want to provide alternatives for. I am not sure we want to, and can, provide alternatives for the whole TrueCrypt feature set. E.g.: - multi-platform encrypted volumes: IIRC dm-crypt / LUKS volumes are usable on Windows thanks to FreeOTFE; OSX? - hidden volumes: doable using plain dm-crypt / cryptsetup (no LUKS), but * multi-platform? * no proper GUI - other features? Bye, -- intrigeri intrig...@boum.org | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc | Who wants a world in which the guarantee that we shall not | die of starvation would entail the risk of dying of boredom ? ___ tails-dev mailing list tails-dev@boum.org https://boum.org/mailman/listinfo/tails-dev -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl ___ tails-dev mailing list tails-dev@boum.org https://boum.org/mailman/listinfo/tails-dev
Re: [T(A)ILS-dev] Specification and security design document
Perhaps consolidated into a single sentence would suffice tim Original-Nachricht Datum: Sun, 19 Dec 2010 10:45:57 +0100 Von: intrigeri intrig...@boum.org An: The T\\(A\\)ILS public development discussion list tails-dev@boum.org Betreff: Re: [T(A)ILS-dev] Specification and security design document Hi, tim smy wrote (15 Dec 2010 14:29:44 GMT) : Please say somewhere in the doc that each cd /version only lasts a few months. As for security reasons tor and other sotware is constanly being updated and made more secure. Thank you for this suggestion that indicates we agree on the background idea. On the other hand, since 0.4 T(A)ILS has been notifying the user in case the running version is affected by security flaws announced on our website. Knowing so, do you still think we should make it explicit in the end-user documentation? This might help reinforcing / explaining the notification system. No strong objection from my part, but I always try to avoid increasing the end-user documentation size unless really needed, based on the the longer it is, the fewer people will read it assumption. Bye, -- intrigeri intrig...@boum.org | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr-fingerprint.asc | Who wants a world in which the guarantee that we shall not | die of starvation would entail the risk of dying of boredom ? ___ tails-dev mailing list tails-dev@boum.org https://boum.org/mailman/listinfo/tails-dev -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl ___ tails-dev mailing list tails-dev@boum.org https://boum.org/mailman/listinfo/tails-dev
