Git Winch Guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
gitlabapitoken1 [2025/07/02 16:28] – admingitlabapitoken1 [2025/07/09 20:20] (current) – admin
Line 9: Line 9:
 And in the .ini file you must make sure that the //GitSys=// must be given one of the 3 values: //Github or Gitea or Gitlab//   And in the .ini file you must make sure that the //GitSys=// must be given one of the 3 values: //Github or Gitea or Gitlab//  
  
-**Encrypted Version of this PAT**\\+**//You should NEVER EVER share the PAT itself with anyone!//**\\
 Sometimes, an owner may not want to do all the work of creating of a repository and adding/removing members of a repository from within //Git Winch// itself. But instead, the owner may decide to make someone else the manager and make that manager do all that work.   Sometimes, an owner may not want to do all the work of creating of a repository and adding/removing members of a repository from within //Git Winch// itself. But instead, the owner may decide to make someone else the manager and make that manager do all that work.  
  
-The problem now is that if the manager is given this PAT directly, that would be a security risk for the owner: The said manager can get free access to the entire Git Host of the owner. Also, the manager may end up sharing that key to someone else who can wreak havoc.+The problem now is that if the manager is given this PAT directly, that would be a security risk for the owner: The said manager can get free access to the entire Git Host of the owner. Also, the manager may end up sharing that key to someone else who can wreak havoc. **//So, never share a PAT!//** 
 + 
 +**Encrypted Version of this PAT**\\ 
 +//We have a solution on how to delegate work to manager://
  
-**//In short: You should NEVER EVER share the PAT itself with anyone!//**+**Right click on this PAT input box** (once you; as an owner, has written the correct PAT in there). //Git Winch// will now encrypt that PAT for you.
  
-//We have solution on how to delegate work to manager://+You would be asked for the //username// of the manager you want to delegate work to. The PAT would be encrypted specifically for that manager only and copied to the clipboard. 
  
-Right click on this PAT edit box (once you as an owner has written the PAT in there). Git Winch will now encrypt that PAT for you.+Then you (again, assuming you are the owner) can send that encrypted PAT to the manager. By email/Whatsapp/Signal/etc. Do NOT use the chat system inside //Git Winch's web-app// as that is a group chat.
  
-You would be asked for the //username// of the manager you want to pass on the key to. The PAT would be encrypted specifically for that manager only and copied to the clipboard. Then you can send that encrypted PAT to the manager. The manager, now can use that encrypted key to do the work on behalf of the owner, from inside //Git Winch// The owner is assured that the PAT is reasonably protected and there are now lesser chances that the owner's Git host will be misused.+The manager, now can use that encrypted key to do the work on behalf of the owner, from inside //Git Winch.// The owner is assured that the PAT is reasonably protected and there are now lesser chances that the owner's Git host will be misused.
  
 Read more how the [[/encryptedPAT?do=export_xhtml|manager uses this encrypted PAT here]] Read more how the [[/encryptedPAT?do=export_xhtml|manager uses this encrypted PAT here]]
gitlabapitoken1.1751466482.txt.gz · Last modified: by admin

Page Tools