-
-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rong Build option: NO_SECUREZEROMEMORY #18
Comments
This option is necessary to build KiTTY. |
Sorry @cyd01 , you can explain why? |
You are absolutely right.
It can compile without it. I can remember when (and why) I've added this
compilation flag.
Now I have to test all the others:
-DAUTO_WINSOCK -DUSE_CAPI -DCOVERITY -DNO_MULTIMON -DNO_HTMLHELP
Le ven. 31 mai 2019 à 12:08, Lars The <notifications@github.com> a écrit :
… This option is necessary to build KiTTY.
Sorry @cyd01 <https://github.com/cyd01> , you can explain why?
Perhaps a workaround it's possible.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18?email_source=notifications&email_token=AIESOBXQGOJHCCYZBGSDVF3PYD2JLA5CNFSM4HOXHYDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWUZ62A#issuecomment-497655656>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIESOBRXCZXGTGK3KGSQJOLPYD2JLANCNFSM4HOXHYDA>
.
|
So please reopen this issue (you can @cyd01 as moderator) until you finish it. |
USE_CAPI is necessary for WINCRYPTPORT. As it is broken with PuTTY 0.71, I
remove it.
I need NO_HTMLHELP because my environment does not have htmlhelp.h (from
winhelp.c).
I need NO_MULTIMON because my environment does not have multimon.h (from
window.c)
I need COVERITY because CRYPTPROTECTMEMORY_BLOCK_SIZE and
CRYPTPROTECTMEMORY_CROSS_PROCESS are unknown (in winshare.c)
I need AUTO_WINSOCK because without it ERROR_BROKEN_PIPE and
BROKEN_PIPE_ERROR_CODE are unknown (in sshshare.c).
Le ven. 31 mai 2019 à 13:09, Cyril DUPONT <cyrildupont71@gmail.com> a
écrit :
… You are absolutely right.
It can compile without it. I can remember when (and why) I've added this
compilation flag.
Now I have to test all the others:
-DAUTO_WINSOCK -DUSE_CAPI -DCOVERITY -DNO_MULTIMON -DNO_HTMLHELP
Le ven. 31 mai 2019 à 12:08, Lars The ***@***.***> a écrit :
> This option is necessary to build KiTTY.
>
> Sorry @cyd01 <https://github.com/cyd01> , you can explain why?
> Perhaps a workaround it's possible.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#18?email_source=notifications&email_token=AIESOBXQGOJHCCYZBGSDVF3PYD2JLA5CNFSM4HOXHYDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWUZ62A#issuecomment-497655656>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AIESOBRXCZXGTGK3KGSQJOLPYD2JLANCNFSM4HOXHYDA>
> .
>
|
Hi @cyd01 ,
I recommend to not include any CAPI/CAC support inside KiTTY. For this functionality it's preferable to use the Pageant from the PuTTY-CAC project: https://github.com/NoMoreFood/putty-cac
Ok.
Umm... CRYPTPROTECTMEMORY_BLOCK_SIZE and CRYPTPROTECTMEMORY_CROSS_PROCESS are defined (if not) in
BROKEN_PIPE_ERROR_CODE is defined as ERROR_BROKEN_PIPE: And ERROR_BROKEN_PIPE (109L) is part of the Windows Errors: So review the dependencies, please. |
Hi, This issue can be closed? |
yes
Le ven. 14 juin 2019 à 11:14, Lars The <notifications@github.com> a écrit :
… Hi,
This issue can be closed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18?email_source=notifications&email_token=AIESOBXQ6NV655B2TXZ34IDP2NOP5A5CNFSM4HOXHYDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXWHEMQ#issuecomment-502034994>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIESOBSHBYJ7IA7CZCCXEETP2NOP5ANCNFSM4HOXHYDA>
.
|
So, please @cyd01 do it! |
The compilation directive -DNO_SECUREZEROMEMORY was removed from Makefile. |
it apiers only with the 0.71 version the Build option NO_SECUREZEROMEMORY is set.
The text was updated successfully, but these errors were encountered: