* Florian Weimer:
>> * Concern for mips, mips64el, mipsel and ppc64el: no upstream support
>>in GCC
>>(Raised by the GCC maintainer; carried over from stretch)
>
> I'm surprised to read this. ppc64el features prominently in the
> toolchain work I do (thou
* Riku Voipio:
> On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
>> * Niels Thykier:
>>
>> > armel/armhf:
>> >
>> >
>> > * Undesirable to keep the hardware running beyond 2020. armhf VM
>> >s
* Niels Thykier:
> armel/armhf:
>
>
> * Undesirable to keep the hardware running beyond 2020. armhf VM
>support uncertain. (DSA)
>- Source: [DSA Sprint report]
Fedora is facing an issue running armhf under virtualization on arm64:
* Richard Laager:
> Getting back to ZFS and /etc/hostid... I would think that a
> randomly-generated /etc/hostid is probably sufficient. Whether that's
> done in the libc, spl, or zfs package makes no difference to me.
As I tried to explain, the risks of collisions without central
coordination
* Michael Stone:
> Other platforms have deprecated gethostid, that's the best way forward
> for linux, IMO.
I agree. It's the most likely outcome if this issue was reported to
glibc upstream.
* Petter Reinholdtsen:
> [Florian Weimer]
>> That's not very different from /etc/machine-id, isn't it?
>
> Ah, thank you very much for bringing this systemd setting to my
> attention. I was not aware of it.
>
> I agree that it seem very similar in pu
* Petter Reinholdtsen:
> Something like this should work, I guess:
>
> if [ ! -f /etc/hostid ]; then
>if [ -e /sys/class/dmi/id/product_uuid ]; then
>sethostidfromuuid $(cat /sys/class/dmi/id/product_uuid)
>else
> dd if=/dev/urandom bs=1 count=4 of=/etc/hostid 2>/dev/null
>
* Lennart Sorensen:
> There are a lot of 32bit powerpc chips still going into embedded systems
> being built today. They are not going away anytime soon.
Do they implement the ISA required by the existing Debian port?
> In other words, i don't think a s390x box will ever just die.
I'm sure “death” encompasses all events which might lead Debian to
lose access to relevant hardware. It's not just about faults with a
piece of equipment.
* Steven Chamberlain:
Hi,
On 22/05/13 19:46, Florian Weimer wrote:
Sorry for the delay. I'm taking care of this now.
Thank you for the DSA.
I notice a problem though when this was (I think - I'm unsure of the
security team's processes here) copied to the main archive, probably so
* Christoph Egger:
Hi!
Steven Chamberlain ste...@pyro.eu.org writes:
tags 706414 + pending
thanks
I've applied upstream's patch in SVN, I'm running it now on my NFS
server and seems okay.
Christoph, would you be able to do an upload of this to unstable please?
I'm building right now.
* Christoph Egger:
Packages will be in people.d.o:~christoph soon (or shall I upload to
security directly?
Looks good. Please upload to security-master directly. You have to
rebuild with -sa, though, so that the upstream tarball is included in
the upload.
--
To UNSUBSCRIBE, email to
* Roland McGrath:
I can't see why you think --as-needed is fundamentally wrong or unnecessary.
It is fundamentally wrong because -lfoo means I demand that the
initializers of libfoo.so run, whether or not I called anything in it.
So it's more like static linking. 8-)
IMHO, the current
* Axel Beckert:
Both netstat and route fail on squeeze with a 7.2 kernel (route:
writing to routing socket: Invalid argument and netstat: kvm_read:
Bad address).
I think you need to package kernel-specific versions of these tools.
They are there. route is just a (currently too) simple
* Petr Salinger:
If I understand it correctly, the security problem is
it allows remote attackers to guess sensitive values such as IP
fragmentation IDs by observing a sequence of previously generated
values.
By default, the next_value is previous_value+1, i.e. unsecure at all.
It can be
* Jerome Warnier:
While the current status of Debian GNU/kFreeBSD is interesting, I was
quite disappointed there is no ZFS support in it (at least any related
tools).
Any plans to enable this support?
Is ZFS producton-ready? On Solaris, Sun recommends to reformat and
restore from backup
* Florian Weimer:
* Jerome Warnier:
While the current status of Debian GNU/kFreeBSD is interesting, I was
quite disappointed there is no ZFS support in it (at least any related
tools).
Any plans to enable this support?
Is ZFS producton-ready? On Solaris, Sun recommends to reformat
* Guillem Jover:
If the stable release team would be fine with introducing a new source
package to stable then I guess the easiest is to just backport.
I think it most probably should build on etch w/o modifications.
Otherwise from where were you thinking on generating the library
package?
* Thorsten Glaser:
Any progress on the libbsd package, now that licence issues are out
of the way? IIRC, plans were to get it ready for all arches in lenny?
We need a thread-safe version of something like arc4random as an element
for various security patches (which will target etch). Shall we
* Thorsten Glaser:
Florian Weimer dixit:
I'd also see a change that limits the number of bytes which is read from
/dev/urandom (32 or fewer should be enough). I'm concerned about
looping shell scripts darinign entropy from the pool at an unacceptably
high rate.
For things like
* Cyril Brulebois:
About the sbcl package, I never work on bootstrapping, but I'm willing
to try that soon.
Can SBCL still be compiled with CLISP? In that case, it's not a real
bootstrapping exercise, and it might be easier to go that route.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Is the NetBSD port dead? And if it's not, what's the name of the
kernel packages? Does the port use GNU libc?
(Please Cc: me on replies as I'm not subscribed to the mailing list.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
22 matches
Mail list logo
