Search Results: "corsac"

14 April 2007

Yves-Alexis Perez: Xfce 4.4.1

Ok, so Xfce 4.4.1 (bugfix release) is out since some days. I've packaged this new version, which is mostly ready in our svn. So 4.4.0 won't be uploaded to unstable at all, and we will upload directly 4.4.1 in sid in some days. The thing which blocked us to upload to unstable was gtk2.10, and it has been uploaded yesterday, so nothing is blocking now and we should be able to upload really soon.

The packages are available from my repository for ppc and sparc. I've changed the layout to add an UNRELEASED branch, so people using it are warned that those packages are even more unstable than unstable. Those packages are packages which have not been uploaded to debian, and thus may be unusable.

Alway prefer packages coming from pure Debian repositories, but if you want to test and help us correct mistakes, you can use the repository (and report bugs to our mailing list).

For etch users, I'll prepare 4.4.1 backports, but as I don't have hardware access, they will be only ppc and sparc binaries. Maybe other will be able to build backports for other arches.

15 March 2007

Tollef Fog Heen: Strength of asymmetric and symmetric encryption algorithms

Yves-Alexis Perez writes a bit about Debian and crypto-containers, comparing cryptsetup and encfs. The comparison is decent enough, except that it's fairly trivial to get cryptsetup to integrate into the whole gnome-volume-manager stack and have a dialogue pop up when you insert an encrypted USB stick or similar. Sure, it's mounted by a root process, but I wouldn't claim it's any kind of insecure because of that. What did really catch my eye was the line near the end:
[...] but this is a bruteforce attack against master password (1024 bits RSA key), not against 128bits aes key of the container.
Well, according to conventional research, a 1024 bit RSA key is about as strong as an 80 bit symmetric key. A semi-recent RSA paper confirms this too. And to the best of my knowledge, there has not been found weaknesses in AES which lower the effective key size.

14 March 2007

Yves-Alexis Perez: Debian and crypto-containers

Theses days, I've been looking for a way to have crypto-containers in Debian. I wanted something easy to use, easy to move but still quite secure, which wouldn't require root access to the box, and as an option could use my gpg key.

I looked closely at two projects:

* cryptsetup/luks

The nice thing is that you only have one file containing all your crypted filesystem, it uses the Linux unified key management system (luks), and you are able to use a gpg key to crypt the data. I didn't tried it yet, because there are some drawbacks which I find really important. It uses multiple commands for every operations (creating the container, mounting and unmounting it).

For creating the crypto container you need to:
- create the file
- use it as a loop device (root access)
- initialize the container
- open the container
- create a filesystem on it
- mount it

Each time you want to mount it, you need to:
- create the loop device from the file
- open the container
- mount it

