Re: HAL

[Lisi Reisz]

On Monday 28 December 2015 02:30:44 Sven Hartge wrote:
> Sven Hartge  wrote:
> > But I see there is a package named libhal1-flash available from
> > Christian Marillat in his deb-multimedia.org repository. It contains the
> > code from https://github.com/cshorler/hal-flash.
>
> Hmm, libhal1-flash is only available for Stretch and Sid. I wonder why.
>
> Maybe you can ask Christian if he could rebuild the package for Jessie.
>
> In the meantime, to get you your TV fix, here are versions of
> libhal1-flash recompiled on Jessie for amd64 and i386:
>
> http://ftp.thm.de/dvzdebian/its-jessie/libhal1-flash_0.3.2-dmo2~its80+1_amd
>64.deb
> http://ftp.thm.de/dvzdebian/its-jessie/libhal1-flash_0.3.2-dmo2~its80+1_i38
>6.deb

Thank you, Sven. :-))  I am sitting here with a broad smile on my face at your 
kindness.  You have really cheered me up - and I needed it this morning!  
I'll report back.

Lisi

Re: Need a calculator that knows about coulombs

[Gener Badenas]

On Wed, Dec 23, 2015 at 9:09 AM, Gene Heskett  wrote:

> Greetings all;
>
> Do we have such a beast?
>
> Thanks.
>
>
There might be some projects in github that does this.


> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Some mill pix are at:
> Genes Web page 
>
>


-- 
Java  and Groovy

Re: HAL

[Sven Hartge]

Nate Bargmann  wrote:

> Does the flashplugin-nonfree package in Jessie not work for you?  It is
> a plugin for Iceweasel/Firefox.  Or do you need something else?

> See also:  https://wiki.debian.org/FlashPlayer/

The problem is not the Flash plugin, but the DRM code that is loaded
from Adobe, which needs libhal.

Grüße,
Sven

-- 
Sigmentation fault. Core dumped.

Re: KTorrent: Turn off computer when finished

[Allan Aguilar]

On 12/28/2015 06:06 AM, Brandon Vincent wrote:
> On Sun, Dec 27, 2015 at 10:20 PM, Allan Aguilar  
> wrote:
>> Hello,
>>
>> Is there a way to set up KTorrent in a way that the computer turns off
>> when all downloads are complete?
> 
> Hi Allan,
> 
> If you go to the "View" menu, there should be a "Plugins" option. One
> of the plugins is "Shutdown" that does what you are looking for.
> 
> Brandon Vincent
> 
> 

That's exactly what I was looking for. Thanks, Brandon. I really
appreciate it.

-- 
Allan Aguilar
allanagui...@riseup.net
https://twitter.com/ailaqua



signature.asc
Description: OpenPGP digital signature

Re: KTorrent: Turn off computer when finished

[Brandon Vincent]

On Sun, Dec 27, 2015 at 10:20 PM, Allan Aguilar  wrote:
> Hello,
>
> Is there a way to set up KTorrent in a way that the computer turns off
> when all downloads are complete?

Hi Allan,

If you go to the "View" menu, there should be a "Plugins" option. One
of the plugins is "Shutdown" that does what you are looking for.

Brandon Vincent

KTorrent: Turn off computer when finished

[Allan Aguilar]

Hello,

Is there a way to set up KTorrent in a way that the computer turns off
when all downloads are complete?

-- 
Allan Aguilar
allanagui...@riseup.net
https://twitter.com/ailaqua



signature.asc
Description: OpenPGP digital signature

Re: Attempt to Move Root

[Stephen Powell]

On Fri, 25 Dec 2015 10:33:56 -0500 (EST), Stephen Powell wrote:
> On Tue, 22 Dec 2015 10:57:41 -0500 (EST), Nicolas George wrote:
>> ...
>> I noticed that LILO seems to be actually capable
>> of finding the sectors for files on LVM.
> 
> In the general case, the sectors of a file on an LVM2 logical volume may
> reside on multiple physical partitions on multiple physical disks.  But if
> all of those disks are addressable via the BIOS, and all of the sectors
> are accessible via the BIOS, then it may be theoretically possible for LILO
> to read the map file, the kernel image file, and the initial RAM file system
> image file from an LVM2 logical volume at boot time.  I guess I was making
> an implicit assumption that they would all have to be on the same physical
> device.  But maybe that's not true.  I'll have to look into that.

