Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

clfarron4 · 2014-09-21 16:00:55

PSA: I am currently looking for a new building and hosting service, so these repositories aren't actually being updated at the moment.

Also, linux-ck-pax is dropped.

I have received correspondence which indicates that there may be issues between ext4 superblocks and TRESOR when using ext4 on a TRESOR encrypted partition.

I would like to emphasise that TRESOR should be treated as experimental software, thus isn't production ready and shouldn't be used for personal storage. If you have any worries, you should back-up your data and move to non-TRESOR encrypted partitions.

If you would like to help diagnose the issue, please see this post.

If you have been affected by the issue and are looking to recover the data on the partition, please see this post.

======

Just as it says, here is a series repository for x86_64 builds LTS kernels.

You can view them all here.

linux-lts-ck: Current ArchLinux LTS kernel with the CK patch

[linux-lts-ck]
Server = http://dl.dropbox.com/u/298301785/arch/linux-lts-ck/$arch

linux-lts31x: Older LTS kernels (3.10 and 3.12 branch)

[linux-lts31x]
Server = http://dl.dropbox.com/u/298301785/arch/linux-lts31x/$arch

linux-lts31x-ck: Older LTS kernels (3.10 and 3.12 branch) with the CK patch

[linux-lts31x-ck]
Server = http://dl.dropbox.com/u/298301785/arch/linux-lts31x-ck/$arch

linux-tresor: Arch current and LTS kernel with TRESOR

[linux-tresor]
Server = http://dl.dropbox.com/u/298301785/arch/linux-tresor/$arch

Please see this post regarding an issue discovered with TRESOR.

You can retrieve my PGP as follows:

pacman-key -r E6366A92 && pacman-key --lsign-key E6366A92

Other miscellaneous repositories:

[nuke-keys]
Server = https://dl.dropboxusercontent.com/u/298301785/arch/nuke-keys/$arch

If there is enough demand (and I have time), then I might consider i686 builds as well.

Last edited by clfarron4 (2015-11-01 15:48:13)

graysky · 2014-09-21 17:04:52

The title shows "Unofficial Repository for LTS, ck-pax and LTS-TRESOR kernels. x86 only" but you are providing x86_64

clfarron4 · 2014-09-21 22:57:15

graysky wrote:

The title shows "Unofficial Repository for LTS, ck-pax and LTS-TRESOR kernels. x86 only" but you are providing x86_64

As you can guess, I was probably a bit excited when I filled out the post. Thanks!

graysky · 2014-09-21 23:18:55

NP. Do it myself all the time. 2nd draft is better than the first

clfarron4 · 2014-10-24 18:32:42

This news item regarding Intel Microcode updates applies to kernel packages in the repository updated after October 13-th.

clfarron4 · 2014-12-14 14:26:31

Holiday Note: There will be no updates to this repository for a period of approximately two weeks starting Thursday 18-th December 2014, because of holidays.

The AUR tarballs will still be updated as normal.

Last edited by clfarron4 (2014-12-14 14:30:01)

clfarron4 · 2015-01-20 13:43:01

OK, I am moving stuff for lts312, lts312-ck (and hopefully lts310 and lts310-ck) from /usr/src to /usr/lib/modules/$version/build over the next few weeks (like what happened over these two commits for the main Arch kernels).

As far as I'm aware, the move for lts312 is working perfectly fine, thus lts312-ck is next on the list.

If you experience any breakage because of this, tell me (or Andes. It was his idea.), else I will assume all is fine.

Last edited by clfarron4 (2015-01-20 13:45:39)

clfarron4 · 2015-03-16 14:23:21

I have received correspondence which indicates that there may be issues between ext4 superblocks and TRESOR when using ext4 on a TRESOR encrypted partition.

I would like to emphasise that TRESOR should be treated as experimental software, thus isn't production ready and shouldn't be used for personal storage. If you have any worries, you should back-up your data and move to non-TRESOR encrypted partitions.

If you would like to help diagnose the issue, please see this post.

If you have been affected by the issue and are looking to recover the data on the partition, please see this post.

Last edited by clfarron4 (2015-03-16 14:32:40)

clfarron4 · 2015-03-16 14:28:55

In the event you have suffered ext4 superblock corruption on a TRESOR encrypted partition, please try the following steps:

1) Recover the corrupted filesystem superblock on the filesystem to get what pieces were left in tact (uncorrupted) with

fsck -y

.
You may not be able to recover the entire filesystem hierarchy.

2) Use GNU find and the_silver_searcher, ag, to process all orphaned inodes in /lost+found, searching for any files that weren't in the recovered hierarchy from step 1.

3) Use the trial version of RStudio to process the entire exported filesystem image, looking for data that looks like e.g. ASCII or Unicode text, saving all found files for further processing. The trial version allows you to recover any file under 256KB.

clfarron4 · 2015-03-16 14:30:37

If you want to take steps to further investigate this issue, I recommend the following :

1) Take a periodic backup of the TRESOR device's filesystem superblock. Upon failure use this block for filesystem recovery, and verify that all data is correctly accessible and intact. This will further confirm that only the superblock itself is being corrupted.

Note that performing some operations, such as filesystem defragmentation, would result in a completely different superblock, such that if failure was to occur after such an operation and before backing up the new superblock, the old superblock would likely not be of much use when recovering data.

2) Create a RAID1 array between a TRESOR encrypted filesystem and a non-TRESOR encrypted filesystem. On failure, check the superblocks of both devices separately. If they differ, this confirms TRESOR's role in corrupting the filesystem superblocks.

clfarron4 · 2015-03-16 22:41:17

I know that 3.18 is now an LTS kernel release. Let me repeat: There is no need to get your knickers in a twist worrying about whether packages for 3.18 will be coming.

I'm just waiting to see what is going to happen to the official linux-lts package first and then act accordingly. My guess is that linux-lts will stay at 3.14, since 3.18 is not a GKH-maintained release.

Last edited by clfarron4 (2015-03-16 23:00:41)

clfarron4 · 2015-03-22 21:42:59

It's been a week and I haven't seen anything about 3.18 LTS on any arch-related channels. Go forth and test!. You'll also find it in the linux-lts31x repository.

If there's demand for the corresponding CK kernel as an LTS release, I'll think about it.

Also, I'll be away from good internet starting this coming Saturday, so yes to Source tarballs, no to repository updates.

PS: I was going to deliberately try and make this post #1900, but I was bored of waiting.

Last edited by clfarron4 (2015-03-22 21:45:18)

clfarron4 · 2015-04-13 21:47:34

I'm not well at the moment and busy with exam revision. So AUR tarballs are also on hold until sometime next week.

Jristz · 2015-04-13 22:00:56

+1 for i686 ck if you are counting votes.

clfarron4 · 2015-04-16 21:38:35

Jristz wrote:

+1 for i686 ck if you are counting votes.

Which one would like the i686 for?

clfarron4 · 2015-07-24 07:54:03

Holiday Note: There will be no updates to this repository for a period of approximately one week starting Friday 25-th July 2015, because of holidays.

The AUR tarballs will still be updated as normal.

EDIT: I'm aware that GCC 5.2 is out. This will be addressed when I return.

Last edited by clfarron4 (2015-07-27 11:32:37)

beaker23 · 2015-10-31 00:01:37

After adding:

[linux-ck-pax]
Server = http://dl.dropbox.com/u/298301785/arch/ … -pax/$arch

to my /etc/pacman.conf and running:

sudo pacman --sync linux-ck-pax

I keep getting:

warning: database file for 'linux-ck-pax' does not exist
error: target not found: linux-ck-pax

The linux-tresor repo worked fine, just wanted to try out the ck-pax version, am I missing something?

clfarron4 · 2015-11-01 15:46:59

beaker23 wrote:

After adding:
[linux-ck-pax]
Server = http://dl.dropbox.com/u/298301785/arch/ … -pax/$arch
to my /etc/pacman.conf and running:
sudo pacman --sync linux-ck-pax
I keep getting:
warning: database file for 'linux-ck-pax' does not exist
error: target not found: linux-ck-pax
The linux-tresor repo worked fine, just wanted to try out the ck-pax version, am I missing something?

Hi, I don't know what is going on, because it's quite random as to whether you can actually access them or not. I've also dropped the package in the AUR as well.

There is the slight issue in that I am currently looking for a new building and hosting service, so these repositories aren't actually being updated at the moment.

Last edited by clfarron4 (2015-11-01 15:47:24)

beaker23 · 2016-02-13 00:35:00

have you moved to a new hosting service? Just curious, any intent to update the tresor kernel?

clfarron4 · 2016-02-14 02:56:44

beaker23 wrote:

have you moved to a new hosting service? Just curious, any intent to update the tresor kernel?

It's going to be later than planned, but Dropbox will be happening at the end of this month.

As for TRESOR, I've got to think about how to do it. Basically, it builds but kernel panics for 3.19+ and haven't gotten around to trying to work out just what is going on.

Arch Linux

#1 2014-09-21 16:00:55

Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#2 2014-09-21 17:04:52

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#3 2014-09-21 22:57:15

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#4 2014-09-21 23:18:55

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#5 2014-10-24 18:32:42

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#6 2014-12-14 14:26:31

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#7 2015-01-20 13:43:01

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#8 2015-03-16 14:23:21

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#9 2015-03-16 14:28:55

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#10 2015-03-16 14:30:37

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#11 2015-03-16 22:41:17

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#12 2015-03-22 21:42:59

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#13 2015-04-13 21:47:34

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#14 2015-04-13 22:00:56

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#15 2015-04-16 21:38:35

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#16 2015-07-24 07:54:03

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#17 2015-10-31 00:01:37

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#18 2015-11-01 15:46:59

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#19 2016-02-13 00:35:00

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

#20 2016-02-14 02:56:44

Re: Unofficial Repository for LTS, ck-pax and TRESOR. x86_64 only

Board footer