It surely can be wrapped, but that may be difficult to deploy. And you need root access for all operations (you can mount/umount without it using fstab, pmount or things like that, but still it's using privilegied access). And the major drawback, I think, is that the container size is fixed. You choose it when you create the initial file which you'll mount as a loop device. I don't know if there's a way to extend it after creating crypto-container, but anyway it'll need to be manual.

* encfs

encfs is fuse-based, so it doesn't require anything, beside fuse support in the kernel and your user belonging to fuse group. No need to root access nor anything. You create the container with only one command, then mount or umount it with only one command too. You can add and remove files from the container without asking yourself about disk usage or something, because the container is "expanded" (see after) when you add files, automatically.

There are two drawbacks in encfs, for me:
- crypto-container isn't a file, but a folder, with files and folders using crypted filenames but real size. (more or less, because you can use options to modify it but you won't hide a 20MB file for example). It's less secure than a one-file crypto-container where you can't determine how many files there are in it (and with crypsetup/luks, you won't be able to determine how much space is used in the container as the size is fixed anyway). It's less easy to move around, put on an usb key or transmit. You can tar it, yes, but you lose the comfort.
- you can't use a gpg key

In the end, I guess I'd like something like .dmg OSX Disk Images, which can be encrypted. They are really easy to use, as far as I could have seen. Maybe not so secure, but this is a bruteforce attack against master password (1024 bits RSA key), not against 128bits aes key of the container.

Anyway, I've setup an encfs folder here, but am still looking for something wich would improve the situation.

5 March 2007

Julien Blache: On why I wrote pommed

Wouter asks why I wrote pommed instead of patching pbbuttonsd. First things first, pommed was originally named mbpeventd and targeted only at the MacBook Pro and MacBook laptops. The port to the PowerBook and iBook (which is what Wouter uses, I think) wasn’t a goal at first. pommed handles the hotkeys events and the ambient light sensors (if available) and that’s it. Nothing more. pbbuttonsd does a lot of other things that other pieces of software can handle far better than it does. I never ran it on my PowerBook and stuck to pmud; it did just what I needed it to do, and it did well. The kernel handled the LCD backlight all by itself, and I had no need for either the volume +/- keys or the eject key. When I got my MacBook Pro, I took a look at the various ways to get the hotkeys to work. Well, nothing worked. I discovered that pbbuttonsd was also available on i386/amd64 and gave it a try. IIRC I had to build it on amd64, and the Makefile already raised a couple of mental flags. But oh well. Then I tried to configure it, and discovered a gazillion configuration options, half of them unneeded. Anyway, I got to the point where it would run, and obviously there was some patching to be done to get it to play nice with the MacBook Pro. To put it simply: looking at the code made me cry. It’s horrible. Incredibly complicated and obfuscated for no good reason. At that point, patching was out of the question. Moreover, I never liked pbbuttonsd that much, for various reasons, ranging from its “let’s do everything!” policy to its SHM interface for the GUIs (come on, that’s the 21st century knocking at your door). So, in a nutshell: I really like the KISS approach and the traditional UNIX way of doing things, so I tend to dislike most one size fits all software. It took me, what, 2 hours to build the first version of mbpeventd which handled the LCD and the keyboard backlight. That’s all the features I needed, past that point everything else was just pure bonus. As for the name… mbpeventd really sucked as a name, and it wasn’t a good name anymore once the PowerBook support got added. I did not want to go with something like “appled” because I did not want to use the name “Apple”, but that was the closest match. Then I thought “hmm, why not … translate it … pommed? … sold!”. The name is funny for both Corsac and I because it’s a fortune cookie from one of the IRC channels we’re both hanging on; as it happens, the fortune is about Apple hardware and how users can get lost with a one button mouse. So, why use pommed? Use it if you want something lightweight, fast and simple which won’t try to do everything for you. And you can even patch it and send me the patches!

25 February 2007

Yves-Alexis Perez: FOSDEM

I'm now just back from FOSDEM in Brussels. Well I was back few hours ago, but now I've eaten, I've send the signed keys from the KSP, pictures are on their waythere, it's time to post.

First, I'd like to really thanks Wouter for the Hosting near Brussels, Madcoder for the trips, and everyone in FOSDEM organization. From my point of view, it was flawless. We had wifi when they promise it, and it works great during all the weekend, we had food and beer at good prices, people were kind etc. Really really thank you.

It was my first "international" meeting, one month after my first "national" meeting at Solutions Linux. First time I met so much FOSS developers, and especially Debian ones. Lot of people I didn't know, lot of people I still don't know, but which I was glad to hear of, to see talks...

I was especially interested by sunday talks, netconf from madduck, and Debian Internals by Enrico, which were really nice (and netconf seems promising).

It was really short, and exhausting, but it made me want to go to Edimburgh for Debconf7, but I really don't know if I'll be able to do this. (nor if I would want to leave for a week 'alone' ...)

In the end, it was a quite improvised week-end, but a really nice one.

1 February 2007

Pierre Habouzit: Solutions Linux

Solutions Linux was great. At least I had a great time, seeing a lot of people that I meet too seldom. A short making up is: There was not as many visitors I would have hoped, but that was still a nice time. edit: it seems only the video card was broken after all, because I carried the computer forgetting to remove the DVI to VGA adapter. So that's a 50 loss, not a 350 + one. I'm relieved

30 January 2007

Yves-Alexis Perez: Solutions Linux, day 1

Today I was at Solutions Linux, with the Debian France team. We weren't presenting something special, only showing the Debian Installer in babelbox, some Etch/Sid desktops (mostly Xfce, currently).

Lot of people came to see Etch, and asked about the release. There were lots of questions about Xfce too (as the two pcs we had there, besides the babelbox, were running it, my laptop using 4.4 and MadCoder's one with the default Etch configuration). Lots of visibility for Xfce and Debian, yeah.

You can see photos there.

27 January 2007

Yves-Alexis Perez: Xfce 4.4 experimental packages.

Ok, i386 users which have downloaded my packages here, I know you can't use thunar volume manager (thunar-volman) nor (u)mount devices from thunar, as it says that exo isn't built with hal support.

Hal support is indeed not enabled in i386 build (it is for ppc builds) on debian.corsac.net. I won't rebuild Xfce 4.4 for i386 with exo hal support enabled, as I don't really have currently enough power to do that more than once in a while.

But ema has begun to upload Xfce 4.4 package to experimental, so exo (with hal support enabled) is available on Debian Experimental packages.

If you want to test it, add experimental sources to your /etc/apt/sources.list:

deb http://ftp.fr.debian.org/debian/ experimental main


Then update and install exo:

sudo aptitude update
sudo aptitude install libexo-0.3-0/experimental


You can also pick other libs from there, which are more recent than ones on debian.corsac.net.

As always, be aware that those packages are in experimental shape, so it may damage your system, kill your cat and make your SO go away. Be prepared!

Anyway if you encounter bugs, don't hesitate to tell us on irc (precising from where your packages come from).

Happy testing.

23 January 2007

Yves-Alexis Perez: Xfce 4.4 released.

Ok, so now everybody knows, Xfce 4.4 has been released, the final version is now out since sunday.

During sunday I worked to package it, and by the time the release was announced, packages were (mostly) ready in our svn. It runs fine (no real changes since 4.4rc2 so there's no urgency).

4.4 won't be uploaded to unstable soon, because of the freeze status. It may be uploaded to experimental in the future.

I've made/uploaded preliminary packages to my repository. There are there packages for ppc and i386. ppc packages are built against gtk 2.10 from experimental, and they run fine (except mousepad with line numbers activated, known bug in gtk 2.10.7). i386 packages are built against gtk 2.8 except gtk2-engines-xfce, built against gtk2.10 because it now uses in the packaging a call to a module only present in gtk 2.10.

If you want to install Xfce 4.4 on i386 via my repository and don't wan't to switch to experimental gtk 2.10, you can do as follow:

apt-get source gtk2-engines-xfce
dpkg-source -x gtk2-engines-xfce_2.4.0-1.dsc
cd gtk2-engines-xfce-2.4.0
vi debian/rules


Now you just have to remove the call to dh_gtkmodules.
Then:

vi debian/control


In the Build-Depends: line, change the dependency from gtk 2.10 to gtk 2.8. (libgtk2.0-dev (>= 2.8) should be ok).

Then just rebuild the package as usual:

apt-get build-dep gtk2-engine-xfce
dpkg-buildpackage -rfakeroot -us -uc


As alway, don't use those packages if you want stability. Current i386 packages are not up to date (as I can't rebuild quickly for this arch), and they can change at anytime. If you still want to test, don't report bug on Debian BTS but rather on IRC (#debian-xfce@freenode).

Happy testing!

11 December 2006

Yves-Alexis Perez: NM Queue, Xfce 4.4rc2 and Etch freeze...

It's been more than one year that I'm waiting on NM queue, waiting for an Applicant Manager, performing Philosophy & Procedure part 1 & 2, then Tasks & Skills.

When applying for NM, it's really appreciated to already maintain a few packages in the archive, so for T&S the AM can check them and appreciate the work done. I guess people applying for NM first start by taking care of some package, before submitting.

But for me, it was the opposite way. I joined pkg-xfce team more than 18 months ago, and got my first packages in the archive a few weeks later.

I only applied to NM 6 months later, because, as I was dedicating more time to pkg-xfce, it would be more efficient for me to be able to upload directly, without
bothering huggie or ema (the two DDs in the team). It wasn't really required, but
it interested me, and huggie said me that it'd take some time so the sooner, the better.

Now, due to personal reason, huggie and ema don't have time/motivation anymore to work on pkg-xfce. I'm currently the one in charge, as I spent some time on it, and tries to spent some time on debian-desktop team, so we have a nice and consistent look for desktop environments in Etch. But I can't upload my packages myself, I need to find a sponsor. Xfce represent more than 50 packages (including goodies), that's quite a lot, and we have scripts and procedure to be efficient when rebuilding everything. If I could do everything myself, Xfce 4.4rc2 (released 2006/11/05) would have been in Etch since a long time. But I can't, because I'm stuck in NM queue.

Most of 4.4rc2 packages have been uploaded by my AM, Dafydd Harries (which I want to thank, though), but not everything, and few packages won't be in Etch, now that it's frozen. Yeah, that means that Etch will have half rc1 and half rc2, which isn't really good. Not really bad either, but still... (ok, and not as bad as shipping broken svn snapshots...)

I'm interested in beeing a Debian Developper because I *know* it'll make my work and my time more efficient. And not beeing able to push rc2 to Etch because of that really makes me sad...

30 November 2006

Yves-Alexis Perez: exiv2

Ok so, I was there, trying to assemble pictures taken at my sister's birthday. I have my pictures, her boyfriend's pictures, both have more or less the same date sor pictures have the same timestamp. Then comes another friend, which camera isn't at all at the same time. It's +/- 6:43 hour lead. And there is the mess, because I want all those pictures sorted by time, so people looking at them doesn't have to sort them himself. He just clic "next" and the next photo appears, whoever has taken it.

Now, I want my pictures sorted by time and gallery knows how to extract the time for EXIF tags, so I don't have to set the modification time of the files accordingly. But what to do when even EXIF tags are wrong ? I just discovered exiv2 adjust option, which does exactly what I want. From the manpage:

ad adjust
Adjust EXIF timestamps by the given time. Requires option -a
time.

-a time
Time adjustment in the format [-]HH[:MM[:SS]]. This option is
only used with the ’adjust’ action. Examples: 1 adds one hour,
1:01 adds one hour and one minute, -0:00:30 subtracts 30 secccc‐
onds.


So a simple loop accros those files:

corsac@hidalgo: for i in * [/tmp/gallery/arthur]
for> do
for> exiv2 ad -a -6:43 $i
for> done


and the work is done. Simple. Powerful. I love it.

Next.

Previous.