Looking at the source package for lilo, in src/geometry.c, I find the following:

if (lbm.lv_dev != geo->base_dev)
die("LVM boot LV cannot be on multiple PVs\n");

Therefore, it appears from a cursory examination that an LVM2 logical volume
may be used for /boot if the logical volume maps to a single
physical volume.  It is not clear to me from this cursory examination whether
this "physical volume" actually means a partition; or if it means a physical 
disk,
which may consist of multiple partitions.  In any case, I would not recommend
putting /boot on an LVM2 logical volume.  It's just one more layer of
complexity, and one more potential thing to go wrong.
  
-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Re: HAL

[Nate Bargmann]

Lisi,

Does the flashplugin-nonfree package in Jessie not work for you?  It is
a plugin for Iceweasel/Firefox.  Or do you need something else?

See also:  https://wiki.debian.org/FlashPlayer/

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us

Re: HAL

[Sven Hartge]

Sven Hartge  wrote:

> But I see there is a package named libhal1-flash available from
> Christian Marillat in his deb-multimedia.org repository. It contains the
> code from https://github.com/cshorler/hal-flash.

Hmm, libhal1-flash is only available for Stretch and Sid. I wonder why.

Maybe you can ask Christian if he could rebuild the package for Jessie.

In the meantime, to get you your TV fix, here are versions of
libhal1-flash recompiled on Jessie for amd64 and i386:

http://ftp.thm.de/dvzdebian/its-jessie/libhal1-flash_0.3.2-dmo2~its80+1_amd64.deb
http://ftp.thm.de/dvzdebian/its-jessie/libhal1-flash_0.3.2-dmo2~its80+1_i386.deb

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: HAL

[Sven Hartge]

Lisi Reisz  wrote:
> On Monday 28 December 2015 00:59:38 Sven Hartge wrote:
>> Lisi Reisz  wrote:

>>> Is there any way I can install HAL in Jessie?  Or do I need to wipe
>>> it, and reinstall Wheezy on the box on which I need HAL?

>> The real question is: "Why do you need HAL?"

> Because, criminal offence though I fully understand it to be, I want
> to use my television to watch UK Channel 4 catch-up TV and Amazon
> Prime Video.  For that I need the computer attached to my television
> to run Flash-player.

> I know that I can get the setup running in Wheezy.  The question is
> whether I can do so it Jessie.  But the stumbling block, I think is
> that I need HAL.

> As I say, I know that such behaviour is a criminal offence, so please,
> people, can we not go there.

Problem is, and I think you know this, HAL has been deprecated since
quite a long time and is no longer available or even compatible with a
reasonably modern Linux system.

But I see there is a package named libhal1-flash available from
Christian Marillat in his deb-multimedia.org repository. It contains the
code from https://github.com/cshorler/hal-flash.

The package description says it is exactly for the purpose you intent to
use it:

