Re: talkingarch support off for now
If talkingarch.tk had finger response capability that's another possible location for a valid sha512sum. What I recommend going forward is for users testing with sha512sum they locate each place you have them and compare all of them. Anything different please ask them to write supp...@talkingarch.tk and let them know because something has been defaced and you just got an alert to that deface. File permissions on web pages can provide some protection, but a backup held off the internet so quick restores can be done buys anyone a little version control management capability. On Wed, 23 May 2018, Linux for blind general discussion wrote: > Date: Wed, 23 May 2018 09:16:36 > From: Linux for blind general discussion <blinux-list@redhat.com> > To: blinux-list@redhat.com > Subject: Re: talkingarch support off for now > > Thankfully I haven't had a problem with the website being defaced. But yes, I > can put the sha512sum up there along with signature verification. I think that > it's a good idea in the future to have a signature verification as well as a > sha512sum. A workable fallback is always a good thing. > > Imetumwa kutoka nyumba yangu > > ___ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > > -- ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
Re: talkingarch support off for now
I can verify current image does install I just made it happen over here. Now I have a valid iso I can get an sha512sum that will also be valid. Probably a good idea to put the valid sha512sum up on the web site too so if sigs go squirrely again people can still verify unless web site is defaced. On Wed, 23 May 2018, Linux for blind general discussion wrote: > Date: Wed, 23 May 2018 07:24:13 > From: Linux for blind general discussion <blinux-list@redhat.com> > To: blinux-list@redhat.com > Subject: Re: talkingarch support off for now > > I'm not sure what has happened, but it appears the signature files don't match > for some reason. I think this is the only issue, as I have seen reports that > downloads do in fact work, they just can't be verified. Since my build/test > machine for TalkingArch has officially left us and gone to a better place, I > can't test or build a new release. But I have e-mailed the comaintainer, and > he has agreed to take over builds beginning next month, and will continue to > build for the foreseeable future, until or unless I come across another > machine I can use to build it again. I'll still handle the website and blog, > seed torrents, hang out in the IRC channel and do all the other maintenance > tasks, I just can't build or test now that my wabbit kicked the bucket. Still, > we can look forward to a release in June that should have unbroken signature > verifications. Sorry for the trouble. > > Imetumwa kutoka mtandao wangu > > ___ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > > -- ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
Re: talkingarch support off for now
I'm not sure what has happened, but it appears the signature files don't match for some reason. I think this is the only issue, as I have seen reports that downloads do in fact work, they just can't be verified. Since my build/test machine for TalkingArch has officially left us and gone to a better place, I can't test or build a new release. But I have e-mailed the comaintainer, and he has agreed to take over builds beginning next month, and will continue to build for the foreseeable future, until or unless I come across another machine I can use to build it again. I'll still handle the website and blog, seed torrents, hang out in the IRC channel and do all the other maintenance tasks, I just can't build or test now that my wabbit kicked the bucket. Still, we can look forward to a release in June that should have unbroken signature verifications. Sorry for the trouble. Imetumwa kutoka mtandao wangu ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
Re: talkingarch support off for now
I wonder could it be only the integrity check sigs are broken and not the iso? I could download the current iso direct and torrent and try a couple installations and find out. I have the time to do this too. Curious. On Tue, 22 May 2018, Linux for blind general discussion wrote: > Date: Tue, 22 May 2018 18:20:43 > From: Linux for blind general discussion <blinux-list@redhat.com> > To: blinux-list@redhat.com > Subject: Re: talkingarch support off for now > > Hi > > I'm not sure about bittorrent download, but FWIW I succeeded > in downloading the .iso image from the talking arch website, > and booting it from qemu. I didn't check the integrity. > > -joel > > > It's not possible to download the current version over here with > > bittorrent and get a download that will pass integrity checks for whatever > > reason. I thought torrents weren't supposed to have those problems. > > So I downloaded the last dual boot iso which was 2017-01-01dual.iso and > > was able to go into an installation to the point of the pacstrap command. > > Unfortunately, pacstrap complained that all files were corrupt it > > downloaded and wouldn't do the commit. I wouldn't use this older version > > if the current version could pass integrity checks. The maintainer has > > had a power supply failure on hardware he used to roll new releases so he > > can't fix any of the release problems either. > > Is there a way around these errors one could take and still like > > themselves the morning after? > > > > If I can finish an install successfully the only version of talkingarch > > that will be available until new support comes on line will be the > > 2017-01-01dual.iso unless that too is taken off line. > > The integrity problems happen since the .sig files that come with the iso > > will not verify as good once corresponding public keys get downloaded and > > without good .sig files the iso is impossible to verify as well. > > > > > > > > -- > > > > ___ > > Blinux-list mailing list > > Blinux-list@redhat.com > > https://www.redhat.com/mailman/listinfo/blinux-list > > -- ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
Re: talkingarch support off for now
Hi I'm not sure about bittorrent download, but FWIW I succeeded in downloading the .iso image from the talking arch website, and booting it from qemu. I didn't check the integrity. -joel > It's not possible to download the current version over here with > bittorrent and get a download that will pass integrity checks for whatever > reason. I thought torrents weren't supposed to have those problems. > So I downloaded the last dual boot iso which was 2017-01-01dual.iso and > was able to go into an installation to the point of the pacstrap command. > Unfortunately, pacstrap complained that all files were corrupt it > downloaded and wouldn't do the commit. I wouldn't use this older version > if the current version could pass integrity checks. The maintainer has > had a power supply failure on hardware he used to roll new releases so he > can't fix any of the release problems either. > Is there a way around these errors one could take and still like > themselves the morning after? > > If I can finish an install successfully the only version of talkingarch > that will be available until new support comes on line will be the > 2017-01-01dual.iso unless that too is taken off line. > The integrity problems happen since the .sig files that come with the iso > will not verify as good once corresponding public keys get downloaded and > without good .sig files the iso is impossible to verify as well. > > > > -- > > ___ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list -- Joel Roth ___ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list
