Gpgtools MacGPG2 → 2.0.18

Comments and changes to this ticket

• You flagged this item as spam.
  

  Alex (via GPGTools) January 29th, 2011 @ 07:25 PM

  @Mento / Benjamin: should we introduce a Pinentry issue repository?

• You flagged this item as spam.
  

  Benjamin Donnachie January 29th, 2011 @ 07:30 PM

  MacGPG2 now only uses the GPGTools pinentry, which is derived from mine.

  I suspect that this may be another feature of the OS' secure input box but no time to test at the moment.

• You flagged this item as spam.
  

  Benjamin Donnachie January 29th, 2011 @ 08:45 PM

  Subject to available time, I'll work with you on this.

• You flagged this item as spam.
  

  Benjamin Donnachie January 30th, 2011 @ 02:53 AM

  Linked with http://lists.apple.com/archives/student-dev/2006/Apr/msg00052.html but no solution shown.

• You flagged this item as spam.
  

  Mento January 30th, 2011 @ 06:21 PM

  • State changed from “open” to “invalid”
  • Tag set to “unsolvable”
  • Assigned user cleared.

  This is a bug in NSSecureTextField.

• You flagged this item as spam.
  

  Alex (via GPGTools) January 30th, 2011 @ 06:42 PM

  • Assigned user set to “Benjamin Donnachie”

  Do you have an Apple issue ID (or s.th. similar) for that?

• You flagged this item as spam.
  

  Mento January 30th, 2011 @ 07:10 PM

  • Assigned user set to “Benjamin Donnachie”

  No

• You flagged this item as spam.
  

  Benjamin Donnachie January 30th, 2011 @ 07:30 PM

  • State changed from “invalid” to “open”
  • Milestone cleared.
  • Tag cleared.
  • Importance changed from “High” to “Low”

  As fully documented, this will be considered a "feature" rather than a bug.

  I will look into overriding an existing class to provide this function. Linked to #26

• You flagged this item as spam.
  

  Alex (via GPGTools) December 28th, 2011 @ 01:26 PM

  • Milestone set to “2.0.18”
  • Importance changed from “High” to “”

  [bulk edit]

• 

  steve January 3rd, 2012 @ 03:21 PM

  • State changed from “open” to “wontfix”

  This is not possible in any password field on a mac (accents or ñ ect).

• You flagged this item as spam.
  

  Benjamin Donnachie January 3rd, 2012 @ 04:06 PM

  A new input class could be created that inherits from the working one
  rather than using the provided secure field class.

• You flagged this item as spam.
  

  Mento January 4th, 2012 @ 11:50 AM

  • Assigned user cleared.
  • State changed from “waiting” to “wontfix”

  Sollte sich jemand finden, der es sich antun will das Passwortfeld entsprechend anzupassen, dann kann er es machen.
  Ich werde das sicher nicht machen und auch niemanden empfehlen, da es ein nicht unerheblicher Aufwand ist.
  Solch ein Verhalten ist ausserdem unter Mac nicht vorgesehen.
  Des weiteren funktioniert Copy & Paste und auch Show Typing ist eine Möglichkeit.

• You flagged this item as spam.
  

  Benjamin Donnachie January 4th, 2012 @ 12:09 PM

  But accents are not. As previously stated, I can do this but it will join
  a long to-do list.

  2012/1/4 Lighthouse <no-reply@lighthouseapp.com>

• 

  steve January 4th, 2012 @ 12:19 PM

  • Assigned user set to “Benjamin Donnachie”
  • State changed from “wontfix” to “hold”
  • Tag set to “low priority”

  Sure. Thanks Ben, just do it whenever you find the time (-> hold / Ben).

• 

  Support January 22nd, 2012 @ 12:10 PM

  Assigned to Tender discussion #208.

• 

  steve September 26th, 2016 @ 10:54 AM

  • State changed from “open” to “wontfix”
  • Tag cleared.
  • Assigned user cleared.
  • Importance changed from “” to “Low”