X-Git-Url: https://code.delx.au/refind/blobdiff_plain/a0a4ba44f4dc01c86499c0fc80730940b53f75c6..c1935b0f6d9272cfa51e9a6c1e342c252ea41b1f:/docs/refind/todo.html

diff --git a/docs/refind/todo.html b/docs/refind/todo.html
index 1fc80b0..fdfca00 100644
--- a/docs/refind/todo.html
+++ b/docs/refind/todo.html
@@ -15,7 +15,7 @@
 href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
 <p>Originally written: 3/14/2012; last Web page update:
-10/6/2012, referencing rEFInd 0.4.6</p>
+12/5/2012, referencing rEFInd 0.5.0</p>
 
 
 <p>I'm a technical writer and consultant specializing in Linux technologies. This Web page is provided free of charge and with no annoying outside ads; however, I did take time to prepare it, and Web hosting does cost money. If you find this Web page useful, please consider making a small donation to help keep this site up and running. Thanks!</p>
@@ -195,6 +195,30 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
     <ul>
 
+    <li>When in Secure Boot mode, rEFInd can launch just one driver that's
+	signed with a shim key or MOK. The second and later drivers
+	generate "access denied" errors. <!-- I think this is because of
+	the fast-and-loose sample code I borrowed from shim, which re-uses
+	rEFInd's own image handle (the <tt>image_handle</tt> variable in
+	<tt>start_image()</tt>) for launching shim/MOK-signed binaries. The
+	result is that when the second driver is loaded, it can't register
+	itself with the firmware because the firmware believes it's already
+	been registered. The solution is likely to involve creating a child
+	image handle rather than re-using rEFInd's own image handle, but
+	this is likely to be tedious to do&mdash;see
+	<tt>/usr/local/UDK2010/MyWorkSpace/MdeModulePkg/Core/Dxe/Image/Image.c</tt>
+	for the reference UEFI implementation. --> </li>
+
+    <li>When launching ELILO in Secure Boot mode, ELILO can't find its
+	configuration file. It's possible that a similar problem exists for
+	other boot loaders, too.</li>
+
+    <li>When setting a resolution higher than about 800x600 (or maybe even
+	640x480) in text mode, the text displayed by rEFInd, and on some
+	systems shells and other programs launched from rEFInd, is
+	restricted to an 80x24-character area in the top-left corner of the
+	screen.</li>
+
     <li>The <a href="http://www.rodsbooks.com/gb-hybrid-efi/">Gigabyte
 	Hybrid EFI</a> has a bug that causes the allegedly case-insensitive
 	<tt>StriCmp()</tt> function to perform a case-sensitive comparison.
@@ -246,6 +270,14 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 
     <ul>
 
+    <li>With the arrival of PCs preloaded with Windows 8 and with Secure
+	Boot enabled, some way to cope is in order. I'm thinking of adding
+	code to limit or prohibit booting of unsigned boot loaders if
+	rEFInd detects that Secure Boot is active, and link with the <a
+	href="http://mjg59.dreamwidth.org/18945.html">Shim</a>
+	pre-bootloader to help handle signing and authentication. I need to
+	research the technical details more, though.</li>
+
     <li>EFI supports network boots. rEFInd doesn't, but it would be nice if
 	it would.</li>
 
@@ -320,9 +352,6 @@ href="mailto:rodsmith@rodsbooks.com">rodsmith@rodsbooks.com</a></p>
 	href="http://www.rodsbooks.com/bios2uefi/">DUET</a>). Nonetheless,
 	I'd like to track down the cause and fix it.</li>
 
-    <li>The driver installation procedure could be improved, perhaps by
-        adding support for drivers to the <tt>install.sh</tt> script.</li>
-
     <li>The HFS+ driver returns a volume label of "HFS+ volume", no matter
         what the volume's real label is.</li>