Menu
▾
▴
gimp-print-devel
You can subscribe to this list here.
| 2000 |
Jan
(111) |
Feb
(412) |
Mar
(133) |
Apr
(187) |
May
(377) |
Jun
(355) |
Jul
(129) |
Aug
(316) |
Sep
(412) |
Oct
(258) |
Nov
(260) |
Dec
(228) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(291) |
Feb
(497) |
Mar
(341) |
Apr
(105) |
May
(127) |
Jun
(97) |
Jul
(348) |
Aug
(195) |
Sep
(353) |
Oct
(516) |
Nov
(454) |
Dec
(99) |
| 2002 |
Jan
(125) |
Feb
(232) |
Mar
(222) |
Apr
(160) |
May
(147) |
Jun
(97) |
Jul
(199) |
Aug
(275) |
Sep
(411) |
Oct
(355) |
Nov
(371) |
Dec
(326) |
| 2003 |
Jan
(314) |
Feb
(181) |
Mar
(166) |
Apr
(90) |
May
(192) |
Jun
(137) |
Jul
(91) |
Aug
(57) |
Sep
(59) |
Oct
(67) |
Nov
(202) |
Dec
(158) |
| 2004 |
Jan
(67) |
Feb
(81) |
Mar
(142) |
Apr
(124) |
May
(190) |
Jun
(245) |
Jul
(124) |
Aug
(199) |
Sep
(182) |
Oct
(92) |
Nov
(285) |
Dec
(173) |
| 2005 |
Jan
(111) |
Feb
(74) |
Mar
(90) |
Apr
(275) |
May
(133) |
Jun
(106) |
Jul
(215) |
Aug
(142) |
Sep
(131) |
Oct
(135) |
Nov
(75) |
Dec
(76) |
| 2006 |
Jan
(173) |
Feb
(96) |
Mar
(127) |
Apr
(226) |
May
(227) |
Jun
(83) |
Jul
(101) |
Aug
(122) |
Sep
(118) |
Oct
(27) |
Nov
(76) |
Dec
(58) |
| 2007 |
Jan
(204) |
Feb
(137) |
Mar
(115) |
Apr
(50) |
May
(135) |
Jun
(111) |
Jul
(57) |
Aug
(40) |
Sep
(36) |
Oct
(36) |
Nov
(77) |
Dec
(145) |
| 2008 |
Jan
(159) |
Feb
(52) |
Mar
(77) |
Apr
(59) |
May
(80) |
Jun
(105) |
Jul
(119) |
Aug
(225) |
Sep
(58) |
Oct
(173) |
Nov
(64) |
Dec
(94) |
| 2009 |
Jan
(61) |
Feb
(13) |
Mar
(70) |
Apr
(115) |
May
(48) |
Jun
(50) |
Jul
(34) |
Aug
(74) |
Sep
(30) |
Oct
(95) |
Nov
(132) |
Dec
(12) |
| 2010 |
Jan
(40) |
Feb
(22) |
Mar
(10) |
Apr
(5) |
May
(10) |
Jun
(73) |
Jul
(73) |
Aug
(74) |
Sep
(117) |
Oct
(33) |
Nov
(34) |
Dec
(41) |
| 2011 |
Jan
(42) |
Feb
(38) |
Mar
(60) |
Apr
(6) |
May
(26) |
Jun
(52) |
Jul
(16) |
Aug
(21) |
Sep
(49) |
Oct
(48) |
Nov
(64) |
Dec
(121) |
| 2012 |
Jan
(112) |
Feb
(81) |
Mar
(92) |
Apr
(37) |
May
(57) |
Jun
(142) |
Jul
(65) |
Aug
(43) |
Sep
(33) |
Oct
(81) |
Nov
(130) |
Dec
(63) |
| 2013 |
Jan
(63) |
Feb
(32) |
Mar
(80) |
Apr
(48) |
May
(44) |
Jun
(79) |
Jul
(86) |
Aug
(91) |
Sep
(43) |
Oct
(95) |
Nov
(130) |
Dec
(117) |
| 2014 |
Jan
(283) |
Feb
(206) |
Mar
(90) |
Apr
(57) |
May
(105) |
Jun
(66) |
Jul
(87) |
Aug
(30) |
Sep
(54) |
Oct
(125) |
Nov
(45) |
Dec
(36) |
| 2015 |
Jan
(58) |
Feb
(51) |
Mar
(59) |
Apr
(75) |
May
(70) |
Jun
(52) |
Jul
(58) |
Aug
(72) |
Sep
(184) |
Oct
(157) |
Nov
(91) |
Dec
(90) |
| 2016 |
Jan
(89) |
Feb
(61) |
Mar
(57) |
Apr
(86) |
May
(46) |
Jun
(63) |
Jul
(71) |
Aug
(60) |
Sep
(207) |
Oct
(139) |
Nov
(76) |
Dec
(68) |
| 2017 |
Jan
(112) |
Feb
(91) |
Mar
(138) |
Apr
(79) |
May
(36) |
Jun
(20) |
Jul
(105) |
Aug
(71) |
Sep
(51) |
Oct
(114) |
Nov
(148) |
Dec
(79) |
| 2018 |
Jan
(118) |
Feb
(107) |
Mar
(111) |
Apr
(127) |
May
(60) |
Jun
(63) |
Jul
(49) |
Aug
(18) |
Sep
(134) |
Oct
(68) |
Nov
(91) |
Dec
(27) |
| 2019 |
Jan
(41) |
Feb
(63) |
Mar
(37) |
Apr
(42) |
May
(44) |
Jun
(81) |
Jul
(53) |
Aug
(21) |
Sep
(62) |
Oct
(55) |
Nov
(41) |
Dec
(57) |
| 2020 |
Jan
(14) |
Feb
(29) |
Mar
(33) |
Apr
(20) |
May
(19) |
Jun
(9) |
Jul
(5) |
Aug
(23) |
Sep
(30) |
Oct
(29) |
Nov
(58) |
Dec
(139) |
| 2021 |
Jan
(62) |
Feb
(117) |
Mar
(13) |
Apr
(17) |
May
(23) |
Jun
(28) |
Jul
(7) |
Aug
(29) |
Sep
(56) |
Oct
(21) |
Nov
(36) |
Dec
(14) |
| 2022 |
Jan
(10) |
Feb
(28) |
Mar
(18) |
Apr
(19) |
May
(18) |
Jun
(3) |
Jul
(14) |
Aug
(11) |
Sep
(12) |
Oct
(4) |
Nov
|
Dec
(5) |
| 2023 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
(2) |
Jun
(8) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2024 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(51) |
Aug
(31) |
Sep
(10) |
Oct
(14) |
Nov
(12) |
Dec
(14) |
| 2025 |
Jan
(17) |
Feb
(5) |
Mar
(30) |
Apr
(2) |
May
(4) |
Jun
(9) |
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Matt B. <wal...@ma...> - 2020-12-15 02:37:08
|
We have had the macos installer fail on 10.6 both for v5.3.3 and v5.3.4. I have been unable to capture the exact wording of why it failed. I think I found the error message in the Apple Discussions forum. The thread was from 2011 where the poster was trying to use Rescue mode to download and install a clean copy. The operation failed with: " Validation token Timeout and Validation failed....." To the best of my recollection, this is what I saw. Might it be that 10.6 can't handle the newer schemes of authentication? I know that macosx 10.4 can only load a few web pages. I keep getting the message that it couldn't establish a secure connection. I have begun to notice the same on 10.6 but to a much lesser extent. Matt |
|
From: Colin B. <bur...@ya...> - 2020-12-12 11:38:16
|
I've been caught up in the HP - Apple printer driver fiasco but I think I may have made it worse by upgrading to Big Sur operating system. Do you have any driver that might work with this printer / operating system combination? Thanks in anticipation Colin Burrough |
|
From: Michael S. <ms...@ms...> - 2020-12-11 17:15:34
|
Matt, > On Dec 11, 2020, at 12:07 PM, Matt Broughton <wal...@ma...> wrote: > ... > Perhaps we should take a different approach here. I have no ability to test anything between macosx 10.6 and macos 10.14. My previous laptop bit the dust and a big hole opened and limited me to what I can test. Buying a used Mac is a bit costly when I am going to get a new laptop with the M1 chipset after Covid-19 clears out enough that my independent Apple dealer starts selling product again. I've used them since the first B&W models came out. Anyway, I ramble on. It may be that other versions between 10.6 and 10.12 may also be having trouble. Didn't code signing start with 10.13? I believe it was first supported in 10.8 but wasn't made mandatory until 10.13. ________________________ Michael Sweet |
|
From: Matt B. <wal...@ma...> - 2020-12-11 17:14:46
|
> On Dec 11, 2020, at 10:58 AM, Michael Sweet <ms...@ms...> wrote: > > Matt, > >> On Dec 10, 2020, at 9:56 PM, Matt Broughton <wal...@ma...> wrote: >> >> I am starting a new thread for several items. Things were getting lost in the thread 'Looking for testers'. >> >> I was able to try the v5.3.4 -- the notarized version in snapshots -- on a Xerox Phaser 6180n. As expected install and printing was fine. Adding a Generic of any type in macos cannot be done via the Apple System Preferences. The printer ID is matched to any drivers that match it. In the case of my Epson Workforce 1100, the default driver comes up as Epson's driver. I then have a choice to use Epson Workforce 1100 + Gutenprint v5.3.4. >> >> The problem then is that printers don't say that they are 'Generic color laser' printers or the like. This means that there is no way via the GUI to generate a PPD and associate it with the printer. The CUPS web interface lists all of the Gutenprint drivers along with the manufacturer's drivers. Thoughts or solutions? > > The driver matching is based on the 1284DeviceId, Product, and NickName/ModelName strings. A generic driver will only match if the device ID matches, but you can choose "select driver" to get the full list and pick a generic one. > > ________________________ > Michael Sweet Thank you Michael. I think that is the menu I missed. It was one of those afternoons that I couldn't figure out why the computer wasn't seeing the printer. Turns out you have to have the connection to the computer fully inserted. Not my best effort. Matt |
|
From: Matt B. <wal...@ma...> - 2020-12-11 17:08:06
|
> On Dec 10, 2020, at 10:29 PM, Steve Letter <sle...@ya...> wrote: > > My system won’t run anything older than 10.9 Mavericks. I need to find a mini or something to run 10.6 Snow Leopard, probably on eBay. If you see something, feel free to let me know. > > Steve Letter > Sent from my Symbolics Lisp Machine using rmail. Take a look at the Low End Mac site. They don't sell Macs but provide specifications for just about everything produced. They have been around forever: https://lowendmac.com/mac-mini-index/ It looks like you could use a Mac mini produced from Early 2009 through Mid 2010. The great thing is that you can run a Mac mini headless as i sometimes do. Please verify the specs on Low End Mac and then look on eBay. There are a couple of them on there now that would seem to work. You will have to vet the product and seller. >> On Dec 10, 2020, at 9:56 PM, Matt Broughton <wal...@ma...> wrote: >> >> I am starting a new thread for several items. Things were getting lost in the thread 'Looking for testers'. >> >> I was able to try the v5.3.4 -- the notarized version in snapshots -- on a Xerox Phaser 6180n. As expected install and printing was fine. Adding a Generic of any type in macos cannot be done via the Apple System Preferences. The printer ID is matched to any drivers that match it. In the case of my Epson Workforce 1100, the default driver comes up as Epson's driver. I then have a choice to use Epson Workforce 1100 + Gutenprint v5.3.4. >> >> The problem then is that printers don't say that they are 'Generic color laser' printers or the like. This means that there is no way via the GUI to generate a PPD and associate it with the printer. The CUPS web interface lists all of the Gutenprint drivers along with the manufacturer's drivers. Thoughts or solutions? >> > If the printer isn’t matched it shows the entire list and generic can be selected. So I don’t see a problem. Maybe I’m missing your point? As to the Xerox Phaser 8160n, I am going to have to take another look when I can get access to the printer. I must have missed something as the gutenprint/5.3/xml/printers/pcl does list the Xerox Phaser 6180n. I must have missed the pop up menu that has it. I remember now that we scoured all the databases we could find to get a list of pcl laser printers. This is probably a non issue then. >> ********************************* >> >> I also tried to install v5.3.4 under macosx 10.6.x. It barfed just as the v5.3.3 installer did briefly pop up a message indicating an error in the signature. Unfortunately, I can't find it in the system logs. I think it may be time to stop supporting macosx 10.6. It would appear that it will not accept the current method of signing code or the newer certificates are not compatible. Robert, your thoughts? >> >> If we drop macosx 10.6, I have some changes for you Steve. We will need to change the info.plist and the preinstall to reflect the changes. >> >> Matt > > Perhaps a separate build without signing for 10.6? Seriously though, I really need a system running snow leopard to debug this. There should be a fix. Perhaps we should take a different approach here. I have no ability to test anything between macosx 10.6 and macos 10.14. My previous laptop bit the dust and a big hole opened and limited me to what I can test. Buying a used Mac is a bit costly when I am going to get a new laptop with the M1 chipset after Covid-19 clears out enough that my independent Apple dealer starts selling product again. I've used them since the first B&W models came out. Anyway, I ramble on. It may be that other versions between 10.6 and 10.12 may also be having trouble. Didn't code signing start with 10.13? If we are thinking about releasing a separate package for 10.6, why don't we think about releasing a package for 10.6 through 10.12? That might be easier for us to deal with and for our users to follow. Matt |
|
From: Michael S. <ms...@ms...> - 2020-12-11 16:58:43
|
Matt, > On Dec 10, 2020, at 9:56 PM, Matt Broughton <wal...@ma...> wrote: > > I am starting a new thread for several items. Things were getting lost in the thread 'Looking for testers'. > > I was able to try the v5.3.4 -- the notarized version in snapshots -- on a Xerox Phaser 6180n. As expected install and printing was fine. Adding a Generic of any type in macos cannot be done via the Apple System Preferences. The printer ID is matched to any drivers that match it. In the case of my Epson Workforce 1100, the default driver comes up as Epson's driver. I then have a choice to use Epson Workforce 1100 + Gutenprint v5.3.4. > > The problem then is that printers don't say that they are 'Generic color laser' printers or the like. This means that there is no way via the GUI to generate a PPD and associate it with the printer. The CUPS web interface lists all of the Gutenprint drivers along with the manufacturer's drivers. Thoughts or solutions? The driver matching is based on the 1284DeviceId, Product, and NickName/ModelName strings. A generic driver will only match if the device ID matches, but you can choose "select driver" to get the full list and pick a generic one. ________________________ Michael Sweet |
|
From: Steve L. <sle...@ya...> - 2020-12-11 04:29:16
|
My system won’t run anything older than 10.9 Mavericks. I need to find a mini or something to run 10.6 Snow Leopard, probably on eBay. If you see something, feel free to let me know. Steve Letter Sent from my Symbolics Lisp Machine using rmail. > On Dec 10, 2020, at 9:56 PM, Matt Broughton <wal...@ma...> wrote: > > I am starting a new thread for several items. Things were getting lost in the thread 'Looking for testers'. > > I was able to try the v5.3.4 -- the notarized version in snapshots -- on a Xerox Phaser 6180n. As expected install and printing was fine. Adding a Generic of any type in macos cannot be done via the Apple System Preferences. The printer ID is matched to any drivers that match it. In the case of my Epson Workforce 1100, the default driver comes up as Epson's driver. I then have a choice to use Epson Workforce 1100 + Gutenprint v5.3.4. > > The problem then is that printers don't say that they are 'Generic color laser' printers or the like. This means that there is no way via the GUI to generate a PPD and associate it with the printer. The CUPS web interface lists all of the Gutenprint drivers along with the manufacturer's drivers. Thoughts or solutions? > If the printer isn’t matched it shows the entire list and generic can be selected. So I don’t see a problem. Maybe I’m missing your point? > ********************************* > > I also tried to install v5.3.4 under macosx 10.6.x. It barfed just as the v5.3.3 installer did briefly pop up a message indicating an error in the signature. Unfortunately, I can't find it in the system logs. I think it may be time to stop supporting macosx 10.6. It would appear that it will not accept the current method of signing code or the newer certificates are not compatible. Robert, your thoughts? > > If we drop macosx 10.6, I have some changes for you Steve. We will need to change the info.plist and the preinstall to reflect the changes. > > Matt Perhaps a separate build without signing for 10.6? Seriously though, I really need a system running snow leopard to debug this. There should be a fix. |
|
From: Matt B. <wal...@ma...> - 2020-12-11 02:57:01
|
I am starting a new thread for several items. Things were getting lost in the thread 'Looking for testers'. I was able to try the v5.3.4 -- the notarized version in snapshots -- on a Xerox Phaser 6180n. As expected install and printing was fine. Adding a Generic of any type in macos cannot be done via the Apple System Preferences. The printer ID is matched to any drivers that match it. In the case of my Epson Workforce 1100, the default driver comes up as Epson's driver. I then have a choice to use Epson Workforce 1100 + Gutenprint v5.3.4. The problem then is that printers don't say that they are 'Generic color laser' printers or the like. This means that there is no way via the GUI to generate a PPD and associate it with the printer. The CUPS web interface lists all of the Gutenprint drivers along with the manufacturer's drivers. Thoughts or solutions? ********************************* I also tried to install v5.3.4 under macosx 10.6.x. It barfed just as the v5.3.3 installer did briefly pop up a message indicating an error in the signature. Unfortunately, I can't find it in the system logs. I think it may be time to stop supporting macosx 10.6. It would appear that it will not accept the current method of signing code or the newer certificates are not compatible. Robert, your thoughts? If we drop macosx 10.6, I have some changes for you Steve. We will need to change the info.plist and the preinstall to reflect the changes. Matt |
|
From: Michael S. <ms...@ms...> - 2020-12-11 02:32:56
|
All,
Since I've not seen a practical article online about macOS code signing or notarization, I decided to write one:
https://www.msweet.org/blog/2020-12-10-macos-notarization.html
Feedback/comments are welcome!
________________________
Michael Sweet
|
|
From: Steve L. <sle...@ya...> - 2020-12-10 22:30:46
|
I think we have it. I just need a few to give it a try and see if I have it right. It SEEMS right, comparable to your notarized package. Steve Letter Sent from my Symbolics Lisp Machine using rmail. > On Dec 10, 2020, at 4:36 PM, Michael Sweet <ms...@ms...> wrote: > > Steve, > > If you've managed to get the notarization done, just run: > > xcrun stapler staple gutenprint-bla-bla-bla.pkg > > where "bla-bla-bla" is the version number. Then build the disk image. > > This can all be scripted but requires a bunch of identifiers (your Apple ID, your Team ID, the OAuth token you get from the developer.apple.com site) so that the scripts can do their work. Relevant documentation (although in my own workflow I setup a "AC_<TEAMID>" item in the keychain instead of "AC_PASSWORD" since I have multiple development teams I belong to via multiple Apple IDs): > > https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/customizing_the_notarization_workflow#3087720 > > >> On Dec 10, 2020, at 12:05 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >> >> Just to add to the confusion... >> >> Steve Letter >> >> Begin forwarded message: >> >>> From: Apple Developer <no_...@em...> >>> Date: December 9, 2020 at 11:45:59 PM EST >>> To: sle...@ya... >>> Subject: Your Mac software was successfully notarized. >>> >>> >>> >>> Dear Stephen, >>> >>> Your Mac software has been notarized. You can now export this software and distribute it directly to users. >>> >>> Bundle Identifier: my-app.myapp >>> Request Identifier: f3497ee2-5824-46b6-b94d-f6cfd329f61d >>> >>> For details on exporting a notarized app, visit Xcode Help or the notarization guide. >>> Best Regards, >>> Apple Developer Relations >>> >>> >>> >>> >>> TM and © 2018 Apple Inc. >>> One Apple Park Way, MS 301-1TEV, Cupertino, CA 95014. >>> >>> All Rights Reserved | Privacy Policy | Account >>> >> _______________________________________________ >> Gimp-print-devel mailing list >> Gim...@li... >> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel > > ________________________ > Michael Sweet > > > |
|
From: Michael S. <ms...@ms...> - 2020-12-10 21:37:05
|
Steve,
If you've managed to get the notarization done, just run:
xcrun stapler staple gutenprint-bla-bla-bla.pkg
where "bla-bla-bla" is the version number. Then build the disk image.
This can all be scripted but requires a bunch of identifiers (your Apple ID, your Team ID, the OAuth token you get from the developer.apple.com site) so that the scripts can do their work. Relevant documentation (although in my own workflow I setup a "AC_<TEAMID>" item in the keychain instead of "AC_PASSWORD" since I have multiple development teams I belong to via multiple Apple IDs):
https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution/customizing_the_notarization_workflow#3087720
> On Dec 10, 2020, at 12:05 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
>
> Just to add to the confusion...
>
> Steve Letter
>
> Begin forwarded message:
>
>> From: Apple Developer <no_...@em...>
>> Date: December 9, 2020 at 11:45:59 PM EST
>> To: sle...@ya...
>> Subject: Your Mac software was successfully notarized.
>>
>>
>>
>> Dear Stephen,
>>
>> Your Mac software has been notarized. You can now export this software and distribute it directly to users.
>>
>> Bundle Identifier: my-app.myapp
>> Request Identifier: f3497ee2-5824-46b6-b94d-f6cfd329f61d
>>
>> For details on exporting a notarized app, visit Xcode Help or the notarization guide.
>> Best Regards,
>> Apple Developer Relations
>>
>>
>>
>>
>> TM and © 2018 Apple Inc.
>> One Apple Park Way, MS 301-1TEV, Cupertino, CA 95014.
>>
>> All Rights Reserved | Privacy Policy | Account
>>
> _______________________________________________
> Gimp-print-devel mailing list
> Gim...@li...
> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
________________________
Michael Sweet
|
|
From: Steve L. <sle...@ya...> - 2020-12-10 19:16:10
|
Yes, the latest is in snapshots. I deleted the bad one. Steve Letter Sent from my Symbolics Lisp Machine using rmail. > On Dec 10, 2020, at 2:12 PM, Matt <wal...@ma...> wrote: > > > > Sent from my iPad > >>> On Dec 10, 2020, at 12:53 PM, Steve Letter <sle...@ya...> wrote: >>> >> >> Forgot to include my results >> >> Stephens-MacBook-Pro:Desktop sletter$ spctl -a -vvv gutenprint-5.3.4.dmg >> gutenprint-5.3.4.dmg: rejected (the code is valid but does not seem to be an app) >> origin=Developer ID Application: Stephen Letter (63GMK36MRC) >> >> Stephens-MacBook-Pro:Desktop sletter$ spctl -a -vvv -t execute /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg >> /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: rejected (the code is valid but does not seem to be an app) >> origin=Developer ID Application: Stephen Letter (63GMK36MRC) >> >> Stephens-MacBook-Pro:Desktop sletter$ spctl -a -vvv -t install /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg >> /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: accepted >> source=Notarized Developer ID >> origin=Developer ID Installer: Stephen Letter (63GMK36MRC) >> >> Stephens-MacBook-Pro:Desktop sletter$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg >> Executable=/Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg >> Identifier=gutenprint-5 >> Format=generic >> CodeDirectory v=20200 size=172 flags=0x0(none) hashes=1+2 location=embedded >> Signature size=9009 >> Timestamp=Dec 10, 2020 at 1:08:23 PM >> Info.plist=not bound >> TeamIdentifier=63GMK36MRC >> Sealed Resources=none >> Internal requirements count=1 size=172 >> Stephens-MacBook-Pro:Desktop sletter$ >> >> The ones below remain the same. > > Looks good to me. Yay!!! Is that the one in Snapshots? It would be great to get this installed. I am going to test v5.3.4 on a color laser this afternoon if it fires up and prints. It has been sitting idle for at least two years. > > I agree that we make a good team. > Matt > >> >> >> On Thursday, December 10, 2020, 01:41:10 PM EST, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >> >> >> Matt, >> >> Thanks. We make a great team. As you found, I did not sign the package. Doing that gave me results that matched Michael's 5.3.3. I replaced the disk image in snapshots. If you would can find the time I'd appreciate anything more you can do to verify it. >> >> Steve Letter You're never to old to learn something stupid. -- unknown >> >> >> On Thursday, December 10, 2020, 08:34:43 AM EST, Matt Broughton <wal...@ma...> wrote: >> >> >> >> >> > On Dec 9, 2020, at 9:57 PM, Matt Broughton <wal...@ma...> wrote: >> > >> > Try running >> > spctl -a -vvv <path to disk image> and >> > spctl -a -vvv -t execute <path to package> >> > >> > also >> > >> > codesign -dv <path to disk image> and >> > codesign -dv <path to package> >> > >> > That should give you the answer or some indication. >> > >> > I'll try to look at things tomorrow. >> > >> > Matt >> > >> > >> >> On Dec 9, 2020, at 9:13 PM, Steve Letter <sle...@ya...> wrote: >> >> >> >> My understanding, everything underneath gets notarized but that’s why I am asking for testers. >> >> >> >> Steve Letter >> >> Sent from my Symbolics Lisp Machine using rmail. >> >> I am showing that nothing has been notarized. I am a bit confused as to the responce of codesign that the package has not been signed. pkgutil shows that the installer at least has a valid signature >> >> >> Last login: Thu Dec 10 07:07:00 on ttys000 >> Borodin:~ matt$ spctl -a -vvv /Users/matt/Downloads/gutenprint-5.3.4-2.dmg >> /Users/matt/Downloads/gutenprint-5.3.4-2.dmg: rejected >> source=no usable signature >> Borodin:~ matt$ codesign -dv /Users/matt/Downloads/gutenprint-5.3.4-2.dmg >> /Users/matt/Downloads/gutenprint-5.3.4-2.dmg: code object is not signed at all >> Borodin:~ matt$ >> Borodin:~ matt$ >> Borodin:~ matt$ >> >> /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: rejected >> source=no usable signature >> Borodin:~ matt$ >> Borodin:~ matt$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg >> /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: code object is not signed at all >> Borodin:~ matt$ >> >> >> Borodin:~ matt$ >> >> Package "gutenprint-5.3.4.pkg": >> Status: signed by a certificate trusted by Mac OS X >> Certificate Chain: >> 1. Developer ID Installer: Stephen Letter (63GMK36MRC) >> SHA1 fingerprint: 8C 21 B8 23 C2 C7 3F C4 53 F5 A6 2E 98 AE 59 62 52 A3 A0 BF >> ----------------------------------------------------------------------------- >> 2. Developer ID Certification Authority >> SHA1 fingerprint: 3B 16 6C 3B 7D C4 B7 51 C9 FE 2A FA B9 13 56 41 E3 88 E1 86 >> ----------------------------------------------------------------------------- >> 3. Apple Root CA >> SHA1 fingerprint: 61 1E 5B 66 2C 59 3A 08 FF 58 D1 4A E2 24 52 D1 98 DF 6C 60 >> >> Borodin:~ matt$ >> >> >> Matt >> >> >> >> >>> On Dec 9, 2020, at 8:31 PM, Matt <wal...@ma...> wrote: >> >>> >> >>> >> >>>> On Dec 9, 2020, at 1:49 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >> >>>> >> >>>> I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should I upload it to? It is the same build (but different date / time) as the one I uploaded the other day. >> >>>> >> >>>> Steve Letter >> >>> >> >>> I didn’t know you had to sign the disk image. I thought it was only the installer or any code. If the disk image image is notarized, does that also notarize the installer? Do you have the commands to check for notarization? I can always post them. >> >>> Matt >> >> >> > >> _______________________________________________ >> Gimp-print-devel mailing list >> Gim...@li... >> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel |
|
From: Matt <wal...@ma...> - 2020-12-10 19:10:06
|
Sent from my iPad > On Dec 10, 2020, at 12:53 PM, Steve Letter <sle...@ya...> wrote: > > > Forgot to include my results > > Stephens-MacBook-Pro:Desktop sletter$ spctl -a -vvv gutenprint-5.3.4.dmg > gutenprint-5.3.4.dmg: rejected (the code is valid but does not seem to be an app) > origin=Developer ID Application: Stephen Letter (63GMK36MRC) > > Stephens-MacBook-Pro:Desktop sletter$ spctl -a -vvv -t execute /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg > /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: rejected (the code is valid but does not seem to be an app) > origin=Developer ID Application: Stephen Letter (63GMK36MRC) > > Stephens-MacBook-Pro:Desktop sletter$ spctl -a -vvv -t install /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg > /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: accepted > source=Notarized Developer ID > origin=Developer ID Installer: Stephen Letter (63GMK36MRC) > > Stephens-MacBook-Pro:Desktop sletter$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg > Executable=/Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg > Identifier=gutenprint-5 > Format=generic > CodeDirectory v=20200 size=172 flags=0x0(none) hashes=1+2 location=embedded > Signature size=9009 > Timestamp=Dec 10, 2020 at 1:08:23 PM > Info.plist=not bound > TeamIdentifier=63GMK36MRC > Sealed Resources=none > Internal requirements count=1 size=172 > Stephens-MacBook-Pro:Desktop sletter$ > > The ones below remain the same. Looks good to me. Yay!!! Is that the one in Snapshots? It would be great to get this installed. I am going to test v5.3.4 on a color laser this afternoon if it fires up and prints. It has been sitting idle for at least two years. I agree that we make a good team. Matt > > > On Thursday, December 10, 2020, 01:41:10 PM EST, Steve Letter via Gimp-print-devel <gim...@li...> wrote: > > > Matt, > > Thanks. We make a great team. As you found, I did not sign the package. Doing that gave me results that matched Michael's 5.3.3. I replaced the disk image in snapshots. If you would can find the time I'd appreciate anything more you can do to verify it. > > Steve Letter You're never to old to learn something stupid. -- unknown > > > On Thursday, December 10, 2020, 08:34:43 AM EST, Matt Broughton <wal...@ma...> wrote: > > > > > > On Dec 9, 2020, at 9:57 PM, Matt Broughton <wal...@ma...> wrote: > > > > Try running > > spctl -a -vvv <path to disk image> and > > spctl -a -vvv -t execute <path to package> > > > > also > > > > codesign -dv <path to disk image> and > > codesign -dv <path to package> > > > > That should give you the answer or some indication. > > > > I'll try to look at things tomorrow. > > > > Matt > > > > > >> On Dec 9, 2020, at 9:13 PM, Steve Letter <sle...@ya...> wrote: > >> > >> My understanding, everything underneath gets notarized but that’s why I am asking for testers. > >> > >> Steve Letter > >> Sent from my Symbolics Lisp Machine using rmail. > > I am showing that nothing has been notarized. I am a bit confused as to the responce of codesign that the package has not been signed. pkgutil shows that the installer at least has a valid signature > > > Last login: Thu Dec 10 07:07:00 on ttys000 > Borodin:~ matt$ spctl -a -vvv /Users/matt/Downloads/gutenprint-5.3.4-2.dmg > /Users/matt/Downloads/gutenprint-5.3.4-2.dmg: rejected > source=no usable signature > Borodin:~ matt$ codesign -dv /Users/matt/Downloads/gutenprint-5.3.4-2.dmg > /Users/matt/Downloads/gutenprint-5.3.4-2.dmg: code object is not signed at all > Borodin:~ matt$ > Borodin:~ matt$ > Borodin:~ matt$ > > /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: rejected > source=no usable signature > Borodin:~ matt$ > Borodin:~ matt$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg > /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: code object is not signed at all > Borodin:~ matt$ > > > Borodin:~ matt$ > > Package "gutenprint-5.3.4.pkg": > Status: signed by a certificate trusted by Mac OS X > Certificate Chain: > 1. Developer ID Installer: Stephen Letter (63GMK36MRC) > SHA1 fingerprint: 8C 21 B8 23 C2 C7 3F C4 53 F5 A6 2E 98 AE 59 62 52 A3 A0 BF > ----------------------------------------------------------------------------- > 2. Developer ID Certification Authority > SHA1 fingerprint: 3B 16 6C 3B 7D C4 B7 51 C9 FE 2A FA B9 13 56 41 E3 88 E1 86 > ----------------------------------------------------------------------------- > 3. Apple Root CA > SHA1 fingerprint: 61 1E 5B 66 2C 59 3A 08 FF 58 D1 4A E2 24 52 D1 98 DF 6C 60 > > Borodin:~ matt$ > > > Matt > > >> > >>> On Dec 9, 2020, at 8:31 PM, Matt <wal...@ma...> wrote: > >>> > >>> > >>>> On Dec 9, 2020, at 1:49 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: > >>>> > >>>> I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should I upload it to? It is the same build (but different date / time) as the one I uploaded the other day. > >>>> > >>>> Steve Letter > >>> > >>> I didn’t know you had to sign the disk image. I thought it was only the installer or any code. If the disk image image is notarized, does that also notarize the installer? Do you have the commands to check for notarization? I can always post them. > >>> Matt > >> > > > _______________________________________________ > Gimp-print-devel mailing list > Gim...@li... > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel |
|
From: Steve L. <sle...@ya...> - 2020-12-10 18:55:46
|
Forgot to include my results
Stephens-MacBook-Pro:Desktop sletter$ spctl -a -vvv gutenprint-5.3.4.dmg
gutenprint-5.3.4.dmg: rejected (the code is valid but does not seem to be an app)origin=Developer ID Application: Stephen Letter (63GMK36MRC)
Stephens-MacBook-Pro:Desktop sletter$ spctl -a -vvv -t execute /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg
/Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: rejected (the code is valid but does not seem to be an app)
origin=Developer ID Application: Stephen Letter (63GMK36MRC)
Stephens-MacBook-Pro:Desktop sletter$ spctl -a -vvv -t install /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg
/Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: accepted
source=Notarized Developer ID
origin=Developer ID Installer: Stephen Letter (63GMK36MRC)
Stephens-MacBook-Pro:Desktop sletter$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg
Executable=/Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg
Identifier=gutenprint-5
Format=generic
CodeDirectory v=20200 size=172 flags=0x0(none) hashes=1+2 location=embedded
Signature size=9009
Timestamp=Dec 10, 2020 at 1:08:23 PM
Info.plist=not bound
TeamIdentifier=63GMK36MRC
Sealed Resources=none
Internal requirements count=1 size=172
Stephens-MacBook-Pro:Desktop sletter$
The ones below remain the same.
Steve Letter You're never to old to learn something stupid. -- unknown
On Thursday, December 10, 2020, 01:41:10 PM EST, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
Matt,
Thanks. We make a great team. As you found, I did not sign the package. Doing that gave me results that matched Michael's 5.3.3. I replaced the disk image in snapshots. If you would can find the time I'd appreciate anything more you can do to verify it.
Steve Letter You're never to old to learn something stupid. -- unknown
On Thursday, December 10, 2020, 08:34:43 AM EST, Matt Broughton <wal...@ma...> wrote:
> On Dec 9, 2020, at 9:57 PM, Matt Broughton <wal...@ma...> wrote:
>
> Try running
> spctl -a -vvv <path to disk image> and
> spctl -a -vvv -t execute <path to package>
>
> also
>
> codesign -dv <path to disk image> and
> codesign -dv <path to package>
>
> That should give you the answer or some indication.
>
> I'll try to look at things tomorrow.
>
> Matt
>
>
>> On Dec 9, 2020, at 9:13 PM, Steve Letter <sle...@ya...> wrote:
>>
>> My understanding, everything underneath gets notarized but that’s why I am asking for testers.
>>
>> Steve Letter
>> Sent from my Symbolics Lisp Machine using rmail.
I am showing that nothing has been notarized. I am a bit confused as to the responce of codesign that the package has not been signed. pkgutil shows that the installer at least has a valid signature
Last login: Thu Dec 10 07:07:00 on ttys000
Borodin:~ matt$ spctl -a -vvv /Users/matt/Downloads/gutenprint-5.3.4-2.dmg
/Users/matt/Downloads/gutenprint-5.3.4-2.dmg: rejected
source=no usable signature
Borodin:~ matt$ codesign -dv /Users/matt/Downloads/gutenprint-5.3.4-2.dmg
/Users/matt/Downloads/gutenprint-5.3.4-2.dmg: code object is not signed at all
Borodin:~ matt$
Borodin:~ matt$
Borodin:~ matt$
/Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: rejected
source=no usable signature
Borodin:~ matt$
Borodin:~ matt$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg
/Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: code object is not signed at all
Borodin:~ matt$
Borodin:~ matt$
Package "gutenprint-5.3.4.pkg":
Status: signed by a certificate trusted by Mac OS X
Certificate Chain:
1. Developer ID Installer: Stephen Letter (63GMK36MRC)
SHA1 fingerprint: 8C 21 B8 23 C2 C7 3F C4 53 F5 A6 2E 98 AE 59 62 52 A3 A0 BF
-----------------------------------------------------------------------------
2. Developer ID Certification Authority
SHA1 fingerprint: 3B 16 6C 3B 7D C4 B7 51 C9 FE 2A FA B9 13 56 41 E3 88 E1 86
-----------------------------------------------------------------------------
3. Apple Root CA
SHA1 fingerprint: 61 1E 5B 66 2C 59 3A 08 FF 58 D1 4A E2 24 52 D1 98 DF 6C 60
Borodin:~ matt$
Matt
>>
>>> On Dec 9, 2020, at 8:31 PM, Matt <wal...@ma...> wrote:
>>>
>>>
>>>> On Dec 9, 2020, at 1:49 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
>>>>
>>>> I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should I upload it to? It is the same build (but different date / time) as the one I uploaded the other day.
>>>>
>>>> Steve Letter
>>>
>>> I didn’t know you had to sign the disk image. I thought it was only the installer or any code. If the disk image image is notarized, does that also notarize the installer? Do you have the commands to check for notarization? I can always post them.
>>> Matt
>>
>
_______________________________________________
Gimp-print-devel mailing list
Gim...@li...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
|
|
From: Steve L. <sle...@ya...> - 2020-12-10 18:40:08
|
Matt,
Thanks. We make a great team. As you found, I did not sign the package. Doing that gave me results that matched Michael's 5.3.3. I replaced the disk image in snapshots. If you would can find the time I'd appreciate anything more you can do to verify it.
Steve Letter You're never to old to learn something stupid. -- unknown
On Thursday, December 10, 2020, 08:34:43 AM EST, Matt Broughton <wal...@ma...> wrote:
> On Dec 9, 2020, at 9:57 PM, Matt Broughton <wal...@ma...> wrote:
>
> Try running
> spctl -a -vvv <path to disk image> and
> spctl -a -vvv -t execute <path to package>
>
> also
>
> codesign -dv <path to disk image> and
> codesign -dv <path to package>
>
> That should give you the answer or some indication.
>
> I'll try to look at things tomorrow.
>
> Matt
>
>
>> On Dec 9, 2020, at 9:13 PM, Steve Letter <sle...@ya...> wrote:
>>
>> My understanding, everything underneath gets notarized but that’s why I am asking for testers.
>>
>> Steve Letter
>> Sent from my Symbolics Lisp Machine using rmail.
I am showing that nothing has been notarized. I am a bit confused as to the responce of codesign that the package has not been signed. pkgutil shows that the installer at least has a valid signature
Last login: Thu Dec 10 07:07:00 on ttys000
Borodin:~ matt$ spctl -a -vvv /Users/matt/Downloads/gutenprint-5.3.4-2.dmg
/Users/matt/Downloads/gutenprint-5.3.4-2.dmg: rejected
source=no usable signature
Borodin:~ matt$ codesign -dv /Users/matt/Downloads/gutenprint-5.3.4-2.dmg
/Users/matt/Downloads/gutenprint-5.3.4-2.dmg: code object is not signed at all
Borodin:~ matt$
Borodin:~ matt$
Borodin:~ matt$ spctl -a -vvv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg
/Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: rejected
source=no usable signature
Borodin:~ matt$
Borodin:~ matt$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg
/Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: code object is not signed at all
Borodin:~ matt$
Borodin:~ matt$ pkgutil --check-signature /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg
Package "gutenprint-5.3.4.pkg":
Status: signed by a certificate trusted by Mac OS X
Certificate Chain:
1. Developer ID Installer: Stephen Letter (63GMK36MRC)
SHA1 fingerprint: 8C 21 B8 23 C2 C7 3F C4 53 F5 A6 2E 98 AE 59 62 52 A3 A0 BF
-----------------------------------------------------------------------------
2. Developer ID Certification Authority
SHA1 fingerprint: 3B 16 6C 3B 7D C4 B7 51 C9 FE 2A FA B9 13 56 41 E3 88 E1 86
-----------------------------------------------------------------------------
3. Apple Root CA
SHA1 fingerprint: 61 1E 5B 66 2C 59 3A 08 FF 58 D1 4A E2 24 52 D1 98 DF 6C 60
Borodin:~ matt$
Matt
>>
>>> On Dec 9, 2020, at 8:31 PM, Matt <wal...@ma...> wrote:
>>>
>>>
>>>> On Dec 9, 2020, at 1:49 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
>>>>
>>>> I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should I upload it to? It is the same build (but different date / time) as the one I uploaded the other day.
>>>>
>>>> Steve Letter
>>>
>>> I didn’t know you had to sign the disk image. I thought it was only the installer or any code. If the disk image image is notarized, does that also notarize the installer? Do you have the commands to check for notarization? I can always post them.
>>> Matt
>>
>
|
|
From: Matt B. <wal...@ma...> - 2020-12-10 17:38:24
|
> On Dec 10, 2020, at 11:30 AM, Steve Letter <sle...@ya...> wrote: > > This looks like it will help me understand what to do. Thanks. > > Steve Letter > Another piecer of trivial data that may or may not be relevant in the future to verify signatures When you get down to the nitty gritty of the binaries after they are installed: Borodin:~ matt$ spctl -a -vvv /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/gutenprint.5.3 /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/gutenprint.5.3: rejected (the code is valid but does not seem to be an app) origin=Developer ID Application: Stephen Letter (63GMK36MRC) Borodin:~ matt$ codesign -dv /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/gutenprint.5.3 Executable=/Library/Printers/Gutenprint.printerDriver/Contents/MacOS/gutenprint.5.3 Identifier=gutenprint.5 Format=Mach-O thin (x86_64) CodeDirectory v=20500 size=13400 flags=0x10000(runtime) hashes=413+2 location=embedded Signature size=9009 Timestamp=Dec 8, 2020 at 8:23:56 AM Info.plist=not bound TeamIdentifier=63GMK36MRC Runtime Version=10.14.0 Sealed Resources=none Internal requirements count=1 size=172 Borodin:~ matt$ I must have had too much time on my hands last night. Matt >> On Dec 10, 2020, at 12:04 PM, Matt Broughton <wal...@ma...> wrote: >> >> >> >>> On Dec 9, 2020, at 9:57 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >>> >>> I uploaded gutenprint-5.3.4.dmg to snapshots. >>> Steve Letter >> >> It is also showing as a new Mac release under Home / gutenprint-5.3 / 5.3.4. Was it your intention to make this an actual release? I don't think the installer is notarized. Compare the data shown below for the revised installer for v5.3.3 the installer for v5.3.4 >> >> >> >> ************************ >> matt$ spctl -a -vvv -t install /Volumes/gutenprint\ 5.3.3/gutenprint-5.3.3.pkg >> /Volumes/gutenprint 5.3.3/gutenprint-5.3.3.pkg: accepted >> source=Notarized Developer ID >> origin=Developer ID Installer: Stephen Letter (63GMK36MRC) >> >> matt$ spctl -a -vvv -t install /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg >> /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: accepted >> source=Notarized Developer ID >> >> **v5.3.4 is not showing an 'origin=Developer ID ... NAME' I am not sure why both show as "accepted", but I think I read that you do need to have the 'origin=Developer ' with the name of the developer. >> >> ************************** >> Compare codesign: >> Borodin:~ matt$ codesign -dv /Volumes/gutenprint\ 5.3.3/gutenprint-5.3.3.pkg >> Executable=/Volumes/gutenprint 5.3.3/gutenprint-5.3.3.pkg >> Identifier=gutenprint-5 >> Format=generic >> CodeDirectory v=20200 size=172 flags=0x0(none) hashes=1+2 location=embedded >> Signature size=9006 >> Timestamp=Nov 25, 2020 at 8:09:29 AM >> Info.plist=not bound >> TeamIdentifier=RU58A2256H >> Sealed Resources=none >> Internal requirements count=1 size=172 >> Borodin:~ matt$ >> >> Borodin:~ matt$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg >> /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: code object is not signed at all >> >> **v5.3.4 didn't return a lot of data that I think it should. >> >> I am speaking from real lack of knowledge here. I am only replying with I have read online as to how to verify that something is notarized plus what we see from the notarized package that Michael provided for v5.3.3 and what is shown for v5.3.4. >> >> Matt >> >> >>> Sent from my Symbolics Lisp Machine using rmail. >>> >>>> On Dec 9, 2020, at 10:50 PM, Steve Letter <sle...@ya...> wrote: >>>> >>>> >>>> Nevermind, I'm an idiot. >>>> >>>> Steve Letter You're never to old to learn something stupid. -- unknown >>>> >>>> >>>> On Wednesday, December 9, 2020, 10:41:04 PM EST, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >>>> >>>> >>>> Forgive my ignorance but how do I get it there? I thought this might be an scp address but when I try I get: >>>> scp: /home/frs/project/g/gi/gimp_print/snapshots/: No such file or directory >>>> >>>> >>>> Steve Letter You're never to old to learn something stupid. -- unknown >>>> >>>> >>>> On Wednesday, December 9, 2020, 10:01:19 PM EST, Robert Krawitz <rl...@al...> wrote: >>>> >>>> >>>> On 12/9/20 2:48 PM, Steve Letter via Gimp-print-devel wrote: >>>> >>>>> I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should I upload it to? It is the same build (but different date / time) as the one I uploaded the other day. >>>> >>>> >>>> snapshots would be ideal >>>> (username,gim...@fr...:/home/frs/project/g/gi/gimp-print/snapshots/ for whatever >>>> your Sourceforge username is). >>>> >>>> >>>> _______________________________________________ >>>> Gimp-print-devel mailing list >>>> Gim...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel >>>> >>>> _______________________________________________ >>>> Gimp-print-devel mailing list >>>> Gim...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel >>> _______________________________________________ >>> Gimp-print-devel mailing list >>> Gim...@li... >>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel >> |
|
From: Steve L. <sle...@ya...> - 2020-12-10 17:30:24
|
This looks like it will help me understand what to do. Thanks. Steve Letter > On Dec 10, 2020, at 12:04 PM, Matt Broughton <wal...@ma...> wrote: > > > >> On Dec 9, 2020, at 9:57 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >> >> I uploaded gutenprint-5.3.4.dmg to snapshots. >> Steve Letter > > It is also showing as a new Mac release under Home / gutenprint-5.3 / 5.3.4. Was it your intention to make this an actual release? I don't think the installer is notarized. Compare the data shown below for the revised installer for v5.3.3 the installer for v5.3.4 > > > > ************************ > matt$ spctl -a -vvv -t install /Volumes/gutenprint\ 5.3.3/gutenprint-5.3.3.pkg > /Volumes/gutenprint 5.3.3/gutenprint-5.3.3.pkg: accepted > source=Notarized Developer ID > origin=Developer ID Installer: Stephen Letter (63GMK36MRC) > > matt$ spctl -a -vvv -t install /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg > /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: accepted > source=Notarized Developer ID > > **v5.3.4 is not showing an 'origin=Developer ID ... NAME' I am not sure why both show as "accepted", but I think I read that you do need to have the 'origin=Developer ' with the name of the developer. > > ************************** > Compare codesign: > Borodin:~ matt$ codesign -dv /Volumes/gutenprint\ 5.3.3/gutenprint-5.3.3.pkg > Executable=/Volumes/gutenprint 5.3.3/gutenprint-5.3.3.pkg > Identifier=gutenprint-5 > Format=generic > CodeDirectory v=20200 size=172 flags=0x0(none) hashes=1+2 location=embedded > Signature size=9006 > Timestamp=Nov 25, 2020 at 8:09:29 AM > Info.plist=not bound > TeamIdentifier=RU58A2256H > Sealed Resources=none > Internal requirements count=1 size=172 > Borodin:~ matt$ > > Borodin:~ matt$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg > /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: code object is not signed at all > > **v5.3.4 didn't return a lot of data that I think it should. > > I am speaking from real lack of knowledge here. I am only replying with I have read online as to how to verify that something is notarized plus what we see from the notarized package that Michael provided for v5.3.3 and what is shown for v5.3.4. > > Matt > > >> Sent from my Symbolics Lisp Machine using rmail. >> >>>> On Dec 9, 2020, at 10:50 PM, Steve Letter <sle...@ya...> wrote: >>> >>> >>> Nevermind, I'm an idiot. >>> >>> Steve Letter You're never to old to learn something stupid. -- unknown >>> >>> >>>> On Wednesday, December 9, 2020, 10:41:04 PM EST, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >>> >>> >>> Forgive my ignorance but how do I get it there? I thought this might be an scp address but when I try I get: >>> scp: /home/frs/project/g/gi/gimp_print/snapshots/: No such file or directory >>> >>> >>> Steve Letter You're never to old to learn something stupid. -- unknown >>> >>> >>>> On Wednesday, December 9, 2020, 10:01:19 PM EST, Robert Krawitz <rl...@al...> wrote: >>> >>> >>>> On 12/9/20 2:48 PM, Steve Letter via Gimp-print-devel wrote: >>> >>>> I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should I upload it to? It is the same build (but different date / time) as the one I uploaded the other day. >>> >>> >>> snapshots would be ideal >>> (username,gim...@fr...:/home/frs/project/g/gi/gimp-print/snapshots/ for whatever >>> your Sourceforge username is). >>> >>> >>> _______________________________________________ >>> Gimp-print-devel mailing list >>> Gim...@li... >>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel >>> >>> _______________________________________________ >>> Gimp-print-devel mailing list >>> Gim...@li... >>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel >> _______________________________________________ >> Gimp-print-devel mailing list >> Gim...@li... >> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel > |
|
From: Matt B. <wal...@ma...> - 2020-12-10 17:27:29
|
> On Dec 10, 2020, at 11:05 AM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: > > Just to add to the confusion... > > Steve Letter > > Begin forwarded message: > >> From: Apple Developer <no_...@em...> >> Date: December 9, 2020 at 11:45:59 PM EST >> To: sle...@ya... >> Subject: Your Mac software was successfully notarized. >> >> >> <x-msg://10/$%7Btext.developer-URL%7D> >> Dear Stephen, >> >> Your Mac software has been notarized. You can now export this software and distribute it directly to users. >> >> Bundle Identifier: my-app.myapp >> Request Identifier: f3497ee2-5824-46b6-b94d-f6cfd329f61d >> >> For details on exporting a notarized app, visit Xcode Help <https://help.apple.com/xcode/mac/current/#/dev88332a81e?sub=dev8a32007db> or the notarization guide <https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution>. >> Best Regards, >> Apple Developer Relations >> >> >> >> >> TM and © 2018 Apple Inc. >> One Apple Park Way, MS 301-1TEV, Cupertino, CA 95014. >> >> All Rights Reserved <http://www.apple.com/legal/> | Privacy Policy <http://www.apple.com/legal/privacy/> | Account <https://developer.apple.com/account/> As I mentioned, all this is stuff is above my ken. Quoting Hogan's Heros Sgt. Schultz. "I know nothing -- nothing". Matt |
|
From: Matt B. <wal...@ma...> - 2020-12-10 17:17:23
|
> On Dec 10, 2020, at 11:09 AM, Steve Letter <sle...@ya...> wrote: > > They are not the same. Under home is a release for Michael to notarize (was my intention). > > Steve Letter OK. I don't know what arrangements you made with Michael. To me, it just looked like a formal release in that directory and there are already 49 downloads. Matt > >> On Dec 10, 2020, at 12:04 PM, Matt Broughton <wal...@ma...> wrote: >> >> >> >>> On Dec 9, 2020, at 9:57 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >>> >>> I uploaded gutenprint-5.3.4.dmg to snapshots. >>> Steve Letter >> >> It is also showing as a new Mac release under Home / gutenprint-5.3 / 5.3.4. Was it your intention to make this an actual release? I don't think the installer is notarized. Compare the data shown below for the revised installer for v5.3.3 the installer for v5.3.4 >> >> >> >> ************************ >> matt$ spctl -a -vvv -t install /Volumes/gutenprint\ 5.3.3/gutenprint-5.3.3.pkg >> /Volumes/gutenprint 5.3.3/gutenprint-5.3.3.pkg: accepted >> source=Notarized Developer ID >> origin=Developer ID Installer: Stephen Letter (63GMK36MRC) >> >> matt$ spctl -a -vvv -t install /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg >> /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: accepted >> source=Notarized Developer ID >> >> **v5.3.4 is not showing an 'origin=Developer ID ... NAME' I am not sure why both show as "accepted", but I think I read that you do need to have the 'origin=Developer ' with the name of the developer. >> >> ************************** >> Compare codesign: >> Borodin:~ matt$ codesign -dv /Volumes/gutenprint\ 5.3.3/gutenprint-5.3.3.pkg >> Executable=/Volumes/gutenprint 5.3.3/gutenprint-5.3.3.pkg >> Identifier=gutenprint-5 >> Format=generic >> CodeDirectory v=20200 size=172 flags=0x0(none) hashes=1+2 location=embedded >> Signature size=9006 >> Timestamp=Nov 25, 2020 at 8:09:29 AM >> Info.plist=not bound >> TeamIdentifier=RU58A2256H >> Sealed Resources=none >> Internal requirements count=1 size=172 >> Borodin:~ matt$ >> >> Borodin:~ matt$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg >> /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: code object is not signed at all >> >> **v5.3.4 didn't return a lot of data that I think it should. >> >> I am speaking from real lack of knowledge here. I am only replying with I have read online as to how to verify that something is notarized plus what we see from the notarized package that Michael provided for v5.3.3 and what is shown for v5.3.4. >> >> Matt >> >> >>> Sent from my Symbolics Lisp Machine using rmail. >>> >>>> On Dec 9, 2020, at 10:50 PM, Steve Letter <sle...@ya...> wrote: >>>> >>>> >>>> Nevermind, I'm an idiot. >>>> >>>> Steve Letter You're never to old to learn something stupid. -- unknown >>>> >>>> >>>> On Wednesday, December 9, 2020, 10:41:04 PM EST, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >>>> >>>> >>>> Forgive my ignorance but how do I get it there? I thought this might be an scp address but when I try I get: >>>> scp: /home/frs/project/g/gi/gimp_print/snapshots/: No such file or directory >>>> >>>> >>>> Steve Letter You're never to old to learn something stupid. -- unknown >>>> >>>> >>>> On Wednesday, December 9, 2020, 10:01:19 PM EST, Robert Krawitz <rl...@al...> wrote: >>>> >>>> >>>> On 12/9/20 2:48 PM, Steve Letter via Gimp-print-devel wrote: >>>> >>>>> I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should I upload it to? It is the same build (but different date / time) as the one I uploaded the other day. >>>> >>>> >>>> snapshots would be ideal >>>> (username,gim...@fr...:/home/frs/project/g/gi/gimp-print/snapshots/ for whatever >>>> your Sourceforge username is). >>>> >>>> >>>> _______________________________________________ >>>> Gimp-print-devel mailing list >>>> Gim...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel >>>> >>>> _______________________________________________ >>>> Gimp-print-devel mailing list >>>> Gim...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel >>> _______________________________________________ >>> Gimp-print-devel mailing list >>> Gim...@li... >>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel >> |
|
From: Steve L. <sle...@ya...> - 2020-12-10 17:10:10
|
They are not the same. Under home is a release for Michael to notarize (was my intention). Steve Letter > On Dec 10, 2020, at 12:04 PM, Matt Broughton <wal...@ma...> wrote: > > > >> On Dec 9, 2020, at 9:57 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >> >> I uploaded gutenprint-5.3.4.dmg to snapshots. >> Steve Letter > > It is also showing as a new Mac release under Home / gutenprint-5.3 / 5.3.4. Was it your intention to make this an actual release? I don't think the installer is notarized. Compare the data shown below for the revised installer for v5.3.3 the installer for v5.3.4 > > > > ************************ > matt$ spctl -a -vvv -t install /Volumes/gutenprint\ 5.3.3/gutenprint-5.3.3.pkg > /Volumes/gutenprint 5.3.3/gutenprint-5.3.3.pkg: accepted > source=Notarized Developer ID > origin=Developer ID Installer: Stephen Letter (63GMK36MRC) > > matt$ spctl -a -vvv -t install /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg > /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: accepted > source=Notarized Developer ID > > **v5.3.4 is not showing an 'origin=Developer ID ... NAME' I am not sure why both show as "accepted", but I think I read that you do need to have the 'origin=Developer ' with the name of the developer. > > ************************** > Compare codesign: > Borodin:~ matt$ codesign -dv /Volumes/gutenprint\ 5.3.3/gutenprint-5.3.3.pkg > Executable=/Volumes/gutenprint 5.3.3/gutenprint-5.3.3.pkg > Identifier=gutenprint-5 > Format=generic > CodeDirectory v=20200 size=172 flags=0x0(none) hashes=1+2 location=embedded > Signature size=9006 > Timestamp=Nov 25, 2020 at 8:09:29 AM > Info.plist=not bound > TeamIdentifier=RU58A2256H > Sealed Resources=none > Internal requirements count=1 size=172 > Borodin:~ matt$ > > Borodin:~ matt$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg > /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: code object is not signed at all > > **v5.3.4 didn't return a lot of data that I think it should. > > I am speaking from real lack of knowledge here. I am only replying with I have read online as to how to verify that something is notarized plus what we see from the notarized package that Michael provided for v5.3.3 and what is shown for v5.3.4. > > Matt > > >> Sent from my Symbolics Lisp Machine using rmail. >> >>>> On Dec 9, 2020, at 10:50 PM, Steve Letter <sle...@ya...> wrote: >>> >>> >>> Nevermind, I'm an idiot. >>> >>> Steve Letter You're never to old to learn something stupid. -- unknown >>> >>> >>>> On Wednesday, December 9, 2020, 10:41:04 PM EST, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >>> >>> >>> Forgive my ignorance but how do I get it there? I thought this might be an scp address but when I try I get: >>> scp: /home/frs/project/g/gi/gimp_print/snapshots/: No such file or directory >>> >>> >>> Steve Letter You're never to old to learn something stupid. -- unknown >>> >>> >>>> On Wednesday, December 9, 2020, 10:01:19 PM EST, Robert Krawitz <rl...@al...> wrote: >>> >>> >>>> On 12/9/20 2:48 PM, Steve Letter via Gimp-print-devel wrote: >>> >>>> I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should I upload it to? It is the same build (but different date / time) as the one I uploaded the other day. >>> >>> >>> snapshots would be ideal >>> (username,gim...@fr...:/home/frs/project/g/gi/gimp-print/snapshots/ for whatever >>> your Sourceforge username is). >>> >>> >>> _______________________________________________ >>> Gimp-print-devel mailing list >>> Gim...@li... >>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel >>> >>> _______________________________________________ >>> Gimp-print-devel mailing list >>> Gim...@li... >>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel >> _______________________________________________ >> Gimp-print-devel mailing list >> Gim...@li... >> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel > |
|
From: Steve L. <sle...@ya...> - 2020-12-10 17:06:04
|
Just to add to the confusion... Steve Letter Begin forwarded message: > From: Apple Developer <no_...@em...> > Date: December 9, 2020 at 11:45:59 PM EST > To: sle...@ya... > Subject: Your Mac software was successfully notarized. > > > > Dear Stephen, > > Your Mac software has been notarized. You can now export this software and distribute it directly to users. > > Bundle Identifier: my-app.myapp > Request Identifier: f3497ee2-5824-46b6-b94d-f6cfd329f61d > > For details on exporting a notarized app, visit Xcode Help or the notarization guide. > Best Regards, > Apple Developer Relations > > > > TM and © 2018 Apple Inc. > One Apple Park Way, MS 301-1TEV, Cupertino, CA 95014. > > All Rights Reserved | Privacy Policy | Account |
|
From: Matt B. <wal...@ma...> - 2020-12-10 17:05:04
|
> On Dec 9, 2020, at 9:57 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: > > I uploaded gutenprint-5.3.4.dmg to snapshots. > Steve Letter It is also showing as a new Mac release under Home / gutenprint-5.3 / 5.3.4. Was it your intention to make this an actual release? I don't think the installer is notarized. Compare the data shown below for the revised installer for v5.3.3 the installer for v5.3.4 ************************ matt$ spctl -a -vvv -t install /Volumes/gutenprint\ 5.3.3/gutenprint-5.3.3.pkg /Volumes/gutenprint 5.3.3/gutenprint-5.3.3.pkg: accepted source=Notarized Developer ID origin=Developer ID Installer: Stephen Letter (63GMK36MRC) matt$ spctl -a -vvv -t install /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: accepted source=Notarized Developer ID **v5.3.4 is not showing an 'origin=Developer ID ... NAME' I am not sure why both show as "accepted", but I think I read that you do need to have the 'origin=Developer ' with the name of the developer. ************************** Compare codesign: Borodin:~ matt$ codesign -dv /Volumes/gutenprint\ 5.3.3/gutenprint-5.3.3.pkg Executable=/Volumes/gutenprint 5.3.3/gutenprint-5.3.3.pkg Identifier=gutenprint-5 Format=generic CodeDirectory v=20200 size=172 flags=0x0(none) hashes=1+2 location=embedded Signature size=9006 Timestamp=Nov 25, 2020 at 8:09:29 AM Info.plist=not bound TeamIdentifier=RU58A2256H Sealed Resources=none Internal requirements count=1 size=172 Borodin:~ matt$ Borodin:~ matt$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: code object is not signed at all **v5.3.4 didn't return a lot of data that I think it should. I am speaking from real lack of knowledge here. I am only replying with I have read online as to how to verify that something is notarized plus what we see from the notarized package that Michael provided for v5.3.3 and what is shown for v5.3.4. Matt > Sent from my Symbolics Lisp Machine using rmail. > >> On Dec 9, 2020, at 10:50 PM, Steve Letter <sle...@ya...> wrote: >> >> >> Nevermind, I'm an idiot. >> >> Steve Letter You're never to old to learn something stupid. -- unknown >> >> >> On Wednesday, December 9, 2020, 10:41:04 PM EST, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >> >> >> Forgive my ignorance but how do I get it there? I thought this might be an scp address but when I try I get: >> scp: /home/frs/project/g/gi/gimp_print/snapshots/: No such file or directory >> >> >> Steve Letter You're never to old to learn something stupid. -- unknown >> >> >> On Wednesday, December 9, 2020, 10:01:19 PM EST, Robert Krawitz <rl...@al...> wrote: >> >> >> On 12/9/20 2:48 PM, Steve Letter via Gimp-print-devel wrote: >> >> > I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should I upload it to? It is the same build (but different date / time) as the one I uploaded the other day. >> >> >> snapshots would be ideal >> (username,gim...@fr...:/home/frs/project/g/gi/gimp-print/snapshots/ for whatever >> your Sourceforge username is). >> >> >> _______________________________________________ >> Gimp-print-devel mailing list >> Gim...@li... >> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel >> >> _______________________________________________ >> Gimp-print-devel mailing list >> Gim...@li... >> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel > _______________________________________________ > Gimp-print-devel mailing list > Gim...@li... > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel |
|
From: Robert K. <rl...@al...> - 2020-12-10 16:06:56
|
On 12/9/20 10:40 PM, Steve Letter via Gimp-print-devel wrote: > Forgive my ignorance but how do I get it there? I thought this might be an scp address but when I > try I get: > scp: /home/frs/project/g/gi/gimp_print/snapshots/: No such file or directory typo -- gimp_print -> gimp-print > Steve Letter You're never to old to learn something stupid. -- unknown > > > On Wednesday, December 9, 2020, 10:01:19 PM EST, Robert Krawitz <rl...@al...> wrote: > > > On 12/9/20 2:48 PM, Steve Letter via Gimp-print-devel wrote: > >> I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should > I upload it to? It is the same build (but different date / time) as the one I uploaded the other day. scp file sletter,gim...@fr...urceforgennet:/home/frs/project/g/gi/gimp-print/snapshots |
|
From: Matt B. <wal...@ma...> - 2020-12-10 13:34:57
|
> On Dec 9, 2020, at 9:57 PM, Matt Broughton <wal...@ma...> wrote:
>
> Try running
> spctl -a -vvv <path to disk image> and
> spctl -a -vvv -t execute <path to package>
>
> also
>
> codesign -dv <path to disk image> and
> codesign -dv <path to package>
>
> That should give you the answer or some indication.
>
> I'll try to look at things tomorrow.
>
> Matt
>
>
>> On Dec 9, 2020, at 9:13 PM, Steve Letter <sle...@ya...> wrote:
>>
>> My understanding, everything underneath gets notarized but that’s why I am asking for testers.
>>
>> Steve Letter
>> Sent from my Symbolics Lisp Machine using rmail.
I am showing that nothing has been notarized. I am a bit confused as to the responce of codesign that the package has not been signed. pkgutil shows that the installer at least has a valid signature
Last login: Thu Dec 10 07:07:00 on ttys000
Borodin:~ matt$ spctl -a -vvv /Users/matt/Downloads/gutenprint-5.3.4-2.dmg
/Users/matt/Downloads/gutenprint-5.3.4-2.dmg: rejected
source=no usable signature
Borodin:~ matt$ codesign -dv /Users/matt/Downloads/gutenprint-5.3.4-2.dmg
/Users/matt/Downloads/gutenprint-5.3.4-2.dmg: code object is not signed at all
Borodin:~ matt$
Borodin:~ matt$
Borodin:~ matt$ spctl -a -vvv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg
/Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: rejected
source=no usable signature
Borodin:~ matt$
Borodin:~ matt$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg
/Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: code object is not signed at all
Borodin:~ matt$
Borodin:~ matt$ pkgutil --check-signature /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg
Package "gutenprint-5.3.4.pkg":
Status: signed by a certificate trusted by Mac OS X
Certificate Chain:
1. Developer ID Installer: Stephen Letter (63GMK36MRC)
SHA1 fingerprint: 8C 21 B8 23 C2 C7 3F C4 53 F5 A6 2E 98 AE 59 62 52 A3 A0 BF
-----------------------------------------------------------------------------
2. Developer ID Certification Authority
SHA1 fingerprint: 3B 16 6C 3B 7D C4 B7 51 C9 FE 2A FA B9 13 56 41 E3 88 E1 86
-----------------------------------------------------------------------------
3. Apple Root CA
SHA1 fingerprint: 61 1E 5B 66 2C 59 3A 08 FF 58 D1 4A E2 24 52 D1 98 DF 6C 60
Borodin:~ matt$
Matt
>>
>>> On Dec 9, 2020, at 8:31 PM, Matt <wal...@ma...> wrote:
>>>
>>>
>>>> On Dec 9, 2020, at 1:49 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
>>>>
>>>> I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should I upload it to? It is the same build (but different date / time) as the one I uploaded the other day.
>>>>
>>>> Steve Letter
>>>
>>> I didn’t know you had to sign the disk image. I thought it was only the installer or any code. If the disk image image is notarized, does that also notarize the installer? Do you have the commands to check for notarization? I can always post them.
>>> Matt
>>
>
|
|
From: Steve L. <sle...@ya...> - 2020-12-10 03:57:48
|
I uploaded gutenprint-5.3.4.dmg to snapshots. Steve Letter Sent from my Symbolics Lisp Machine using rmail. > On Dec 9, 2020, at 10:50 PM, Steve Letter <sle...@ya...> wrote: > > > Nevermind, I'm an idiot. > > Steve Letter You're never to old to learn something stupid. -- unknown > > > On Wednesday, December 9, 2020, 10:41:04 PM EST, Steve Letter via Gimp-print-devel <gim...@li...> wrote: > > > Forgive my ignorance but how do I get it there? I thought this might be an scp address but when I try I get: > scp: /home/frs/project/g/gi/gimp_print/snapshots/: No such file or directory > > > Steve Letter You're never to old to learn something stupid. -- unknown > > > On Wednesday, December 9, 2020, 10:01:19 PM EST, Robert Krawitz <rl...@al...> wrote: > > > On 12/9/20 2:48 PM, Steve Letter via Gimp-print-devel wrote: > > > I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should I upload it to? It is the same build (but different date / time) as the one I uploaded the other day. > > > snapshots would be ideal > (username,gim...@fr...:/home/frs/project/g/gi/gimp-print/snapshots/ for whatever > your Sourceforge username is). > > > _______________________________________________ > Gimp-print-devel mailing list > Gim...@li... > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel > > _______________________________________________ > Gimp-print-devel mailing list > Gim...@li... > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel |
137 messages has been excluded from this view by a project administrator.