,
| Description: Compatibility library to allow playback of flash DRM content
|  The Adobe Flash web browser plugin for Linux relies upon libhal to provide
|  information required by libadobecp (which libflashplayer.so retrieves from
|  the internet) for playing back drm content.
|  
|  Since HAL is no longer centric to most modern Linux systems (now we have
|  UDev, UDisks etc) - I'm only really providing this library because I see a
|  growing trend in the UK: ITV, Lovefilm and others are now using Silverlight
|  rather than Flash for their drm streams. Currently Silverlight DRM
|  protected content isn't supported on Linux (I'd like to see this change - I
|  have nothing against Silverlight).
`

I think this may solve your problems without frankensteining your Debian
installation.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: HAL

[Lisi Reisz]

On Monday 28 December 2015 00:59:38 Sven Hartge wrote:
> Lisi Reisz  wrote:
> > Is there any way I can install HAL in Jessie?  Or do I need to wipe
> > it, and reinstall Wheezy on the box on which I need HAL?
>
> The real question is: "Why do you need HAL?"
>
> Grüße,
> Sven.

Because, criminal offence though I fully understand it to be, I want to use my 
television to watch UK Channel 4 catch-up TV and Amazon Prime Video.  For 
that I need the computer attached to my television to run Flash-player.

I know that I can get the setup running in Wheezy.  The question is whether I 
can do so it Jessie.  But the stumbling block, I think is that I need HAL.

As I say, I know that such behaviour is a criminal offence, so please, people, 
can we not go there.

Lisi

Re: HAL

[Sven Hartge]

Lisi Reisz  wrote:

> Is there any way I can install HAL in Jessie?  Or do I need to wipe
> it, and reinstall Wheezy on the box on which I need HAL?

The real question is: "Why do you need HAL?"

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

HAL

[Lisi Reisz]

Is there any way I can install HAL in Jessie?  Or do I need to wipe it, and 
reinstall Wheezy on the box on which I need HAL?

Lisi

Re: Attempt to Move Root

[Pascal Hambourg]

Sven Hartge a écrit :
> Pascal Hambourg  wrote:
>>> Le duodi 2 nivôse, an CCXXIV, Sven Hartge a écrit :
> 
 And this is why I love the GPT. There is a defined space for the
 bootloader to be and no nether region of swirly unknowness between
 the MBR and the start of the first partition.
> 
>> Note that current partition tools leave a bigger gap than ~31 KB,
>> typically ~1 MB to ensure partition alignment. So on a newer
>> installation you would not face that problem again even with an MSDOS
>> partition table.
> 
> Correct. But that space is still indefined and who knows what tries to
> write data into that place.

You do know, if you only install and run open source software on this
machine. However that comment was just for completeness. I advocate and
favour GPT whenever I can.

Re: Dovecot Problems?

[Anthony DeRobertis]

Presuming you're running stable, I've got 1:2.2.13-12~deb8u1 running and
login from Android clients (K-9, Android 5 and 6) works just fine. I
would suggest using tcpdump to see how far the packets are getting.
Also, IMAP/SSL (as opposed to IMAP + STARTTLS) runs on port 993—make
sure you're not blocking that.

You could also use a telnet client on Android to test, by telnet'ing to
the IMAP port. Some trivial IMAP commands to try are "tag capability"
and "tag logout". Tag can be any tag, including "tag".

Re: Attempt to Move Root

[Sven Hartge]

Pascal Hambourg  wrote:
> Nicolas George a écrit :
>> Le duodi 2 nivôse, an CCXXIV, Sven Hartge a écrit :

>>> And this is why I love the GPT. There is a defined space for the
>>> bootloader to be and no nether region of swirly unknowness between
>>> the MBR and the start of the first partition.

> Note that current partition tools leave a bigger gap than ~31 KB,
> typically ~1 MB to ensure partition alignment. So on a newer
> installation you would not face that problem again even with an MSDOS
> partition table.

Correct. But that space is still indefined and who knows what tries to
write data into that place.

S°

-- 
Sigmentation fault. Core dumped.

Re: Attempt to Move Root

[Nicolas George]

Le septidi 7 nivôse, an CCXXIV, Pascal Hambourg a écrit :
> I repeat : the point is not MBR/MSDOS vs GPT. It is that the GRUB
> installer handles *specially* one type of partition which exists only in
> GPT style : "BIOS Boot" aka "bios_grub".
> 
> Are you talking about the installer code run by grub-install or the
> bootloader code ? I am not aware that the installer code can handle any
> partition type other than the above type in the same way.

I am talking about the installer, of course. The algorithm used is:

1. embed in the disk if possible, otherwise:
2. embed in the filesystem if possible, otherwise:
3. write in a file and print a warning.

It seems that no options are present to control this finely, which means it
will try to use the first method that works, but all the infrastructure is
there.


signature.asc
Description: Digital signature

Re: Attempt to Move Root

[Pascal Hambourg]

Nicolas George a écrit :
> 
> In the meantime, I can tell what I saw in the code, and this is: GRUB makes
> no difference between MBR-style partitions (that it calls internally
> "msdos") and GPT.

I repeat : the point is not MBR/MSDOS vs GPT. It is that the GRUB
installer handles *specially* one type of partition which exists only in
GPT style : "BIOS Boot" aka "bios_grub".

Are you talking about the installer code run by grub-install or the
bootloader code ? I am not aware that the installer code can handle any
partition type other than the above type in the same way.

Re: Attempt to Move Root

[Nicolas George]

Le septidi 7 nivôse, an CCXXIV, Pascal Hambourg a écrit :
> *Cough*
> At least it was supposed to. The more I mess with UEFI implementations,
> the more I feel dubious about its real advantages.

Six messages ago, I wrote "or would be if it was correctly implemented by
vendors"; you read it since you replied to it. Please try to keep up.

> My experience and the documentation I read.

If you manage to find usable documentation for GRUB, please share it.

In the meantime, I can tell what I saw in the code, and this is: GRUB makes
no difference between MBR-style partitions (that it calls internally
"msdos") and GPT.


signature.asc
Description: Digital signature

Re: Digital signatures

[Teemu Likonen]

Anthony Mapes [2015-12-27 09:03:22-05] wrote:

> I do have one question about the MIME version, though. I've seen
> mailing lists that add a footer to each message (in the form of a
> signature). With inline PGP, this footer gets appended after the
> signature block, and everything is wonderful. Would MIME work properly
> with that, since it doesn't seem to explicitly define the start and
> end of the signed message?

I didn't know the answer but I just checked one Mailman-managed mailing
list which adds a footer. In PGP/MIME messages (and probably any MIME
multipart messages) it adds another MIME layer (multipart/mixed). The
original multipart/signed is inside the first part and the mailing list
footer is the second part. At least Gnus and Mutt understand it and give
a "good signature". But I'm sure that old unmaintained mail clients
won't show it nicely.

Below is an example. See the different boundary strings for two
different layers.


From:
To:
Date
Subject:
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="===1041589328404701819=="

--===1041589328404701819==
Content-Type: multipart/signed; boundary="=-=-=";
micalg=pgp-sha256; protocol="application/pgp-signature"

--=-=-=
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

The original message body here.

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

[...]
-END PGP SIGNATURE-
--=-=-=--

--===1041589328404701819==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Mailing list footer here.

--===1041589328404701819==--

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature

Re: Attempt to Move Root

[Gene Heskett]

On Sunday 27 December 2015 09:30:38 Nicolas George wrote:

> Le septidi 7 nivôse, an CCXXIV, Pascal Hambourg a écrit :
> > There was nothing confusing in Sven's message until you mentionned
> > UEFI in response to "I love the GPT". Why did you start talking
> > about UEFI ?
>
> For the early stage of booting, there is no difference between
> MBR-style partitions (it is more accurate and less ambiguous than
> "MSDOS-style") and GPT-style partitions. There are only sectors
> accessed through a BIOS call. Therefore, if something makes booting
> easier, it's not GPT, it's UEFI.
>
> > Could you please give a concrete example ?
> > AFAIK, GRUB cannot use a partition in MSDOS format to store its core
> > image in the same way as it uses a BIOS boot partition in GPT
> > format.
>
> What makes you say that? There is nothing special about GPT
> partitions, they are intervals of sectors, just as MBR-style
> partitions.

I made the mistake of trying to install a wheezy derivitive on a 2T drive 
that had been prepared using GPT partitions.  The installer could not 
see them at all, so after 2 tries, I just let it go ahead and do its own 
partitioning and formatting to ext4. The system has actually worked 
well, on a drive that is said to be too big for MBR.

So I would like to be enlightened as to the real differences between the 
systems. URL's to the proponents sites would be fine.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Attempt to Move Root

[Pascal Hambourg]

Nicolas George a écrit :
> Le septidi 7 nivôse, an CCXXIV, Pascal Hambourg a écrit :
>> There was nothing confusing in Sven's message until you mentionned UEFI
>> in response to "I love the GPT". Why did you start talking about UEFI ?
> 
> For the early stage of booting, there is no difference between MBR-style
> partitions (it is more accurate and less ambiguous than "MSDOS-style") and
> GPT-style partitions. There are only sectors accessed through a BIOS call.

I agree, but a dedicated space on a partition is a safer location than
unallocated disk space or a filesystem.

> Therefore, if something makes booting easier, it's not GPT, it's UEFI.

*Cough*
At least it was supposed to. The more I mess with UEFI implementations,
the more I feel dubious about its real advantages.

>> AFAIK, GRUB cannot use a partition in MSDOS format to store its core
>> image in the same way as it uses a BIOS boot partition in GPT format.
> 
> What makes you say that?

My experience and the documentation I read. If you know a way to have
GRUB install its core image into an arbitrary partition, I'd love to
learn about it.

Re: Attempt to Move Root

[Nicolas George]

Le septidi 7 nivôse, an CCXXIV, Pascal Hambourg a écrit :
> There was nothing confusing in Sven's message until you mentionned UEFI
> in response to "I love the GPT". Why did you start talking about UEFI ?

For the early stage of booting, there is no difference between MBR-style
partitions (it is more accurate and less ambiguous than "MSDOS-style") and
GPT-style partitions. There are only sectors accessed through a BIOS call.
Therefore, if something makes booting easier, it's not GPT, it's UEFI.

> Could you please give a concrete example ?
> AFAIK, GRUB cannot use a partition in MSDOS format to store its core
> image in the same way as it uses a BIOS boot partition in GPT format.

What makes you say that? There is nothing special about GPT partitions, they
are intervals of sectors, just as MBR-style partitions.


signature.asc
Description: Digital signature

Re: Attempt to Move Root

[Pascal Hambourg]

Nicolas George a écrit :
> Le septidi 7 nivôse, an CCXXIV, Pascal Hambourg a écrit :
>> You are confusing GPT (partition table format) and UEFI (firmware and
>> boot interface).
> 
> Quite the contrary, I am trying to de-confuse by using exactly the correct
> terms.

There was nothing confusing in Sven's message until you mentionned UEFI
in response to "I love the GPT". Why did you start talking about UEFI ?

>> Can you tell more ? AFAIK, there is no equivalent to the "BIOS boot"
>> partition in the MSDOS partition scheme.
> 
> What is there to tell more? You create a partition and decide it is for the
> bootloader, period.

Could you please give a concrete example ?
AFAIK, GRUB cannot use a partition in MSDOS format to store its core
image in the same way as it uses a BIOS boot partition in GPT format.
If you're talking about a partition mounted on /boot/grub, it is not the
same at all. If you're talking about another bootloader, please name it.

Re: Digital signatures

[Anthony Mapes]

On 12/27/2015 02:59 AM, Teemu Likonen wrote:
> 
> If we change the subject to digital signatures I think that having the
> signature in a separate MIME part is the modern way. You had the PGP
> signature in the body of the message (and it's fine with me and my mail
> client) but separate MIME parts allow clients to display and save
> different parts correctly.

OK.  I use Engimail with Icedove/Thunderbird, and it warned me that some
mail clients don't properly handle PGP/MIME, but that all clients should
handle inline PGP.  I wasn't sure how many clients out there didn't
accept the MIME version, so I went with inline to be safe.

I do have one question about the MIME version, though.  I've seen
mailing lists that add a footer to each message (in the form of a
signature).  With inline PGP, this footer gets appended after the
signature block, and everything is wonderful.  Would MIME work properly
with that, since it doesn't seem to explicitly define the start and end
of the signed message?

-- 
Anthony Mapes



signature.asc
Description: OpenPGP digital signature

Re: Recovering data from a Raid 1Sata HD

[Pascal Hambourg]

to...@tuxteam.de a écrit :
> 
> On Wed, Dec 23, 2015 at 07:41:00AM -0300, Renaud OLGIATI wrote:
> 
>> Or do I have to first create a (failed) array with mdadm ?
> 
> For RAID 1 it shouldn't be necessary, AFAIR

You cannot mount directly a RAID 1 partition with format 1.1 or 1.2
because the RAID superblock gets in the way. You must mount it with
loop,offset (see my other reply in this thread) or assemble it as a
degraded array and mount the array.

Re: Attempt to Move Root

[Nicolas George]

Le septidi 7 nivôse, an CCXXIV, Pascal Hambourg a écrit :
> You are confusing GPT (partition table format) and UEFI (firmware and
> boot interface).

Quite the contrary, I am trying to de-confuse by using exactly the correct
terms.

> Can you tell more ? AFAIK, there is no equivalent to the "BIOS boot"
> partition in the MSDOS partition scheme.

What is there to tell more? You create a partition and decide it is for the
bootloader, period.

> I beg to differ.
> Upgrading the GRUB package will automatically try to reinstall the
> bootloader it is responsible for. If it fails, it will install the new
> modules in /boot/grub/ and leave the old boot image and core image,
> leading to a version mismatch.
> Also, the grub.cfg config file created by grub-mkconfig or update-grub
> may not be compatible with the bootloader installed by another version
> of GRUB because of changes in syntax or modules.
> 
> Of course you are correct if the GRUB package is not responsible for the
> active bootloader.

Agreed.


signature.asc
Description: Digital signature

Re: Recovering data from a Raid 1Sata HD

[Pascal Hambourg]

Felix Miata a écrit :
> 
> A RAID1 partition normally cannot be mounted as an sdX# device.

It can if the RAID superblock is located at the end of the partition.
I.e. the superblock format is 0.9 (obsolete) or 1.0.

However if the format is 1.1 or 1.2 (default), the superblock is located
at or near the beginning of the partitition and offsets the beginning of
the filesystem, preventing mount to identify it. But the filesystem can
still be mounted with loop, by specifying the offset.

Use "mdadm -E /dev/" to display the superblock format and the
data offset. I don't remember if the offset is in 512-byte sectors, KiB
or other unit. You must multiply the offet with the block size to get
the offset in bytes.

Then mount the filesystem with "-o loop,offset=".

Re: Attempt to Move Root

[Pascal Hambourg]

Nicolas George a écrit :
> Le duodi 2 nivôse, an CCXXIV, Sven Hartge a écrit :
>> And this is why I love the GPT. There is a defined space for the
>> bootloader to be and no nether region of swirly unknowness between the
>> MBR and the start of the first partition.

Note that current partition tools leave a bigger gap than ~31 KB,
typically ~1 MB to ensure partition alignment. So on a newer
installation you would not face that problem again even with an MSDOS
partition table.

> The UEFI boot system is indeed a great improvement, or would be if it was
> correctly implemented by vendors, but do not expect too much of it.

You are confusing GPT (partition table format) and UEFI (firmware and
boot interface).

> You can have already a partition dedicated to the bootloader with old-style
> MBR partitions.

Can you tell more ? AFAIK, there is no equivalent to the "BIOS boot"
partition in the MSDOS partition scheme.

> You seem to be missing something here: there is absolutely no requirement
> that the GRUB version installed as a package on the distribution is the same
> as the version installed as bootloader. You could have left the upgrade
> replace GRUB or even removed the package for GRUB, just leaving the old
> bootloader, that is not a problem.

I beg to differ.
Upgrading the GRUB package will automatically try to reinstall the
bootloader it is responsible for. If it fails, it will install the new
modules in /boot/grub/ and leave the old boot image and core image,
leading to a version mismatch.
Also, the grub.cfg config file created by grub-mkconfig or update-grub
may not be compatible with the bootloader installed by another version
of GRUB because of changes in syntax or modules.

Of course you are correct if the GRUB package is not responsible for the
active bootloader.

> The same thing would have worked with without GPT.

Yes, by leaving a bigger gap between the MBR and the first partition.

> Especially if you use a
> bios_grub partition instead of an EFI system partition.

A bios_grub (actually "BIOS boot") partition without GPT ? Please tell
me more !

Digital signatures

[Teemu Likonen]

Anthony Mapes [2015-12-24 10:38:28-05] wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> While we're on the topic of signatures, what do you consider to be
> good and bad to include in signatures?

If we change the subject to digital signatures I think that having the
signature in a separate MIME part is the modern way. You had the PGP
signature in the body of the message (and it's fine with me and my mail
client) but separate MIME parts allow clients to display and save
different parts correctly. Raw message data looks like this:

From: [...]
To: [...]
Subject: [...]
Date: [...]
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
micalg=pgp-sha256; protocol="application/pgp-signature"

--=-=-=
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Here's the message body.

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

[...]
-END PGP SIGNATURE-
--=-=-=--

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature