[05:02] <adjen> hi
[05:02] <adjen> i discover a new great exploit to get root take a look  http://ro0t.dyndns-server.com/
[08:21] <lordievader> Good morning
[10:44] <who_me> hello, is there any chance that the fox for kde bug #298895 will make it on the next respin of the LTS images ?
[10:44] <who_me> s/fox/fix
[10:48] <lordievader> who_me: Perhaps this question is better suited for #kubuntu-devel
[10:50] <who_me> lordievader, thanks. I shall poke in there :)
[10:53] <who_me> Is the KDE version that gets launched from the Live DVD/CD the same version with the one that gets installed in the case of LTS releases ?
[10:53] <lordievader> who_me: What do you mean exactly?
[10:55] <who_me> in the case of 12.04.2 there are surely some fixes that were made to KDE since the initial 12.04 launch. Those fixes are probably included in the packages that are installed, but is that updated code also running when the live session is launched ?
[10:56] <lordievader> who_me: Yes, 12.04.2 has KDE SC 4.10 (or so I believe).
[10:57] <who_me> hmm, when I started the live session it still launched KDE 4.8.5
[10:59] <lordievader> who_me: Have to say I'm not entirely sure of the version number, but since 12.04.2 also has all of the blue stuff KDE SC 4.10 has I'd guess it comes with 4.10.
[10:59] <invariant> who_me, you need to have -updates enabled.
[11:00] <who_me> problem is that with the particular setup I simply can't get online, so no updates
[11:09] <_droid> hi people, i have a network attached 4in1 printer a canon iR2018i. Then installation of the printer worked fine but how do I add the scanner?
[12:23] <reindeer> Q: im trying to create/mount/verify an encrypted dvd backup image, but have no luck so far. When mounting it using a loop device errors are either "mount: stolen loop=/dev/loop0" or ioctl: LOOP_SET_STATUS: No such file or directory. Whats going on?
[12:23] <reindeer> the system is 12.04
[12:28] <reindeer> i am trying to follow this tutorial at part 3.3: http://loop-aes.sourceforge.net/aespipe.README
[12:33] <reindeer> i think the problem is somehow related to loop-aes-utils package, that according to that guide needs to be version 3.0a or later, but what is available for 12.04, through apt-get seems to be 2.16.2  http://packages.ubuntu.com/fi/precise/loop-aes-utils
[12:40] <Walex> reindeer: the utils versions does not matter a lot.
[12:40] <reindeer> Walex: hmm yes seems that the utils is 2.16 even at PPA
[12:41] <Walex> reindeer: but try doing it in two steps: first 'losetup' and then 'mount' without '-o loop'
[12:49] <BluesKaj> Happy Easter all
[13:11] <lordievader> Good afternoon
[13:20] <reindeer> Walex: i tried, but still got error
[13:20] <reindeer> ioctl: LOOP_MULTI_KEY_SETUP_V3: Invalid argument
[13:21] <Walex> reindeer: then are you sure that the 'loop' module loaded in the kernel is the loop-AES one rather than the original one?
[13:21] <reindeer> i'll checl
[13:21] <reindeer> check
[13:24] <reindeer> i did  rmmod/modprobe cryptoloop but still same error on mounting
[13:24] <reindeer> i dont get how can this be this difficult, should be trivial.. :-/
[13:25] <Walex> reindeer: what makes you think that 'cryptoloop' is the module for loop-AES?
[13:26] <Walex> reindeer: there are three different blockdevice encryption modules and systems in Linux, and perhaps you should be clear as to which one you want to use.
[13:27] <Walex> reindeer: they are loop-AES, DM Crypt and Cryptoloop.
[13:28] <Walex> reindeer: of these for various reasons the best is indeed loop-AES BTW, so you have made a good choice.
[13:30] <reindeer> thanks, well, im still quite new to this, trying to study and learn crypto usage so yes, things are still quite mixed up in my head, but id like to use one that basically works on my system. :)
[13:30] <reindeer> and that loopaes quide seemd good an efficent so i liked that one, glad its a good choice
[13:30] <reindeer> or actually that was aespipe that im referring to
[13:31] <reindeer> ..see! :)
[13:31] <Walex> reindeer: 'aespipe' is a user level command that uses the same encryption that 'loop-AES' in the kernel uses.
[13:32] <reindeer> ok, and they are both maintained by Jari Ruusu? :)
[13:32] <Walex> reindeer: so don't use the 'cryptoloop' module. Now confusingly the loop-AES module is called 'loop' like the original unencrypted 'loop' module.
[13:32] <reindeer> ok
[13:33] <Walex> reindeer: yes, both 'aespipe' and 'loop-AES' are maintained by Jari Ruusu. The main purpose of 'aespipe' is to allow decrypting or changing encryption keys of loop-AES block devices.
[13:34] <reindeer> so ill stick with aespipe and loop-AES, is the latter is in the kernel, i bet there is even speedup, due to CPU instruction support on these lates CPU's
[13:34] <reindeer> if*
[13:35] <Walex> reindeer: yes, it is particularly efficient.
[13:36] <reindeer> so how should i proceed then
[13:36] <Walex> reindeer: especially with a 64 bit kernel as the 64 bit AMD instruction set is much better for computing AES encryption (at least 128 bit AES encryption).
[13:36] <reindeer> copy that
[13:36] <Walex> reindeer: well, you have to figure out where you have installed the 'loop.ko' that is actually the loop-AES version of it.
[13:37] <Walex> reindeer: then you need to 'rmmod loop' and 'insmod' that 'loop.ko' file.
[13:37] <reindeer> hmm, if im running this basic 12.04 system, its not in some specific place?
[13:38] <Walex> because the kernel is telling you that the current 'loop' module does not have the LOOP_MULTI_KEY_SETUP_V3 ioctl, which is only implemented by 'loop-aes'
[13:39] <reindeer> hmm $locate loop.ko only returns cryptoloop.ko locations
[13:40] <Walex> reindeer: the basic 12.04 system does not have the 'loop-AES' module, you need to compile it from the relevant source package. Looking
[13:40] <reindeer> oh..well thats news! no wonder im getting nowhere yet :)
[13:40] <Walex> reindeer: if you do 'modinfo cryptoloop' it will tell you something...
[13:42] <Walex> reindeer: I was sure there was a ready-made kernel source package for 'loop-AES', but perhaps you need to compile from original sources.
[13:42] <reindeer> oh and 'locate' also returned ".. drivers/target/loopback/tcm_loop.ko" which is the basic loop back device right?
[13:42] <Walex> reindeer: no, another one,
[13:42] <reindeer> ok..
[13:43] <Walex> reindeer: uhm I am starting to remember something disappointing.
[13:45] <Walex> reindeer: ah yes. Because of their wickedness :-) Ubuntu have hard-coded the non-encrypting 'loop' module into the kernel. So I created a patch that renames the 'loop-AES' module from 'loop' to 'loop-AES' for that reason, so both the builting 'loop' and the module 'loop-AES' can coexist
[13:45] <reindeer> ok and..
[13:45] <Walex> reindeer: and the patch is...
[13:47] <Walex> reindeer: wait...
[13:47] <reindeer> :-O
[13:49] <Walex> http://www.sabi.co.uk/Proj/Small/loop-AES-v3.6e_rename.diff
[13:50] <Walex> reindeer: you get the loop-AES tarball from http://loop-aes.sourceforge.net/ apply the diff, and build, and insert the 'loop-AES' module.
[13:52] <reindeer> ok, will try. I havent done diff merging before, but i guess ill google some
[13:52] <reindeer> and thanks so far
[13:52] <Walex> reindeer: just use patch -p0' inside the directory
[13:52] <Walex> reindeer: 'wget -N -O /tmp/loop.diff http://www.sabi.co.uk/Proj/Small/loop-AES-v3.6e_rename.diff'
[13:53] <Walex> reindeer: wget -N -O /tmp/loop-AES.tar.bz2 http://loop-aes.sourceforge.net/loop-AES-latest.tar.bz2
[13:54] <Walex> reindeer: cd /tmp; tar -x -j -f loop-AES.tar.bz2
[13:57] <Walex> reindeer: cd /tmp/loop-AES-v3.6g
[13:57] <Walex> reindeer: patch -p0 < /tmp/loop.diff
[13:57] <reindeer> ok
[13:57] <BluesKaj> looks an encryption lecture in here this morning :)
[13:58] <reindeer> this is great! :)
[13:58] <reindeer> ok, patched
[13:59] <reindeer> it says "1 out of 8 hunks FAILED -- saving rejects to file ./Makefile.rej"
[13:59] <reindeer> at "patching file ./Makefile"
[14:00] <Walex> reindeer: it does not matter, it builds regardless. Just say 'make'
[14:00] <reindeer> made
[14:01] <Walex> then 'cp -p tmp-d-kbuild/*.ko /lib/modules/$(uname -r)/extra' and then 'depmod -a'
[14:03] <reindeer> i dont have the destination folder 'extra' at the moment but thats ok i guess?
[14:05] <reindeer> or?
[14:05] <reindeer> Walex
[14:07] <Walex> reindeer: make it
[14:08] <reindeer> k
[14:11] <reindeer> i take it that the 'cp' command needs sudo, because the mkdir needed that too? asking cos I dont want to mess things up, which sometimes happens when copying/running something as sudo/root when not supposed to and then not being able to access that as a normal user anymore..
[14:12] <Walex> reindeer: yes
[14:15] <reindeer> hmm, since i built the files not using sudo they are actually owned by me, at the 'extra' folder  is that a problem?
[14:15] <reindeer> Walex
[14:16] <Walex> reindeer: no, but you can change ownership. Hey, these are very basic questions for someone who wants to setup encryption :-)
[14:18] <reindeer> just havent done any kernel pathcing before (if that is the correct term)
[14:18] <reindeer> *patching
[14:21] <reindeer> Walex: ok depmod done
[14:22] <Walex> reindeer: done.
[14:22] <Walex> reindeer: so 'modprobe loop-AES'
[14:23] <Walex> reindeer: and imminently you should see in '/dev' a number of 'loop-AES' device files
[14:24] <reindeer> yes, seems so, right after regular loop's, fresh from the oven
[14:27] <reindeer> ok, so now i should be able to proceed according to the guide, willcheck
[14:28] <Walex> reindeer: you must use 'losetup' because the regular patches to 'unix-utils' only look at device files called "loop" not "loop-AES"
[14:29] <reindeer> Walex: ok. I was just about to ask that do i need to reference all "/dev/loop0" as /dev/loop-AES0" but i guess that wont work..?
[14:30] <Walex> reindeer: yes, you need to do that, but 'mount -o loop' won't work because it will use a "/dev/loop" device.
[14:31] <reindeer> Walex: i see, i will try now
[14:45] <reindeer> Walex: hmm somehow it still fails with the "ioctl: LOOP_MULTI_KEY_SETUP_V3: Invalid argument" error..maybe is will post all my commands here
[14:47] <reindeer> So following this guide at part 3.3: http://loop-aes.sourceforge.net/aespipe.README
[14:48] <reindeer> first:   'yes "" | dd of=image.iso bs=512 count=16'
[14:48] <reindeer> head -c 3705 /dev/random | uuencode -m - | head -n 66 | tail -n 65 | gpg --symmetric -a | dd of=image.iso conv=notrunc
[14:49] <Walex> reindeer: stop there. Have you got the '.iso' files and the keys?
[14:49] <reindeer> yes
[14:50] <Walex> reindeer: then use 'losetup' with parameters eqyuivalent to 'encryption=AES128,gpgkey=image.iso,offset=8192'
[14:52] <reindeer> oh, but shuoldn't i do the part "mkisofs -quiet -r ./myfolder/ | aespipe -K image.iso -O 16 >>image.iso"  before?
[14:52] <Walex> reindeer: that part only happens when you create the ISO image, but you hav have already created it.
[14:53] <Walex> reindeer: once create the iso image stays encrypted.
[14:54] <Walex> reindeer: the 'losetup' options are more or less identical to the 'aespipe' options
[14:55] <reindeer> Walex: but isnt it that the 1st command creates and empty file, 2nd writes the key file to the beginning and then this 3rd mkisods should actally create the iso file itself?
[14:55] <Walex> reindeer: you said before you have already created the ISO image file and the key file...
[14:56] <Walex> reindeer: you just want to _mount_ it if what you said was accurate.
[14:56] <reindeer> well i think i created it somehow wrong because i cannot mount it using the losetup, so that swhy i wanted to start over to verify
[14:57] <Walex> reindeer: you cannot mount it using 'losetup' because you were using the wrong device...
[14:57] <reindeer> i did the whole procedure allready again using this new AES and it failed thats why i came back now
[14:59] <Walex> reindeer: note that the instructions in that file suggest that you prefix the image with the encrypted key, that is a slightly weird thing to do.
[15:00] <Walex> reindeer: anyhow what are you trying to do?
[15:00] <reindeer> i was wondering about that too, but since its from the author i went ahead and tried
[15:00] <reindeer> ok
[15:00] <reindeer> so
[15:01] <reindeer> head -c 3705 /dev/random | uuencode -m - | head -n 66 | tail -n 65 | gpg --symmetric -a | dd of=image.iso conv=notrunc
[15:01] <reindeer> asks for a passphrase, i used 20 numbers for a test
[15:02] <reindeer> then i did teh losetup with:
[15:03] <reindeer> 'sudo losetup -e AES128 /dev/loop-AES0 ./image.iso'
[15:03] <reindeer> it was ok
[15:04] <Walex> reindeer: it cannot have been ok beause you did not specify the required offset, and anyhow the image was empty.
[15:04] <Walex> reindeer: if you are following a non trivial procedure without understanding each step, bad news.
[15:05] <reindeer> yes i forgot to post one step:
[15:06] <Walex> reindeer: what are you trying to achieve? Why are going alon wiht Jari Ruusu's bizarre scheme of putting the encrypted keylist at the beginning of the image file instead of a separate file?
[15:07] <reindeer> so this was the third command: mkisofs -quiet -r ./folder/ | aespipe -K image.iso -O 16 >>image.iso
[15:07] <Walex> reindeer: also, if you follow his scheme the options to 'losetup' probably need to be '-e AES128 -o 8192 -K image.iso'
[15:08] <reindeer> Walex: well simply im just trying to do an encrypted dvd image of a folder, that i can burn and access later by mounting it.
[15:09] <reindeer> and tbh, i dont understand that keylist thing at all, why oh why
[15:10] <Walex> reindeer: they keylist thing is simple: you can encrypt with either a single key which is in effect a password, or with a set of keys that rotate.
[15:11] <Walex> reindeer: since the set of keys is large, you cannot remember it, so you put it into a file and encrypt that file. So when you decrypt, first the file with keys is decypted, then the decrypted keys are used to decrypt the loop image.
[15:11] <reindeer> ok.  I just did a new gpg user just for this aesloop to test, but what is even unclear is that do i need to use that gpg users password in some of these commands or not..and why it asks for password in some of the points, even though it has the gpg key assess..sigh
[15:12] <reindeer> ok
[15:13] <reindeer> *assess->passes
[15:13] <Walex> reindeer: in order to avoid losing the encrypted key list, Jari Ruusu suggested prefixing it to the image file, so the first 8192 bytres contain the encrypted key list, and the rest contain the ISO image encrypted with that key list.
[15:14] <reindeer> ok, makes sense, understood, thx! :)
[15:14] <reindeer> and no i dont mean that example was over simplified, it was just good.
[15:14] <Walex> reindeer: So 'losetup' needs to be given 'image.iso' twice: once with offset 0 to get the encrypted key list file, the second with offset 8192 and AES128 decryption to get the image.
[15:16] <Walex> reindeer: so if you followed the instructions the 'head ....' bit creates a list of 64+1 keys, and writes it in the first 8192 bytes, and the 'aespipe -K ...' bit uses that to encrypt the image and put it after that (-O 16 is the same as 8192 bytes)
[15:17] <reindeer> ok, yes i understand that
[15:17] <Walex> so in the end you should write 'losetup -K image.iso -e AES18 -o 8192 /dev/loop-AES0 image.iso'
[15:18] <reindeer> ok, so it know to get the keys from the file properly, will try
[15:19] <reindeer> and its -AES128 i belive ;)
[15:19] <Walex> reindeer: the first 8192 bytes (less actually) are encrypted with GPG, and the bit after 8192 bytes are encrypted with AES128
[15:22] <reindeer> ok and what about the mount command?
[15:22] <Walex> reindeer: same as always, not '/dev/loop-AES0' is a block device and you mount it as any block device.
[15:23] <Walex> reindeer: I use 'mount -t iso9660 -o ro /dev/loop-AES0 /mnt/...' for example
[15:23] <reindeer> hmm.. i did that and got "wrong fs type" ..sigh :/
[15:23] <reindeer> break, brb 10mins
[15:54] <reindeer> Walex: ok im back
[15:55] <Walex> reindeer: uhm I have been doing tests... wait.
[15:55] <reindeer> ok sure
[15:57] <Walex> reindeer: I have done some tests on the various steps/options, and it is not working as expected when there is an offset innvolved
[16:00] <reindeer> ok intresting
[16:01] <reindeer> Walex: so might explain the errors?
[16:01] <Walex> reindeer: yes. Wait as this is moderately peculiar.
[16:03] <reindeer> sure, im not in a hurry at this anymore, it is allready the second day i sacrifice for trying to get this to work. brb..
[16:23] <reindeer> back
[16:23] <Walex> reindeer: I found that there is a misdesign in loop-AES which probably was introduced later than Jari Ruuse wrote the README section
[16:24] <reindeer> oh
[16:24] <reindeer> its not on any buglists yet?
[16:24] <Walex> so to mount an image you have to do two 'losetup' steps
[16:24] <Walex> to work around this bug
[16:25] <Walex> losetup -o 8192 /dev/loop0 image.iso
[16:25] <ahoneybun> hello my clock keeps going to UTC and I am EST
[16:25] <Walex> losetup -e aes -K image.keys.asc /dev/loop-AES0 /dev/loop0
[16:25] <Walex> losetup -e aes -K image.iso /dev/loop-AES0 /dev/loop0
[16:26] <Walex> because 'loop-AES' computes the encryption from the start of the file, not the offset.
[16:26] <reindeer> Walex:oh, that is nice
[16:26] <reindeer> catch
[16:28] <ahoneybun> I have it set for New York everywhere, the digital clock widget, the date and time in the settings
[16:28] <Walex> ahoneybun: you have to set your locale also at the OS level, not just the KDE level.
[16:28] <Walex> ahoneybun: including your timezone.
[16:29] <ahoneybun> Oh well it was set when I installed it
[16:29] <SonikkuAmerica> ahoneybun: You may need to set it again
[16:29] <ahoneybun> How so?
[16:30] <SonikkuAmerica> First make sure your locale settings are correct (System Settings > Locale)
[16:30] <reindeer> Walex: what is the image.keys.asc file exactly? Is it the image just after the keys are appended to the start?
[16:31] <ahoneybun> SonikkuAmerica: It says USA but it has 4:30 pm not 12:30 pm
[16:32] <Walex> reindeer: it was a file I was using here for testing. I create first a tiny unencrypted ISO image 'image.iso', then an unencrypted keys files 'image.keys', then a GPG encrypted keys file 'image.keys.asc', then an encrypted ISO 'image.iso.aes', then a concatenation called 'image-keys.dat'
[16:34] <mawk> hi
[16:34] <SonikkuAmerica> ahoneybun: Right-click your clock and select "Adjust Date and Time..." and tell me what you see.
[16:34] <ahoneybun> SonikkuAmerica: says 16:34 as in 4:34 pm
[16:35] <SonikkuAmerica> OK (So does mine and I'm in the same time zone as you, EDT)
[16:35] <reindeer> Walex: so in my scheme it is the image.iso file after the "-head -c 3705..." command?
[16:35] <ahoneybun> I'm in est
[16:35] <ahoneybun> New York timezone
[16:36] <SonikkuAmerica> Are you in Indiana? We're on Eastern Daylight Time everywhere else in the ET zone
[16:36] <Walex> reindeer: also I used '/dev/urandom' for the key to avoid waiting.
[16:36] <ahoneybun> SonikkuAmerica: Florida
[16:36] <Walex> reindeer: so: head -c 3705 /dev/urandom | uuencode -m - | head -n 66 | tail -n 65 >| image.keys
[16:36] <SonikkuAmerica> ahoneybun: You should be on EDT then.
[16:36] <reindeer> Walez:same here, i just did CTRL-C on /dev/random :)
[16:37] <Walex> reindeer: mkisofs -quiet -rJ -V loop-AES image | aespipe -P image.keys >| image.iso.aes
[16:37] <ahoneybun> SonikkuAmerica: It is 12:37 pm not 4:37pm
[16:37] <SonikkuAmerica> Right, EDT.
[16:37] <Walex> reindeer: gpg --symmetric -a image.keys
[16:37] <SonikkuAmerica> What we'll have to do is [ kdesudo systemsettings ] to adjust the date and time.
[16:37] <Guest62631> Hi, i have a problem, when I try to login from kdm it back to login screen. I've tried to create a new user on terminal but nothing. Any suggestion, please?
[16:38] <ahoneybun> how it crashed
[16:38] <ahoneybun> and
[16:39] <SonikkuAmerica> With code 6?
[16:39] <SonikkuAmerica> ahoneybun: ("Unable to authenticate/execute the action: 6,")
[16:40] <Walex> reindeer: but wait, I did not put '-O 16' on my 'aespipe' so perhaps it would have worked otherwise without the double 'loop'
[16:40] <ahoneybun> now I went back 4 hours lol
[16:40] <Guest62631> Could you help me?
[16:41] <BluesKaj> ahoneybun:  in the date and make sure the UTC is uchecked in the time zone tab
[16:41] <reindeer> Walex: cant i use a directory entry like "mkisofs -quiet -r ./mydir | aespipe ..." ?
[16:41] <ahoneybun> no bug now but it does nothing
[16:41] <BluesKaj> date and time
[16:41] <ahoneybun> well the only time zone in the time and date timezones it UTC
[16:42] <ahoneybun> well Locale say the right time
[16:42] <SonikkuAmerica> BluesKaj: Unchecked? There's no place to check/uncheck anything! (I'm having the same problem)
[16:42] <ahoneybun> so now it says new york it is 8:42 am
[16:43] <ahoneybun> and utc is 12:42 pm
[16:43] <Walex> reindeer: you can, you know, commands can be used in many different ways, and if you try to use them blindly you will waste a lot of time
[16:43] <SonikkuAmerica> One second...
[16:43] <ahoneybun> restart maybe
[16:43] <BluesKaj> right clickm on the time and date in the panel , choose "adjust date and time" , then onn the time zone tab  scroll to the UTC
[16:44] <BluesKaj> ahoneybun: ^
[16:44] <ahoneybun> well I made the change
[16:44] <ahoneybun> some how
[16:44] <ahoneybun> now to do a restart to see if it stuck
[16:48] <SonikkuAmerica> ahoneybun: I have a solution to the UTC problem if you didn't get it solved
[16:49] <SonikkuAmerica> Wow, left
[16:49] <Walex> reindeer: my experiment was wrong, if I create the image with keys with 'aespipe -O' it mounts directly without doing a two level thing.
[16:49] <reindeer> Walex: ok
[16:50] <BluesKaj> SonikkuAmerica:  no need to restart
[16:51] <SonikkuAmerica> I had rebooted, but I found out the solution was to symlink /etc/localtime to the correct tz file
[16:51] <Walex> reindeer: so for me the procedure in Jari Ruusu's README works all through.
[16:52] <BluesKaj> this works for me , right click on the time and date in the panel , choose "adjust date and time" , then on the time zone option and scroll to the UTC uncheck that , then find a city in your timezone and check that.Then click ok
[16:53] <SonikkuAmerica> BluesKaj: Apparently in Raring they don't have checkboxes
[16:53] <SonikkuAmerica> (Or in 4.10)
[16:53] <BluesKaj> I'm on 13.04
[16:53] <BluesKaj> and 4.10.1
[16:54] <SonikkuAmerica> OK... But on my Time Zone tab there aren't check boxes
[16:55] <reindeer> Walex: ok, good, im just now doing a new clean experiment. and for the mkisofs command i now read that the -r is to make rationalRockRidge, -J to jolietDirs and -V is to give the volume and id of "loop-AES" and after that comes the "image" that can could be in any path ofcourse, like "/dir/dir/image.iso" it all just looks quite confusing without knowing the switches..
[16:56] <SonikkuAmerica> BluesKaj: Screenshot here: http://imagebin.org/252102
[16:57] <BluesKaj> SonikkuAmerica:  here's mine
[16:57] <BluesKaj> http://imagebin.org/252103
[16:58] <zzAMzz> SonikkuAmerica: Use "Digital Clock Settings" and "Time Zones" Tab
[16:58] <SonikkuAmerica> If you insist... (not to mention my KDE config looks more like GNOME 2 XD) It might be that I haven't upgraded to 4.10.1
[16:59] <SonikkuAmerica> Ohhhhhhhhhh
[16:59]  * SonikkuAmerica feels like an idiot for opening Digital Clock Settings and never, ever seeing that tab
[17:01] <SonikkuAmerica> (I do have 4.10.1 of course)
[17:01] <SonikkuAmerica> Now that I have that fixed, I'm having a problem with acpid interfering with KDE power management.
[17:02] <reindeer> Walex: You mean works all through, without even changing the /dev/loop0 to /dev/loop-AES0 ?
[17:02] <Walex> reindeer: yes.
[17:02] <reindeer> ok im doing it too now
[17:02] <SonikkuAmerica> Particularly, no matter how I config my power button, acpid always sends [ sudo shutdown -h now ] to my computer.
[17:03] <SonikkuAmerica> On top of that, I embarrassed myself by imagebin'ing the wrong window. :\
[17:05] <reindeer> Walex: well while doing literaly the same except for filenames and locations at the end of mount command i get: "ioctl: LOOP_MULTI_KEY_SETUP_V3: Invalid argument"
[17:05] <BluesKaj> no worries , SonikkuAmerica , we all make those mistakes sometimes
[17:05]  * SonikkuAmerica grins
[17:05] <SonikkuAmerica> But anyway, about the other problem: no matter how I config my power button, acpid always sends [ sudo shutdown -h now ] to my computer.
[17:05] <Walex> reindeer: as I was trying to explain you cannot use the 'mount' command but you must use the equivalent 'losetup' command.
[17:05] <reindeer> ok, so it was not literally :)
[17:06] <BluesKaj> recommend konversation to xchat tho , SonikkuAmerica :)
[17:06] <reindeer> will try..
[17:06] <SonikkuAmerica> BluesKaj: You said that yesterday! XD
[17:06] <BluesKaj> see ? :)
[17:07] <BluesKaj> I just don't get xchat
[17:07] <SonikkuAmerica> Kinda fell in love with XChat though. It came from a little fling with XFCE
[17:07] <BluesKaj> understand whay it's so goofy
[17:07] <BluesKaj> don't
[17:07] <reindeer> Walex: because ive been trying to take notes about the commands that should make this whole thing work and they keep changing quite often it seems, first we have to use losetup, then we have to do it 'twice', then we can do this just literally as the guide says, but then afterall we have to use the losetup, so i guess im getting a littel confused here.. ;)
[17:08] <reindeer> not to mention patching the kernel in between all this :)
[17:08] <Walex> reindeer: that's understandable. You can do the building of the image literally, and then use the 'losetup' with '-o 8192' to open the image and then a separate mount.
[17:10] <SonikkuAmerica> BluesKaj: It also came stock with Mint (which was surprising)
[17:11] <SonikkuAmerica> Weird... it went right back to UTC
[17:12] <reindeer> oh behold the creation it is mounted! :D
[17:12] <reindeer> Walex:success
[17:12] <SonikkuAmerica> OK that symlink worked again
[17:13] <BluesKaj> SonikkuAmerica:  or run , sudo dpkg-reconfigure tzdat
[17:13] <SonikkuAmerica> *tzdata
[17:14] <SonikkuAmerica> All set
[17:14] <reindeer> Walex: that was quite and adventure dont you think, or just a regular day at the cryptographic's day? Now to make a script and possible www post on the subject would be next.. :)
[17:14] <Walex> reindeer: that's good....
[17:15] <Walex> but I was very disappointed that loop-AES does not start the IV calculations at the given offset. Rather inappropriate. But whatever...
[17:22] <SonikkuAmerica> {ATT 2 (10 minute wait)} It seems that no matter how I configure my power button to work in KDE power management, the computer always shuts down when I press it... any ideas?
[17:24] <BluesKaj> back your mint comment SonikkuAmerica , think mint was originally camw with the gnome desktop , so xchat stuck
[17:25] <SonikkuAmerica> That might be.
[17:25] <BluesKaj> or orginally came with the gnome desktop , rather
[17:28] <reindeer> brb
[17:30] <SonikkuAmerica> {ATT 3 (8 minute wait)} It seems that no matter how I configure my power button to work in KDE power management, the computer always shuts down when I press it... any ideas?
[18:31] <reindeer> Walex: 1.If following the Jari Ruusu guide, besides using losetup at the end, is the new loop-AES and patch even needed for the task anymore? 2. When updating kernel, do i need to rebuild both and copy to the latest kernels 'extra' folder every time?
[18:32] <Walex> reindeer: yes yes
[18:32] <reindeer> :)
[18:35] <reindeer> Walex: Whats a good way to handle that kind of rebuild process, are there some scripts/methods? Or should one just keep away from updating kernel?
[18:35] <Walex> don't rebuild the kernel unless you know better. building out-of-kernel modules is sometimes inevitable, but to be minimized. For loop-AES it is inevitable.
[18:38] <reindeer> Walex: ok thanks and no i wont be building kernel, i just ment the official updates coming through apt-get.
[18:39] <Walex> ah the official updates are often quite important
[18:41] <reindeer> Walex: and of course this new loop-AES  is needed, even for following the guide, because  the mount goes through /dev/loop-AES0... im still digesting this.. :)
[18:42] <Walex> reindeer: the 'loop' driver is hardbuilt-into the kernel, and regrettably various commands have hardcoded "/dev/loop" as the name of the loop device.
[18:42] <reindeer> yes, that i know
[18:43] <reindeer> Walex: btw, on what kind of system the guide would work, literally without any modification? What is the culprit here..?
[18:52] <Walex> reindeer: well, in theory Ubuntu who have hardcoded the non-AES loop into the kernel, and you for at the beginning for using the wrong kernel driver.
[18:53] <reindeer> ok
[18:54] <Walex> reindeer: but no guide should be expected to work without modification or understanding of what it does. Unless by a "practictioner".
[18:57] <reindeer> ok, so as you mentioned in the start that there are also DM crypt and Cryptoloop, so could this image encryption be done with those, out-of-the-box then? So are those the more standard tools, or what are?
[19:02] <Walex> reindeer: cryptoloop is probably obsolete
[19:09] <lordievader> Good evening
[19:13] <reindeer> hi
[19:17] <lordievader> Hey reindeer, how are you?
[19:18] <reindeer> good thx
[19:36] <reindeer> Walex: does the loop-AES patch/diff need to be a new one for every new kernel or can the same one be used for how long?
[19:57] <Hannes_> was ist das hier? :)
[19:58] <Hannes_> So ein programm gegen langeweile?
[19:59] <Hannes_> sdasdsdsddsadasd<wswsdwadwdsadsadasdsadadrfrfrfrfr
[19:59] <Hannes_> #
[20:02] <lordievader> !de | Hannes_
[20:03] <Hannes_> Oh, thank you! :-)
[20:10] <Quest>  when i click on networks tab in file manager and then in samba shares, it says Unable to find any workgroups in your local network. This might be caused by an enabled firewall. . any idea?
[20:12] <Captain_Proton> Quest: I have the same problem I have not been able to find a solution. the work around is the path bar delete what there and typ smb://ip or computer name then hit enter
[20:15] <Quest> Captain_Proton,  I stoped the firewall by  gui. now they are showing up
[20:17] <Quest> Captain_Proton,   how to see the list of computers on network by concole?
[20:22] <Captain_Proton> Quest: http://askubuntu.com/questions/102924/list-samba-shares-and-current-users
[20:28] <chiefw0tj_> Greetings all! New here...just switched to Kubuntu 12.10.  Gotta say I'm loving it!
[20:28] <Quest> Captain_Proton,   how to see the list of computers on network by concole?
[20:41] <syncsys_> Captain_Proton,   how to see the list of computers on network by concole?  I was disconnected.
[20:53] <syncsys_> how to see the list of computers on network by concole?