e
> commit itself is good enough for this but I personally prefer verbosity.
> It also calls out that it wasn't my work.
>
This sounds more like a reviewed by or acked by?
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5
On 10/24/2016 09:21 AM, Daniel Campbell (zlg) wrote:
> What would you call what I decribed, though; Acked?
Acked-By and/or Reviewed-By (although we don't have a specific
reviewer's statement in Gentoo (yet?))
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-k
builds they
> don't hold copyright on without permission. A DCO would probably help
> with this, which is why that is generally considered a best practice.
>
+1
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
were dropped at some point once ebuilds
> had proper deps. My guess would be ppl wanted to keep them commented
> out just in case it appeared to be a bad idea to drop them and be able
> to "revert" easily. Nowadays, we can probably assume it was ok :)
>
Indeed, to avoi
hether to remove the commented out lines to clean up the packages file.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
t; doing all of this, but I'm sure there is room for improvement (having
> a bug header in the default repoman commit template probably wouldn't
> hurt - then they all look the same and you can always delete it or
> leave it blank if it doesn't apply).
Quality of comm
t know was a 'thing'?
>>
>
> It would be a good thing, especially since this relies on Gentoo
> Prefix (I think), which is a fairly unique capability I've yet to see
> in any other distro.
>
+1
Would certainly like to see a writeup of positive things in a blog
On 10/29/2016 06:22 PM, Benda Xu wrote:
> Kristian Fiskerstrand writes:
>
>
> I will need first to set up a blog and then draft a writeup.
>
> Any hints?
>
You can request a blog from blogs.gentoo.org and ask for it to be
included in planet and universe
--
Kristian
packages
(maintainership) and fixing the issues then. If not, they should be removed.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
7;t properly maintained, they certainly should be removed. if
you want to keep them and have fixes for known issues, take over
maintainership
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
s an example, but it is mostly wrong route
to go on discussion.
tl;dr; A signature by a release key is valuable
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 11/01/2016 04:55 PM, gro...@gentoo.org wrote:
> Any hints please?
This discussion should take place on https://bugs.gentoo.org
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.
<=X-r reliable,
> 1b. to prevent pathological uses of revision as date.
Given revision in most cases is incremental (except for some -r100,
-r200) cases, some structure here is likely good. I take it we're
talking about devmanual changes in this case for policy?
--
Kristian Fisker
ps://archives.gentoo.org/gentoo-dev/message/355f4b4272c0049cffcdec88d815e267
[2]
https://archives.gentoo.org/gentoo-dev/message/1246dd8fabe44e7e7ecf59ecf029af3e
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 11/17/2016 02:47 PM, Michael Palimaka wrote:
> On 18/11/16 00:26, Kristian Fiskerstrand wrote:
>> Strictly speaking GLEP 40 forbids it still, although some arch teams
>> have made announcements to approve it, see e.g [1,2]. I wouldn't be
>> surprised if one of the resu
ackage managers.
* It should be possible to install a package while all MISC entries
have been deleted from the tree.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
too-proxy-ma...@lists.gentoo.org]
https://archives.gentoo.org/gentoo-proxy-maint/
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 12/11/2016 03:13 PM, gro...@gentoo.org wrote:
> gpg: signing failed: Inappropriate ioctl for device
this might indicate a want for export GPG_TTY=$(tty)
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED F
> On 12/21/2016 11:23 PM, i...@gentoo.org wrote:
Why is this email sent using an invalid email addresse in FROM?
As for the rest of the email content itself, please consider the
appropriate forum for any discussion, and I strongly recommend staying
away from personal attacks.
--
Krist
On 12/26/2016 08:45 AM, Andrew Savchenko wrote:
> 8 packages are using either rbd or rados USE flag for Rados
> Block Device support:
Are there other possibly conflicting issues of using "rados" rather than
"rbd" as name (or "radosbd") or someting a bit
>
>> ago suggested "Packages list" or "Package list" - thoughts?
>
> Isn't it rather a list of "ebuilds" or "package versions"? That's the
> term which https://devmanual.gentoo.org/keywording/index.html uses.
${PF}-list? :)
--
lag? Immediately it sounds like it
adds complexity without much gain.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
ikely needs to be made between actively maintained
upstream and actively Gentoo maintained as well. Actively maintained
upstream might not be an issue for a feature complete package, but if it
lacks a Gentoo-maintainer in addition it is worrying.
--
Kristian Fiskerstrand
OpenPGP keyblock reach
vulnerabilities bumping etc, so now we have a branching of processes
depending on project/category selections that needs to be taken into
consideration?
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
13:55
/usr/bin/python -> python-wrapper
additionally the original upgrade, after manually setting the updated
symlink, ended up with a
python-exec: Invalid impl in /etc/python-exec/python-exec.conf: python3.3
How was this allowed into stable?
--
Kristian Fiskerstrand
OpenPG
On 01/21/2017 05:36 PM, Kristian Fiskerstrand wrote:
> This change broke a stable system in my case without any of these features.
without any of these features enabled explicitly...
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5
On 01/21/2017 06:05 PM, Michał Górny wrote:
> On Sat, 21 Jan 2017 17:36:27 +0100
> Kristian Fiskerstrand wrote:
>
..
>>
>> How was this allowed into stable?
>
> I know things like this don't ever happen in your beloved perfect
> corporate world but mista
;> I didn't realise changing this to REQUIRED_USE resulted in a conflict on
>> default profiles, because I (obviously) have a package.use entry for the
>> package.
> I don't see Mike saying you got it wrong here. Reading your email, I
> think you did the right thing.
the maintainer silently making a choice behind their back.
There is an argument to be made for sane defaults in profiles as well as
default IUSE specification in this though to provide a better user
experience, but the underlying mechanism should be explicit.
--
Kristian Fiskerstrand
OpenPGP key
7;ll have to default to legacy behavior.
"
You'll find some more discussion around this in e.g [bug 540006]
References:
[0] http://lwn.net/Articles/521626/
[1] http://www.spinics.net/lists/stable-commits/msg21052.html
[bug 540006] https://bugs.gentoo.org/show_bug.cgi?id=540006
--
Kr
ven the number of packages
involved.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
ad, the fact
> that it is openssh compounds that. +1 for removing the + and
> leaving this optional (default off).
Just to pitch in that as a user I'm in favor of this approach as well.
- --
- ----
Kristian Fiskerstrand
Blog: http://blog.sumpt
for the dependencies.
>
For what it is worth, I completely agree significant changes to stable
ebuilds (hereunder changes to dependencies) should get a revision bump
and go through normal stabilization procedures.
- --
-
Kristian Fiskerstrand
Blog: http://blog.sumptuousca
net-misc/sks package for ~arch is still on
4.8 without any issues on the rest of the servers. Upgrading is
relatively easy, mostly involving cleaning the environment, which will
be re-generated with the updated version.
- --
-
Kristian F
is discussion yet. IMHO a user on
~arch should expect a higher number of rebuilds, it _is_ after all
testing, whereby at the point it reaches stable, the deps are
hopefully more likely to be correct to begin with.
Does anyone have any insight into where these changes most often occur
nPGP Signed:
1024 5f:c3:fe:9a:ac:a7:99:f4:d3:c1:93:4c:52:87:74:28 (DSA)
256 aa:6a:e4:74:1d:73:d2:5a:9f:45:9f:18:55:81:c9:9a (ECDSA)
256 1c:2e:99:7d:c7:f0:bc:3b:a9:fb:d0:3e:2c:2a:79:ba (ED25519)
2048 24:3b:2d:3b:47:ca:7e:62:48:97:49:6a:f5:ad:66:88
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
# Kristian Fiskerstrand (26 Aug 2014)
# Open security bug #386221 (CVE-2010-3353)
# Does not seem actively maintained
# Masked for removal in 30 days
media-sound/cowbell
- --
Kristian Fiskerstrand
Public PGP key 0xE3EDFAE3 at hkp://pool.sks
hope :).
I'm using app-crypt/ekeyd with my entropykeys so can take that one at
least.
>
> We should also consider removing some of the packages listed
> there.
>
> [1]:http://dev.gentoo.org/~mgorny/maintainer-needed.txt
>
- --
Kristian Fiskerstrand
Public PGP key 0xE3
I would expect as much. But my primary argument would be key management
related, it is simply impossible to present a raw copy of our repo to end-users
and have them verify each commit
Original message From: William Hubbs
Date: 7/3/18 17:39 (GMT+01:00) To: gentoo-dev@lists.ge
is less
of a concern now than back in the day.
But there aren't really very strong arguments in favor of ecc, and in
the case of quantum computation there less protection offered from ecc
due to smaller key sizes.
We also keep gnupg 1.4 in tree that does not, and will not, support ecc.
--
e wouldn't want to accept
them for various reasons.
There are good reasons these are not provided in the regular interface
of gnupg, but requires --expert
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3E
prefer 1.4 for its smaller
footprint etc. If we conclude that the git repo is internal and not to
be exposed to end-users per se, but distribution happens in curated git
or rsync I agree it is not an issue.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr
On 07/04/2018 11:09 AM, Michał Górny wrote:
> I honestly don't think Gentoo is the distribution where we let people
> stay with obsolete versions for 'smaller footprint'.
1.4 isn't obsolete, it is still maintained as separate branch upstream.
--
Kristian Fiskerstrand
On 07/04/2018 12:23 PM, Michał Górny wrote:
> -2. Root key and signing subkey of EITHER:
> +2. Root key and a dedicated signing subkey, both of EITHER:
"dedicated" here might be misread to be gentoo-specific, which doesn't
really make much sense.
--
Kristian Fiskerst
On 07/04/2018 12:54 PM, Michał Górny wrote:
> W dniu śro, 04.07.2018 o godzinie 12∶35 +0200, użytkownik Kristian
> Fiskerstrand napisał:
>> On 07/04/2018 12:23 PM, Michał Górny wrote:
>>> -2. Root key and signing subkey of EITHER:
>>> +2. Root key and a dedicated
On 07/04/2018 12:59 PM, Michał Górny wrote:
>
> Or maybe even make a separate point about having a separate signing
> subkey?
>
Right, that is likely also easier to understand.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 30
.
>
As I understand ulm's concern, the issue is with the max 1 year in
combination with this, e.g it effectively prohibits extended a subkey
expiring 2018-12-31 to 2019-12-31 two weeks before, since that exceeds
one year maximum
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hk
On 07/04/2018 11:43 PM, Kristian Fiskerstrand wrote:
> On 07/04/2018 11:28 PM, Michał Górny wrote:
>> W dniu śro, 04.07.2018 o godzinie 23∶12 +0200, użytkownik Ulrich Mueller
>> napisał:
>>>>>>>> On Wed, 04 Jul 2018, Michał Górny wrote:
>>>&g
t;\x2b\x24\x03\x03\x02\x08\x01\x01\x0d" -> 512(* brainpoolP512r1 *)
| "\x2b\x81\x04\x00\x0a" -> 256(* secp256k1 *)
| "\x2b\x06\x01\x04\x01\xda\x47\x0f\x01" -> 256(* Ed25519 *)
| _ -> failwith "Unknown OID"
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 07/05/2018 01:22 AM, Kristian Fiskerstrand wrote:
> that said, I'm not aware of any curves defined with a lower security
> margin than this for OpenPGP in general. The known curves in the
> ecosystem are
known in the ecosystem being the union of rfc4880bis draft and rfc6637
ers to add a dedicated RSA signing key for Gentoo if necessary
> (especially, since someone using ECC could be considered an advanced
> GnuPG user).
If the primary key is ECC, clients not supporting it won't be able to
use the key material even if the signing subkey is RSA.
>
> U
consuming / difficult that it is a problem
to do it once a year? What do you do when certifying/signing other's UIDs?
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
ng it from LDAP
and as such block access to push etc, so it actually is more important
for other aspects of the ecosystem than for us.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
D
w default.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
ease wait for something that benefits
most users, just to give alternatives to a few using non-default sync
mechanism. Securing git distribution is a whole different ballpark.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA
let others answer that. In any case, the point itself (requiring
> SHA-2 digest) makes sense. The RiseUp standard requires all self-
> signatures to be SHA-2, and I was planning on verifying that as well.
>
no, SHA256 in this context is already default, and it doesn't impac
ght not have published a revocation certificate.
the git sync method will need a way to distinguish this for end-users,
but the proper rsync synchronization will be able to trust the data at
the point we say it is OK.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
f
On 07/08/2018 08:10 PM, Rich Freeman wrote:
> Again, the current portage support for git verification doesn't check
> any developer keys.
right, so why would it be material for a news item improving the status
quo for those synching using the official rsync method?
--
Kristian F
s we
go along we need to have proper key rollover procedures so this should
never happen including backup keys.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
r field).
Sounds like a good thing, go for it!
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
'd say
cache is out of the question, whether it is /var/lib or /var/db doesn't
matter too much to me, but it needs to be announced properly ahead of
time to adjust LVM2 volumes etc etc if impacting existing systems... I'd
mostly argue any such change should only affect new systems
--
On 07/18/2018 11:55 AM, Ulrich Mueller wrote:
> I therefore suggest the following scheme:
The full scheme looks good to me
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Descript
onger proper description
can be written in the body of the commit message instead. Potentially
mixed in with multiple commits for different logical changes etc etc.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B
nd RESTRICT="!test? ( test )" in plenty of ebuilds,
disabling the test phase if the use flag is unset altogether.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
thing installed on the system, if not for
> Werror preventing the code from building.
one way to look at it though, is that it is a valuable upstream
contribution that this configuration produces the error, so Gentoo is
contributing to upstream development because of it.
--
Kristian Fisk
On 9/10/18 10:56 PM, Kristian Fiskerstrand wrote:
> On 9/10/18 10:51 PM, Matt Turner wrote:
>> Consider again the bug that started this. The maintainer had not built
>> this configuration. None of the arch teams had built this
>> configuration until I did for the last archite
That it wasn't caught before being stabilized on several arches was
indeed bad, but that likely says more about our stabilization procedures
than the quality of the underlying package's upstream choices.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
On 9/10/18 11:04 PM, Kristian Fiskerstrand wrote:
> On 9/10/18 11:01 PM, Mike Gilbert wrote:
>
>> It's quite a bit harder for a user to remove -Werror from the build
>> system, assuming they can even interpret the error output.
>>
>
> Sure, but at some poin
rries for build system (autotools re-generation that
might make it unsupported upstream etc) ?
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 9/10/18 11:21 PM, Kristian Fiskerstrand wrote:
> On 9/10/18 11:19 PM, Chí-Thanh Christopher Nguyễn wrote:
>> It is indeed an insurmountable task to write code that is warning-free
>> from the beginning across architectures, compiler versions, etc. But
>> that is not t
On 9/10/18 11:31 PM, Rich Freeman wrote:
> For more critical packages (like the example of zfs) whether it
> compiles and installs isn't 1/10th as important as whether it eats my
> data...
exactly
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
en reported. There is a difference
here, and on some level that is up to maintainer privilege to evaluate
the difference.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 11/27/18 9:07 PM, William Hubbs wrote:
> All,
> I just picked a random msg to reply to on the thread.
>
> Here is the updated AUTHORS file I would like to commit.
>
> William
Lets put it on agenda for next council meeting and let the discussion go
until then.
--
Kri
6 seconds
util-linux-2.32-r4: Sun Jul 15 15:51:21 2018: 50 seconds
util-linux-2.33-r1: Sun Jan 6 20:53:29 2019: 46 seconds
util-linux-2.33-r1: Thu Feb 21 22:16:25 2019: 53 seconds
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 51
the catalyst seed chroots I am building/updating.
Its just a a quick way to propagate this wrapper on multiple computers;
# cat /usr/local/bin/emerge_time.sh
#!/bin/bash
if [[ $# < 1 ]]; then
echo "Usage: ${0} ";
exit;
fi
qlop -tHvg "$1"
--
Kristian Fi
stinct signing
subkey, this is one of the expected results of it to begin with.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
interactive mode?
Quite frankly I'd expect a Gentoo Developer to be able to manage the gpg
interface.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
and
certainly something expected not to happen from a Gentoo Dev to begin
with (for primary key material at least)
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
not FTP+expect.
default-key is exactly for config file, for other operations you use
-u/--local-user
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
g, but its not an official communication channel
for Gentoo.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 4/30/19 6:04 PM, Kristian Fiskerstrand wrote:
> On 4/30/19 9:05 AM, Cynede wrote:
>> Right, alike reddit, twitter, facebook and other PR channels. It's
>> "official" because it's controlled by PR Gentoo team,
>
> No, that does not make anything officia
it is
controlled by Gentoo. But this is where you get into semantic discussions.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
team runs it', '8 Gentoo developers have admin
> rights', 'i.e. it is sanctioned by the project itself'. I was suggested
> that if it's not official, we should close it instead.
If that is how it is perceived I'd be in favor of outright closing it at
entoo and causing a
negative reputation as in the article in this thread. One some level
that actually goes to trademark infringement that should be of interest
to the foundation, but the issue is broader than that.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
y a reasonable person, which the author of the article doesn't
sound like, but the article doesn't provide sufficient information for
third parties to judge per se.
I guess a more interesting question is why communication is increasingly
fragmented across multiple chat systems; it reminds me of
On 4/30/19 7:32 PM, Matthew Thode wrote:
> One thing that may help is to have multiple levels of control defined.
Indeed, this distinction is interesting.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED F
al packages.
>
> [1] https://docs.syncthing.net/advanced/folder-uselargeblocks.html
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
emerge --unmerge consolekit
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
n them with me.
I can join on
>> app-crypt/gpgme
>> dev-libs/libassuan
>> dev-libs/libgpg-error
>> dev-libs/libksba
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
signature.asc
Description: OpenPGP digital signature
On 08.01.2020 22:16, Mikle Kolyada wrote:
> These are up for grabs due to the crypto@ project being disbanded.
>
> app-eselect/eselect-pinentry
I'll take this as well.
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109
On 08.01.2020 22:16, Mikle Kolyada wrote:
> These are up for grabs due to the crypto@ project being disbanded.
Going over the list once more, I'll also take
> app-crypt/nasty
> dev-libs/npth
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
up earlier in this thread, although
that as well seems to be under a more restrictive AGPL-3 license).
- --
Kristian Fiskerstrand
Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJUhLI0A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/07/2014 10:05 PM, Tim Harder wrote:
> On 2014-12-07 15:02, Kristian Fiskerstrand wrote:
>>>> The most important consumer is app-text/pdftk Unfortunately,
>>>> there is still no replacement for the latter which work
>> package that was being masked is no longer in the tree [1].
>
> Regardless of what repoman says, the mask entry is still useful.
>
> The repoman warning serves as a nice reminder, but please don't
> treat it as policy.
>
My two cents is that this is particularly t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/07/2015 07:48 PM, Kristian Fiskerstrand wrote:
> On 01/07/2015 07:22 PM, Mike Gilbert wrote:
>> On Wed, Jan 7, 2015 at 1:11 PM, William Hubbs
>> wrote:
...
>
>
> My two cents is that this is particularly true f
gs (sign &
certification) and an encryption subkey. In this case you'll want to
add a signing subkey using the "addkey" command of --edit-key to make
a compliant key.
- --
Kristian Fiskerstrand
Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5
rypt 1.6.
Another issue is that DSA key sizes > 1024 bits are part of what is
commonly referred to as DSA2-standard, so this is less interoperable
with older versions.
Newer versions of GnuPG (in the 2.1 branch) won't give algorithm
choice at all unless --full-gen-key is used but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/12/2015 07:29 PM, Rich Freeman wrote:
> On Mon, Jan 12, 2015 at 1:06 PM, Kristian Fiskerstrand
> wrote:
>>
>> One issue with DSA/ElGamal is the requirement for a random k
>> value while signing/encrypting,
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/13/2015 05:58 AM, Andrew Savchenko wrote:
> On Mon, 12 Jan 2015 19:44:46 +0100 Kristian Fiskerstrand wrote:
>> On 01/12/2015 07:29 PM, Rich Freeman wrote:
>>> On Mon, Jan 12, 2015 at 1:06 PM, Kristian Fiskerstrand
>>
icular on servers that are not in my physical
presence (at least without a great deal of travelling). Thankfully
have all servers upgraded to get rid of 2.6 series though :)
- --
Kristian Fiskerstrand
Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5
201 - 300 of 358 matches
Mail list logo
