On Fri 22 Dec 2017 6:13 AM, Warren Young wrote:
> On Dec 21, 2017, at 4:57 PM, jungle Boogie wrote:
> >
> > On 21 December 2017 at 15:03, Warren Young wrote:
> >> On Dec 21, 2017, at 2:58 PM, jungle Boogie wrote:
> >>> perhaps left of the username.
> >>
> >> I think right, simply because it’s
On Dec 21, 2017, at 4:57 PM, jungle Boogie wrote:
>
> On 21 December 2017 at 15:03, Warren Young wrote:
>> On Dec 21, 2017, at 2:58 PM, jungle Boogie wrote:
>>> perhaps left of the username.
>>
>> I think right, simply because it’s currently ordered most-clicked to
>> least-clicked, more or l
On Dec 21, 2017, at 4:03 PM, Warren Young wrote:
>
> I’d recommend designing three distinct black-filled SVG icons
Another idea: Unicode may have characters you can use as icons.
Lock: http://www.fileformat.info/info/unicode/char/1f512/
Open: http://www.fileformat.info/info/unicode/char
Thus said Richard Hipp on Thu, 21 Dec 2017 16:46:05 -0500:
> Suppose Fossil were enhanced to show an icon beside each check-in that
> indicated whether or not the check-in had been signed and whether the
> signature had been verified.
Regarding such an enhancement, would it involve configuring
On 21 December 2017 at 15:03, Warren Young wrote:
> On Dec 21, 2017, at 2:58 PM, jungle Boogie wrote:
>>
>> 3) Small green lock, like you see in your browser for https
>> 2) Unlocked & red
>> 1) Locked, but grey
>
> That’s going to make the red-green color blind unhappy:
>
>
> https://en.wiki
On Dec 21, 2017, at 2:58 PM, jungle Boogie wrote:
>
> 3) Small green lock, like you see in your browser for https
> 2) Unlocked & red
> 1) Locked, but grey
That’s going to make the red-green color blind unhappy:
https://en.wikipedia.org/wiki/Color_blindness#Red%E2%80%93green_color_blindness
On 21 December 2017 at 14:16, Richard Hipp wrote:
> On 12/21/17, jungle Boogie wrote:
>>
>> How are the signatures verified?
>
> Signatures are not verified, at the moment.
>
> Probably each repository would have a set of trusted public keys.
> Then as each check-in is received via push (or durin
For what it's worth, I submitted a patch a while back to add S/MIME
support to Fossil's signature scheme. I still apply this patch to Fossil
when I use it. S/MIME uses PKI and is primarily used for non-repdudiation
or encryption in email (every major email client supports it out of the
box).
Forged should be a skull and crossbones. I would think yellow and red
unlocked locks and green locked locks, but definitely with hover text for
those of us with faulty color perception.
On Dec 21, 2017 3:16 PM, "Richard Hipp" wrote:
> On 12/21/17, jungle Boogie wrote:
> >
> > How are the signat
On 12/21/17, jungle Boogie wrote:
>
> How are the signatures verified?
Signatures are not verified, at the moment.
Probably each repository would have a set of trusted public keys.
Then as each check-in is received via push (or during a rebuild) those
with signatures have the signatures verified
On Thu, Dec 21, 2017 at 3:58 PM, jungle Boogie
wrote:
> On 21 December 2017 at 13:46, Richard Hipp wrote:
> > Suppose Fossil were enhanced to show an icon beside each check-in that
> > indicated whether or not the check-in had been signed and whether the
> > signature had been verified. Thus, t
On 21 December 2017 at 13:46, Richard Hipp wrote:
> Suppose Fossil were enhanced to show an icon beside each check-in that
> indicated whether or not the check-in had been signed and whether the
> signature had been verified. Thus, there are three states: (1)
> unsigned, (2) signed but unverifie
Suppose Fossil were enhanced to show an icon beside each check-in that
indicated whether or not the check-in had been signed and whether the
signature had been verified. Thus, there are three states: (1)
unsigned, (2) signed but unverified, and (3) signed and verified.
What would the three icons
13 matches
Mail list logo