Re: MD5 password magic numbers
My apologies. I had not thought it through enough, but it isn't a problem that actually affects me anyway. Let me first say that I am completely ignorant as to how MD5 works, but would it be possible to test if the password is a valid MD5 key and then fall back on plain text, doing away with the `--' completely? Or at least keep it compatible with old passwords. Let me add that I am very happy with how the hurd has been coming along lately. I had last looked at it about a year and a half ago, and was pleased with how it worked (flawlessly) and was a little surprised to see some of the features that it now has. I spent the last hour setting my roommate with an NFS-mounted copy of linux. GRUB made it easy. Thanks :) Quoting OKUJI Yoshinori <[EMAIL PROTECTED] > > Do you think that I approved the patch without considering the > possibility? I have been making effort not to break compatibility > unreasonably, and so I approve a patch only if it wouldn't make > anyone's machine unbootable. I'm conservative enough. > > In this case, if you have a password prefixed with `--', your menu > interface will just not be protected by the password. You can boot > menu entries with no problem. And, if you have upgraded GRUB right > now, you should sit in the front of your machine, so you can change > your password to a safe one immediately. Therefore, I decided that the > incompatibility would be acceptable. Ok? > > Okuji > > ___ > Bug-grub mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/bug-grub > - This mail sent through IMP: demo.horde.org ___ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
Re: Hurd port for gcc-7 go PATCH 1-3(15)
On 06.11.2017 16:36, Svante Signell wrote: > Hi, > > Attached are patches to enable gccgo to build properly on Debian > GNU/Hurd on gcc-7 (7-7.2.0-12). Svante, please could you base your patches on upstream trunk, or the gcc-8 packages from experimental, which follow upstream trunk until gcc-8 branches? I think upstream would rather like to see your patches against the current trunk. Thanks, Matthias
Re: Hurd port for gcc-7 go PATCH 1-3(15)
On 06.11.2017 16:36, Svante Signell wrote: > Hi, > > Attached are patches to enable gccgo to build properly on Debian > GNU/Hurd on gcc-7 (7-7.2.0-12). sysinfo.go:6744:7: error: redefinition of 'SYS_IOCTL' const SYS_IOCTL = _SYS_ioctl ^ sysinfo.go:6403:7: note: previous definition of 'SYS_IOCTL' was here const SYS_IOCTL = 0 ^ the patches break the build on any Linux architecture. Please could you test your patches against a linux target as well?
Re: Samuel: Do you have permission to _enable_ the gccgo patches again?
On 27.03.2018 01:42, Samuel Thibault wrote: > Svante Signell, on lun. 26 mars 2018 19:20:04 +0200, wrote: >> On Mon, 2018-03-26 at 19:06 +0200, Samuel Thibault wrote: >>> Svante Signell, on lun. 26 mars 2018 18:50:20 +0200, wrote: >>>> I just saw: >>>> https://anonscm.debian.org/viewvc/gcccvs?view=revision&revision=10084 >>>> >>>> This is really a large step BACK: >>> >>> It's not a step back, it's just fixing something that is completely >>> wrong. >> >> What is really wrong is that Matthias Klose removed the Hurd patches. > > Sure, but see what he wrote in the changlog: he found the patches > "unmaintained", i.e. I guess he got an issue with it, and couldn't > afford spending the time to fix it, and thus just dropped them. That's > only normal for something that hasn't been upstreamed so far. exactly. and you'll see that I updated some of these even before. So no, having a complete port only done in the Debian package is not the best way to do that. And I pinged you several times to do a proper upstream submission. >> Adding them back is a piece of cake for you (or him), see #894080. > > It's not: it means sorting out from your three mails what actually needs > checking in, understanding what you mean by > “ > Finding the reverting commit and applying it > gcc.git-b12c2c48c2c6aa1db9e6c50f6b26330d9caf.patch gcc+gccgo builds > fine again. > ” > whether it's something that needs to be done on top of the patches, > scratching one's head whether “I will report the build status when the > latest version is built. (an eventually provide updated patches)” means > one should wait for that to happen etc. > > Then eventually try to build the whole thing, possibly realize it > doesn't actually build, etc. etc. Not a piece of cake, really. > >>>> Since you could issue that commit to _disable_ >>>> gccgo for Hurd, what about committing to _enable_ gccgo for Hurd instead. >>> >>> Because that would take *way* more time to do, and my current priority >>> is rather glibc. >> >> And why would I help you with glibc upstream? Give me a good reason for that >> :( > > Because if the work there is not done, the Hurd is basically screwed: > glibc will drop the port, which means we'll get way more regressions > etc. Do compare that with just having go working. that's the fate of some ports. Look for kfreebsd instead. If nobody runs the buildds the port is dying. If nobody integrates the kfreebsd patch in openjdk upstream, the patch is dying. Look how m68k is still maintained upstream, and you see floating in patches for go, openjdk, gcc, ... It's the only way to keep these ports alive, not carrying all these patches downstream. Matthias
[Postmaster+auto@ruhr-uni-bochum.de: Virus-Warnung]
Hi *, I'm getting (or better getting not, cause they are infected) emails, which contain the W32.Hybris.gen-Virus. Since I have no idea, from whom this mail originates, I hope all you guys using windoze for mail biz check their machines... Thanks, Matthias - Forwarded message from [EMAIL PROTECTED] - Date: 30 Mar 2001 03:39:54 - From: [EMAIL PROTECTED] To: <[EMAIL PROTECTED]> Subject: Virus-Warnung Unser Standard-Spamcheck hat in einer an Sie gerichteten Mail in den Headern Eigenschaften festgestellt, die darauf hindeuten, dass diese Mail einen Virus enthaelt. Diese Mail wurde Ihnen daraufhin *nicht* zugestellt. Der Return-Path der betroffenen Mail ist [EMAIL PROTECTED] Unsere Kennung des Virus lautet W32.Hybris.gen-Virus. Im WWW finden Sie Informationen unter http://www.ruhr-uni-bochum.de/sec/ , insbesondere zu Happy99 unter http://www.ruhr-uni-bochum.de/sec/happy99.htm Netzinformationen: Happy99 http://members.tripod.com/docsmiley/happy99german.htm Melissa http://www.ciac.org/ciac/bulletins/j-037.shtml VBS/Freelink http://vil.nai.com/vil/vbs10225.asp Bubbleboyhttp://vil.nai.com/vil/vbs10418.asp VBS/Loveletter http://vil.nai.com/villib/dispvirus.asp?virus_k=98617 Bei Fragen koenne Sie auf diese Mail antworten oder sich an unser Servicecenter wenden (Tel. 24025). - End forwarded message - -- +-created at Fri Mar 30 09:08:17 CEST 2001-+ | Matthias Berse Phone:+49-2323-42397 | \Bachstr.28 44625 Herne, GermanyeMail: [EMAIL PROTECTED]/ - longf_ffree;/* free file nodes in fs */ + longf_ffree;/* freie Dateiknoten im Dateisystem */ -- Seen in a translation -BEGIN GEEK CODE BLOCK- GIT/Sd-s:a-C++UL+++P+++L+++W++EN+K?wO-M?V?PS?PE?Y+PGP+t+5+>X+Rtvb+DI+> D+e+++>h*r++y? --END GEEK CODE BLOCK-- ___ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
