-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
642 lines (560 loc) · 54.4 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>lxgr's blog</title>
<link rel="stylesheet" href="//blog.lxgr.net/theme/css/main.css" />
<link href="//blog.lxgr.net/feeds/all.atom.xml" type="application/atom+xml" rel="alternate" title="lxgr's blog Atom Feed" />
<!--[if IE]>
<script src="https://html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body id="index" class="home">
<header id="banner" class="body">
<h1><a href="//blog.lxgr.net/">lxgr's blog </a></h1>
<nav><ul>
<li><a href="//blog.lxgr.net/pages/contact.html">Contact</a></li>
<li><a href="//blog.lxgr.net/category/misc.html">misc</a></li>
</ul></nav>
</header><!-- /#banner -->
<aside id="featured" class="body">
<article>
<h1 class="entry-title"><a href="//blog.lxgr.net/posts/2015/04/30/grub-efi-multiboot/">Booting multiple Ubuntu versions with EFI</a></h1>
<footer class="post-info">
<abbr class="published" title="2015-04-30T13:32:00+02:00">
Published: Thu 30 April 2015
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/linux.html">linux</a> <a href="//blog.lxgr.net/tag/software.html">software</a> </p>
</footer><!-- /.post-info --><p>For an upcoming project, I will have to use Ubuntu 14.04, and since I didn't want to downgrade my main Ubuntu install on my laptop, I decided to install the second version on a spare partition of my primary harddisk. Sounds easy, right? That's what I thought too, and I was very wrong.</p>
<p>I expected to be able to simply point the Ubuntu installer to the spare partition and wait for the automatic setup to complete, like I used to when I was using plain old BIOS and MBRs to boot my system. My current laptop, however, supports something called UEFI and Secure Boot, and since the "secure" part piqued my interest, I had decided to give it a try. I have been using this setup for dual-booting Ubuntu and Windows 8 for more than a year without any problems now.</p>
<p>After watching the installer copy all the necessary files of Ubuntu 14.04 to the disk and installing the bootloader, I booted into the new system, and everything worked as expected so far – I saw the new, old 14.04 desktop and was even able to open my main, encrypted 15.04 partition using Nautilus. But when I wanted to boot back into my main system, I realized that something had gone wrong: My 15.04 install didn't show up anywhere in the boot process. Not in the EFI boot menu of my laptop I can access by pressing F12 during the boot process (I used that to boot the Windows, because somehow the secure boot stuff interfered with grub's chain loading), and also not in grub itself – it looked as if the installation had never existed in the first place (except for the fact that I was able to see all of its file in 14.04, of course).</p>
<p>After the initial rush of panic had subsided, I was able to restore the system to its original state by the "usual" process of <a href="http://howtoubuntu.org/how-to-repair-restore-reinstall-grub-2-with-a-ubuntu-live-cd">mounting and chrooting</a> my previous system and executing <code>grub-install</code>. This worked, but now I was not able to boot into the new system anymore, besides executing all those steps again from within the old system. I realized I had to dig into the details of the Linux boot process on EFI (and secure boot) if I wanted to accomplish the triple-boot setup I had in mind. If you are unfamiliar with UEFI, I would recommend you to <a href="https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/">read an introduction</a> before reading the following paragraphs.</p>
<p>The main problem seemed to be that the <code>grub-install</code> utility of both Ubuntu systems (which is also executed from the installer) wrote to the same location – I just didn't know what that location was. I started to dig into the details of the EFI boot process – from previous triple-boot experiments on a Mac I vaguely remembered something about a so-called "EFI system partition" where the initial boot loaders of all installed operating systems are stored, and also that there were some parts of the UEFI configuration that were stored in a non-volatile memory on the mainboard. This is very different from the "legacy" boot process, where the trusty BIOS simply loads a chunk of code stored in the MBR of some disk (which can be configured in the BIOS setup, but usually defaults to a sequence of CD-ROM/USB/primary HDD) and executes it. That process is both simple (it doesn't depend on any stable configuration storage within the PC) and robust (in my experience, it was possible to migrate to a new machine simply by swapping the hard drive!), but is also showing its age – things like a dual-boot setup of uncooperating operating systems quickly become a mess, as everybody who has ever installed Windows after Linux on the same machine probably knows. Additionally, there is no mechanism that allows checking the integrity of the system before it is booted, enabling malware that hooks itself into the boot process and is virtually undetectable by any software or operating system mechanism.</p>
<p>UEFI solves the problem of multiple operating systems by specifying the "EFI system partition", which is basically just a plain old FAT partition with a special partition flag and a standardized folder structure where every operating system on the disk or even machine (more on that later) can store its initial bootloader as an executable file. This is a much more robust and future-proof way of storing the first-stage bootloader than the very limited MBR scheme that basically only allows a single primary bootloader which has to locate and execute all secondary boot loaders of all operating systems on the drive. However, it is unfortunately not enough (at least on my computer!) to just dump a bootloader in the correct location (which would have been a <em>really</em> nice EFI feature!) – the corresponding operating system also has to tell the EFI about the new bootloader (both the EFI disk's UUID it resides on and the path on that disk), which then stores that information in its non-volatile configuration memory (a.k.a. NVRAM).</p>
<p>To sum the EFI boot process up, you need a folder on the EFI system partition containing your operating system's boot loader as an EFI binary (which in turn might be the first stage of a multi-stage boot loader that simply locates and executes its remaining parts) and a pointer (i.e. disk and path) to that file in the NVRAM. In the case of secure boot, the EFI binary will also be signed by some "trusted" entity, which could be your operating system vendor or amusingly Microsoft (even though you aren't actually using their operating system – this is because many hardware vendors opted to include their keys in their firmware, which was cause for much political discussion when secure boot was initially introduced).</p>
<p>Fortunately, <code>grub-install</code> takes care about all of that automatically as long as all the correct flags are supplied to it – but unfortunately, in the case of Ubuntu and secure boot, this only works for a single installation per <em>machine</em> (i.e. <em>not</em> per disk, which kept me puzzling for hours!). I'm no expert on secure boot, but I think that this might not be easily fixable by Ubuntu, depending on how exactly the signature mechanism is implemented.</p>
<p>When invoked with no parameters, Ubuntu's <code>grub-install</code>, on an EFI system, installs its signed bootloader to the EFI system partition that is mounted in <code>/boot/efi</code> (which might or might not be the one you want to use on a multi-disk setup!), in the folder <code>/EFI/ubuntu/</code>. The signed loader consists of a shim signed by Microsoft that subsequently executes the actual EFI loader called <code>grubx64.efi</code> in the same directory. Finally, there is a <code>grub.cfg</code> configuration file which contains a pointer (both as a disk UUID and as a GPT number) to the "regular" grub boot disk, which is usually your Linux root partition (or a separate boot partition if you are using an encrypted root device).</p>
<p>Initially, the problem only seemed to be that both Ubuntu installs were trying to install their bootloader and configuration to the same EFI subdirectory – I thought that if I were to somehow convince <code>grub-install</code> to install the EFI loader to some other subdirectory of <code>/EFI</code>, I would be able to select the Ubuntu I wanted from the EFI boot screen. <code>grub-install</code> conveniently has an option for exactly that; you can either change the value of the <code>GRUB_DISTRIBUTOR</code> variable in <code>/etc/default/grub</code>, or directly supply it using the <code>--bootloader-id</code> parameter. When invoking <code>grub-install</code> this way, you can see that a new folder in <code>/EFI</code> will be created using the supplied name (and registered with the EFI NVRAM). Unfortunately, while I was able to boot from the newly created boot entry, I didn't seem to be able to change the disk that grub was booting from in any way. It took me hours to find out why.</p>
<p>Remember that grub uses the value stored in <code>/EFI/<loadername>/grub.cfg</code> to determine the disk where it will continue loading. With a lot of trial-and-error experimentation, I was finally able to determine that regardless of which boot entry I was using in the EFI boot manager, grub would always read the same grub.cfg from <code>/EFI/ubuntu</code>, <strong>regardless of the actual bootloader location</strong> (i.e. subfolder of <code>/EFI</code>)! This location is actually hardcoded in the <code>grubx64.efi</code> binary, which can be verified by using <code>strings</code> or simply opening it with a hex editor. This means that regardless of the Ubuntu install from which <code>grub-install</code> was executed, only the system that <em>most recently</em> installed the loader in the <em>default location</em> <code>/EFI/ubuntu</code> was actually able to change the partition that grub would boot from. (I think I found out about that hard-coded string from some bug report, which I will try to find and reference here.)</p>
<p>If the hard-coded string is modified to reflect the actual location of the boot entry in the <code>/EFI</code> directory everything works as expected (with secure boot enforcing disabled)! Now why would the Ubuntu team be so stupid to hard-code a string that obviously would better be supplied by a parameter? The answer is secure boot: If you enable signature enforcing in the EFI configuration, the modified bootloader stops working. It seems that the string within the binary is covered in the asymmetric signature Canonical uses to certify their bootloader; they could either modify it (and break all systems where secure boot is enforced) or leave it as it is (and break multi-booting). They seem to have decided on the latter. (Maybe there is also a third way, where the configuration file location could be encoded relative to the binary location, i.e. <code>./grub.cfg</code>, but I don't know enough about EFI to say whether such a thing is possible.)</p>
<p>As I later realized, there is an easier way than modifying the signed grub binary. Since secure boot doesn't work with the modified loader anyway, I tried to invoke <code>grub-install</code> with the <code>--no-uefi-secure-boot</code> parameter and examined the resulting bootloader: Without secure boot, there is only a single EFI executable that is also called <code>grubx64.efi</code> (which confused me to no end, since the other files are <em>not</em> cleaned up by <code>grub-install</code>, and I assumed that the configuration file was still working), but that has a much simpler internal structure and importantly has the boot disk location hardcoded. This wasn't as easy to find as the suspicious <code>/EFI/ubuntu</code> string – it is only some kind of relative disk ID like <code>(,gpt2)</code>, if your boot partition is the second partition of the volume on which the EFI partition resides, but a complete disk UUID if the boot partition is located on a <em>different</em> disk.</p>
<p>Finally, here is the complete guide on how to install two Ubuntu versions on a single disk:</p>
<ul>
<li>Disable secure boot in your EFI settings.</li>
<li>Install the first Ubuntu system on the disk. (If it already exists and you have spare space on your disk, you can obviously skip this.)</li>
<li>
<p>Backup the boot entry of the first disk by reinstalling it from within the system using a different name, without secure boot:</p>
<div class="highlight"><pre>grub-install --bootloader-id=myfirstubuntu --no-uefi-secure-boot
</pre></div>
</li>
<li>
<p>Install the second system using the regular Ubuntu installer where you want it. This will break the boot entry of the first system called <code>ubuntu</code>, but not the backup you just created.</p>
</li>
<li>Boot the second system and create a backup of the bootloader, e.g. <code>grub-install --bootloader-id=mysecondubuntu --no-uefi-secure-boot</code></li>
<li>(only if you want to primarily boot the first system) Boot the first system using your computer's EFI boot menu and execute <code>grub-install</code> without any parameters.</li>
</ul>
<p>Congratulations, you now have <em>two</em> Ubuntus running on a single machine!</p>
<p>If you want to use a similar setup, but using more than one disk, you can basically use the same steps if you don't mind that the same EFI partition of the first disk will be used for both systems, which means that you can never format or remove that disk without also disrupting the system on the other disk. grub will just put a pointer to the second disk in its binary that is executed from the EFI partition on the first disk, which should theoretically even survive partition and disk renumbering (but don't count on it!).</p>
<p>If that is a problem for you, there is also the possibility of using a second EFI partition on the second disk, but the Ubuntu installer will make your life even harder by stubbornly insisting to use the EFI partition on the first disk; I was able to solve this only by creating a backup of the first system's bootloader as described above, installing the second system, mounting the second EFI partition in <code>/boot/efi</code> instead of the first one and rerunning <code>grub-install --bootloader-id=...</code>.</p>
<p>You can verify if everything has been setup as you want it by examining the EFI directory on the EFI system partition(s) on your disk(s) as well as the output of <code>efibootmgr -v</code>, which lists the content of the boot list in the EFI NVRAM.</p>
<p>There is also an option <code>--removable</code> which supposedly sets up the EFI directory on a removable device, which looks a bit different than for internal devices and importantly doesn't create an NVRAM entry (which wouldn't be available on different machines anyway). You might be able to use that to boot from an internal disk too, but I have not tried that approach, however.</p>
<p>Of course, if that sounds like a lot of headache and your computer still supports the legacy BIOS boot process (a.k.a CSM in EFI parlance), you can just install the second system on a different disk with an MBR bootloader and configure your EFI for both CSM and EFI booting if it supports that; then you can just select the EFI entry of the first system or the second disk (which will start the second system's boot loader) in the EFI boot menu.</p>
<p>Let me know if you actually made it through that big wall of text and were able to solve your EFI boot problems in the comments!</p>
<h1>Update (2015-12-11):</h1>
<p>There is an <a href="https://www.kubuntuforums.net/archive/index.php/t-68588.html">interesting discussion</a> about the whole topic in the Kubuntu forums. Apparently, it should also be possible to use multiple EFI partitions to get multiple instances of Ubuntu working with secure boot. Thanks for that idea, and sorry for being unreachable. I will probably have to add my mail address here sometime. In the meantime, you can try "me" at lxgr dot net.</p><p>There are <a href="//blog.lxgr.net/posts/2015/04/30/grub-efi-multiboot/#disqus_thread">comments</a>.</p> </article>
</aside><!-- /#featured -->
<section id="content" class="body">
<h1>Other articles</h1>
<hr />
<ol id="posts-list" class="hfeed">
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2015/04/27/chrome-linux-vsync/" rel="bookmark"
title="Permalink to How to fix video tearing on Chrome/Chromium and Compiz">How to fix video tearing on Chrome/Chromium and Compiz</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2015-04-27T18:27:00+02:00">
Published: Mon 27 April 2015
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/graphics.html">graphics</a> <a href="//blog.lxgr.net/tag/software.html">software</a> <a href="//blog.lxgr.net/tag/linux.html">linux</a> </p>
</footer><!-- /.post-info --> <p>One thing I really like about Netflix is their excellent device and browser support. Unlike a certain other streaming service (the one from the company also selling books and clouds), which wouldn't allow watching their streams using an Android tablet (bizarrely, smartphones were somehow allowed...?) and requires Flash and ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2015/04/27/chrome-linux-vsync/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2015/04/27/chrome-linux-vsync/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2014/05/15/vim-tmux-startup-delay/" rel="bookmark"
title="Permalink to vim and that weird one-second startup delay">vim and that weird one-second startup delay</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2014-05-15T20:16:00+02:00">
Published: Thu 15 May 2014
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/linux.html">linux</a> <a href="//blog.lxgr.net/tag/software.html">software</a> </p>
</footer><!-- /.post-info --> <p>Are you using <code>vim</code>, <code>tmux</code>, a graphical Linux desktop and are you experiencing random sluggishness when starting your editor? If not, you can skip this one.</p>
<p>This is something that had been bugging me for ages, first at work on my workstation, then at home: Long-running <code>tmux</code> sessions would sporadically ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2014/05/15/vim-tmux-startup-delay/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2014/05/15/vim-tmux-startup-delay/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2014/05/12/on-agents-and-keychains-part3/" rel="bookmark"
title="Permalink to On agents and keychains (Part 3)">On agents and keychains (Part 3)</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2014-05-12T21:40:00+02:00">
Published: Mon 12 May 2014
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/security.html">security</a> </p>
</footer><!-- /.post-info --> <p>In the previous posts of this series, I've <a href="//blog.lxgr.net/posts/2014/05/10/on-agents-and-keychains-part1/">described the operating environment</a> of a password or private key agent and <a href="//blog.lxgr.net/posts/2014/05/11/on-agents-and-keychains-part2/">given a summary of their tasks</a>. This time, we'll see how some real-world agents are implemented.</p>
<p>But before that, a disclaimer: I'm merely an interested observer of ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2014/05/12/on-agents-and-keychains-part3/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2014/05/12/on-agents-and-keychains-part3/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2014/05/11/on-agents-and-keychains-part2/" rel="bookmark"
title="Permalink to On agents and keychains (Part 2)">On agents and keychains (Part 2)</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2014-05-11T13:19:00+02:00">
Published: Sun 11 May 2014
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/security.html">security</a> </p>
</footer><!-- /.post-info --> <p>In the <a href="//blog.lxgr.net/posts/2014/05/10/on-agents-and-keychains-part1/">previous post</a> of this series, I've roughly described the operating environment of a password or private key agent; this time, I'll try to summarize the basic structure and tasks of such an agent.</p>
<h1>Part 2: What does an agent do?</h1>
<p>The job of a password or ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2014/05/11/on-agents-and-keychains-part2/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2014/05/11/on-agents-and-keychains-part2/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2014/05/10/on-agents-and-keychains-part1/" rel="bookmark"
title="Permalink to On agents and keychains (Part 1)">On agents and keychains (Part 1)</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2014-05-10T14:22:00+02:00">
Published: Sat 10 May 2014
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/security.html">security</a> </p>
</footer><!-- /.post-info --> <p>Many people, myself included, use tools like ssh-agent or gpg-agent to protect their private keys from theft without sacrificing the convenience of password-less logins. Presumably even more people use some kind of password manager, whether that is the one included with their operating system or a third-party one. I've ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2014/05/10/on-agents-and-keychains-part1/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2014/05/10/on-agents-and-keychains-part1/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2014/05/08/ssh-agent-osx-keychain/" rel="bookmark"
title="Permalink to ssh-agent and the OS X Keychain">ssh-agent and the OS X Keychain</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2014-05-08T16:06:00+02:00">
Published: Thu 08 May 2014
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/security.html">security</a> <a href="//blog.lxgr.net/tag/osx.html">osx</a> </p>
</footer><!-- /.post-info --> <p>Are you relying on OS X's Keychain to protect your SSH key passphrases? You
shouldn't. (The "plain" ssh-agent is fine, though.)</p>
<p>To be continued!</p>
<a class="readmore" href="//blog.lxgr.net/posts/2014/05/08/ssh-agent-osx-keychain/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2014/05/08/ssh-agent-osx-keychain/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/11/18/nsswitch-ubuntu-slow-dns-lookups/" rel="bookmark"
title="Permalink to How to fix slow DNS lookups on Ubuntu">How to fix slow DNS lookups on Ubuntu</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-11-18T22:03:00+01:00">
Published: Mon 18 November 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/network.html">network</a> <a href="//blog.lxgr.net/tag/linux.html">linux</a> <a href="//blog.lxgr.net/tag/dns.html">dns</a> </p>
</footer><!-- /.post-info --> <p>If you're using a relatively recent version of Ubuntu, chances are that you have encountered spurious slowdowns that might be related to a very specific DNS failure. For me, it was the fact that <code>ping</code> to a host <em>without</em> a reverse DNS entry would only transmit a single ICMP ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/11/18/nsswitch-ubuntu-slow-dns-lookups/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/11/18/nsswitch-ubuntu-slow-dns-lookups/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/10/24/thoughts-on-cloud-password-sync/" rel="bookmark"
title="Permalink to Thoughts on a cloud-based password synchronization service">Thoughts on a cloud-based password synchronization service</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-10-24T16:15:00+02:00">
Published: Thu 24 October 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/security.html">security</a> </p>
</footer><!-- /.post-info --> <p>Today, Apple has enabled its cloud-based password synchronization service, iCloud Keychain. The service promises to safely store and synchronize passwords and other sensitive user data like credit card numbers among multiple devices. Apple claims that the information is protected with AES, but that alone is meaningless without knowing where that ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/10/24/thoughts-on-cloud-password-sync/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/10/24/thoughts-on-cloud-password-sync/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/08/30/deterministic-dsa-signatures-openssl/" rel="bookmark"
title="Permalink to Safe deterministic (EC)DSA signatures are coming to OpenSSL">Safe deterministic (EC)DSA signatures are coming to OpenSSL</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-08-30T00:37:00+02:00">
Published: Fri 30 August 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/security.html">security</a> </p>
</footer><!-- /.post-info --> <p>By now, everybody involved in implementing algorithms using the DSA or the ECDSA signature schemes should <em>really</em> understand <a href="http://tools.ietf.org/html/rfc6979">the importance of a proper secret nonce</a> as one of the inputs for a signature.</p>
<p>This is easy to get wrong, both because PRNGs <a href="http://www.debian.org/security/2008/dsa-1571">are</a> <a href="http://kakaroto.homelinux.net/2012/01/how-the-ecdsa-algorithm-works/">really</a>, <a href="http://jbp.io/2013/08/15/android-securerandom-guess/">really</a>, <a href="http://android-developers.blogspot.com/2013/08/some-securerandom-thoughts.html">really</a> <a href="http://armoredbarista.blogspot.com/2013/03/randomly-failed-weaknesses-in-java.html">hard</a> to get right ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/08/30/deterministic-dsa-signatures-openssl/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/08/30/deterministic-dsa-signatures-openssl/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/08/27/tls-client-certs-safari/" rel="bookmark"
title="Permalink to TLS client certificates and Mobile Safari">TLS client certificates and Mobile Safari</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-08-27T16:02:00+02:00">
Published: Tue 27 August 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/security.html">security</a> <a href="//blog.lxgr.net/tag/ios.html">ios</a> </p>
</footer><!-- /.post-info --> <p><strong>Update (2013-08-31):</strong> Apple has asked me to refrain from publishing any details on this security-relevant bug for the time being; I hope that a fix will be released soon. When that happens (or after a reasonable amount of time has passed), the original post will be restored.</p>
<p>Until then, I ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/08/27/tls-client-certs-safari/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/08/27/tls-client-certs-safari/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/08/15/android-securerandom-not-even-nonce/" rel="bookmark"
title="Permalink to Android's SecureRandom - not even nonce">Android's SecureRandom - not even nonce</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-08-15T15:30:00+02:00">
Published: Thu 15 August 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/security.html">security</a> <a href="//blog.lxgr.net/tag/android.html">android</a> </p>
</footer><!-- /.post-info --> <p>There has been a bit of drama about the <a href="https://bitcointalk.org/index.php?topic=271486.0">theft of some 55 Bitcoins</a> (worth about $5500 at the current exchange rate), with the common denominator that all of the corresponding private keys were stored in Android wallets. While this is not nearly the first case of Bitcoin theft, it ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/08/15/android-securerandom-not-even-nonce/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/08/15/android-securerandom-not-even-nonce/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/05/20/uninitialized-buffers-in-opengl/" rel="bookmark"
title="Permalink to Uninitialized buffers in OpenGL">Uninitialized buffers in OpenGL</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-05-20T21:25:00+02:00">
Published: Mon 20 May 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/gpu.html">gpu</a> <a href="//blog.lxgr.net/tag/linux.html">linux</a> <a href="//blog.lxgr.net/tag/drivers.html">drivers</a> <a href="//blog.lxgr.net/tag/opengl.html">opengl</a> </p>
</footer><!-- /.post-info --> <p>As I've mentioned in my last article, I'm interested in the implementation details and the security of open and closed-source GPU drivers.</p>
<p>In addition to the security implications of the model that is used by some of the current drivers (they allow the OpenGL client to send commands ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/05/20/uninitialized-buffers-in-opengl/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/05/20/uninitialized-buffers-in-opengl/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/05/10/graphics-processing-hardware-software/" rel="bookmark"
title="Permalink to Graphics processing in hardware and software">Graphics processing in hardware and software</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-05-10T20:23:00+02:00">
Published: Fri 10 May 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/gpu.html">gpu</a> <a href="//blog.lxgr.net/tag/hardware.html">hardware</a> <a href="//blog.lxgr.net/tag/linux.html">linux</a> <a href="//blog.lxgr.net/tag/drivers.html">drivers</a> </p>
</footer><!-- /.post-info --> <p>I've got a peculiar hobby: I like to worry about very specific implementation details of technologies I don't really understand at all; one of them being GPUs and graphics drivers.</p>
<p>On one hand, it's really simple: In almost every computing device, there is a GPU. This is ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/05/10/graphics-processing-hardware-software/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/05/10/graphics-processing-hardware-software/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/05/10/a-quine-in-x86-64-assembly/" rel="bookmark"
title="Permalink to A quine in x86-64 assembly">A quine in x86-64 assembly</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-05-10T17:30:00+02:00">
Published: Fri 10 May 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/programming.html">programming</a> <a href="//blog.lxgr.net/tag/assembler.html">assembler</a> </p>
</footer><!-- /.post-info --> <p>This summer term, I'm taking a really interesting course on computer security: While the lectures are pretty theoretical (one of the topics is a proof that shows that proving the general security properties of certain models is equivalent to the halting problem, which is done by implementing a turing ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/05/10/a-quine-in-x86-64-assembly/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/05/10/a-quine-in-x86-64-assembly/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/04/12/jumboframes-on-the-internet/" rel="bookmark"
title="Permalink to Jumboframes on the Internet?">Jumboframes on the Internet?</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-04-12T11:43:00+02:00">
Published: Fri 12 April 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/network.html">network</a> <a href="//blog.lxgr.net/tag/linux.html">linux</a> </p>
</footer><!-- /.post-info --> <p>Recently, I've been experimenting with Wireshark for my bachelor's thesis, monitoring the performance of TCP uploads from my notebook to my web server. A while ago, I had also swapped my router for a nicer model capable of gigabit ethernet and 5 GHz wifi (due to increasing congestion ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/04/12/jumboframes-on-the-internet/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/04/12/jumboframes-on-the-internet/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/03/29/vpn-ipv6-part2/" rel="bookmark"
title="Permalink to VPNs and IPv6, part 2">VPNs and IPv6, part 2</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-03-29T17:28:00+01:00">
Published: Fri 29 March 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/vpn.html">vpn</a> <a href="//blog.lxgr.net/tag/network.html">network</a> <a href="//blog.lxgr.net/tag/linux.html">linux</a> <a href="//blog.lxgr.net/tag/security.html">security</a> </p>
</footer><!-- /.post-info --> <p>As I've <a href="//blog.lxgr.net/posts/2013/03/06/vpn-circumvention-ipv6/">written before</a>, VPNs can lead to insecure situations when used with IPv6 enabled networks.</p>
<p>The easiest way to mitigate that problem is actually just to enable IPv6 tunneling over the VPN itself, provided your VPN gateway has IPv6 connectivity and you have a spare /64 subnet you ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/03/29/vpn-ipv6-part2/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/03/29/vpn-ipv6-part2/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/03/15/static-blog-http-caching/" rel="bookmark"
title="Permalink to Static blogs and HTTP caching">Static blogs and HTTP caching</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-03-15T10:56:00+01:00">
Published: Fri 15 March 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/web.html">web</a> <a href="//blog.lxgr.net/tag/blog.html">blog</a> <a href="//blog.lxgr.net/tag/caching.html">caching</a> </p>
</footer><!-- /.post-info --> <p>As you can see in the footer, this blog is powered by <a href="http://getpelican.com">Pelican</a>, a static blog generator written in Python. It's really simple to use and fits my requirements nicely – I can write posts offline on my notebook and view the results in my browser with the included web ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/03/15/static-blog-http-caching/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/03/15/static-blog-http-caching/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/03/13/variable-indirection-shell-scripts/" rel="bookmark"
title="Permalink to Variable indirection in shell scripts">Variable indirection in shell scripts</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-03-13T15:30:00+01:00">
Published: Wed 13 March 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/shell.html">shell</a> <a href="//blog.lxgr.net/tag/linux.html">linux</a> <a href="//blog.lxgr.net/tag/programming.html">programming</a> </p>
</footer><!-- /.post-info --> <p>Recently, I had to find a way to do variable indirection in a shell script. More specifically, I wanted to write a function that takes two arguments and interprets one of them as a string, and the other one as a variable to which that string should be added – a ...</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/03/13/variable-indirection-shell-scripts/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/03/13/variable-indirection-shell-scripts/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/03/13/tls-rc4-not-so-secure/" rel="bookmark"
title="Permalink to TLS and RC4 - not so secure after all">TLS and RC4 - not so secure after all</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-03-13T11:24:00+01:00">
Published: Wed 13 March 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/cryptography.html">cryptography</a> <a href="//blog.lxgr.net/tag/security.html">security</a> </p>
</footer><!-- /.post-info --> <p>Turns out that TLS with RC4 (which was <a href="http://blog.phonefactor.com/2011/09/23/slaying-beast-mitigating-the-latest-ssltls-vulnerability/">supposed to protect us</a> against the BEAST and the CRIME attacks) is <a href="http://www.isg.rhul.ac.uk/tls/">not so secure after all</a>:</p>
<blockquote>
<p>The attacks arise from statistical flaws in the keystream generated by the RC4 algorithm which become apparent in TLS ciphertexts when the same plaintext is ...</p></blockquote>
<a class="readmore" href="//blog.lxgr.net/posts/2013/03/13/tls-rc4-not-so-secure/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/03/13/tls-rc4-not-so-secure/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/03/08/server-move-graz-vienna/" rel="bookmark"
title="Permalink to Server relocation">Server relocation</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-03-08T11:46:00+01:00">
Published: Fri 08 March 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/hosting.html">hosting</a> <a href="//blog.lxgr.net/tag/network.html">network</a> </p>
</footer><!-- /.post-info --> <p>This weekend, the server on which this blog is hosted will be <a href="http://www.edis.at/de/support-und-service/blog/edis-zieht-um-nach-wien/">moved from Graz to Vienna</a>. If all goes well, there will be a short outage on Saturday evening/night, and much better connectivity afterwards.</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/03/08/server-move-graz-vienna/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/03/08/server-move-graz-vienna/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/03/06/vpn-circumvention-ipv6/" rel="bookmark"
title="Permalink to VPNs and IPv6">VPNs and IPv6</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-03-06T10:31:00+01:00">
Published: Wed 06 March 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/vpn.html">vpn</a> <a href="//blog.lxgr.net/tag/network.html">network</a> <a href="//blog.lxgr.net/tag/linux.html">linux</a> <a href="//blog.lxgr.net/tag/security.html">security</a> </p>
</footer><!-- /.post-info --> <!--- Summary: Inadverted VPN circumvention by IPv6 -->
<p>A while ago, I have configured a small OpenVPN for personal use (mostly for security when using public wireless networks) with <a href="http://openvpn.net/">OpenVPN</a>. The setup is pretty easy, thanks to a <a href="http://wiki.openvpn.eu/index.php/Konfiguration_eines_Internetgateways">very helpful tutorial (in German)</a> and the sensible default settings of OpenVPN itself. (Setting up the certificate infrastructure was a ...</p></!--->
<a class="readmore" href="//blog.lxgr.net/posts/2013/03/06/vpn-circumvention-ipv6/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/03/06/vpn-circumvention-ipv6/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/01/28/my-openwrt-setup/" rel="bookmark"
title="Permalink to My OpenWrt setup">My OpenWrt setup</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-01-28T12:15:00+01:00">
Published: Mon 28 January 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/openwrt.html">openwrt</a> <a href="//blog.lxgr.net/tag/network.html">network</a> <a href="//blog.lxgr.net/tag/linux.html">linux</a> </p>
</footer><!-- /.post-info --> <!--- Summary: My OpenWrt configuration -->
<p>This weekend, I finally reinstalled <a href="https://openwrt.org/">OpenWrt</a> on my home router. I've been using a nightly build for several months now, and it had been working just fine, but unfortunately, the opkg (OpenWrt's package manager) repositories for the nightly builds are updated every few days, and all of the ...</p></!--->
<a class="readmore" href="//blog.lxgr.net/posts/2013/01/28/my-openwrt-setup/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/01/28/my-openwrt-setup/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
<li><article class="hentry">
<header>
<h1><a href="//blog.lxgr.net/posts/2013/01/13/hello/" rel="bookmark"
title="Permalink to Hello">Hello</a></h1>
</header>
<div class="entry-content">
<footer class="post-info">
<abbr class="published" title="2013-01-13T12:00:00+01:00">
Published: Sun 13 January 2013
</abbr>
<address class="vcard author">
By <a class="url fn" href="//blog.lxgr.net/author/lxgr.html">lxgr</a>
</address>
<p>In <a href="//blog.lxgr.net/category/misc.html">misc</a>.</p>
<p>tags: <a href="//blog.lxgr.net/tag/hello.html">hello</a> </p>
</footer><!-- /.post-info --> <!--- Summary: Welcome to my blog -->
<p>This is going to be my new personal blog. Topics will vary from programming and technical stuff to random thoughts about (possibly non-technical) things.</p>
<a class="readmore" href="//blog.lxgr.net/posts/2013/01/13/hello/">read more</a>
<p>There are <a href="//blog.lxgr.net/posts/2013/01/13/hello/#disqus_thread">comments</a>.</p> </div><!-- /.entry-content -->
</article></li>
</ol><!-- /#posts-list -->
</section><!-- /#content -->
<section id="extras" class="body">
<div class="blogroll">
<h2>blogroll</h2>
<ul>
<li><a href="http://docs.notmyidea.org/alexis/pelican/">Pelican</a></li>
</ul>
</div><!-- /.blogroll -->
<div class="social">
<h2>social</h2>
<ul>
<li><a href="//blog.lxgr.net/feeds/all.atom.xml" type="application/atom+xml" rel="alternate">atom feed</a></li>
<li><a href="http://twitter.com/imlxgr">twitter</a></li>
</ul>
</div><!-- /.social -->
</section><!-- /#extras -->
<footer id="contentinfo" class="body">
<address id="about" class="vcard body">
Proudly powered by <a href="http://getpelican.com/">Pelican</a>, which takes great advantage of <a href="http://python.org">Python</a>.
</address><!-- /#about -->
<p>The theme is by <a href="http://coding.smashingmagazine.com/2009/08/04/designing-a-html-5-layout-from-scratch/">Smashing Magazine</a>, thanks!</p>
</footer><!-- /#contentinfo -->
<script type="text/javascript">
var disqus_shortname = 'lxgrblog';
(function () {
var s = document.createElement('script'); s.async = true;
s.type = 'text/javascript';
s.src = 'https://' + disqus_shortname + '.disqus.com/count.js';
(document.getElementsByTagName('HEAD')[0] || document.getElementsByTagName('BODY')[0]).appendChild(s);
}());
</script>
</body>
</html>