Invalid core.invalidfd in Win64 about luasec HOT 7 CLOSED

Could you tell me the parameters of SSL_set_fd() on win64? (ssl.h)
I think we have another problem...

from luasec.

I think so, but not very urgent.

Same as in win32: SSL_set_fd(SSL *s, int fd) but int is 64-bit.

I think that normal fd fits into lua number, but invalidfd in win64 not.
I have two ideas how to fix it:

1. clean solution - reimplement fd as light userdata
2. fast dirty - remove invalidfd constant and add two methods isvalidfd and invalidatefd

from luasec.

Sorry, but I think "int" is not 64 bits on win64.

from luasec.

You are right, my mistake - int is 32bit
But in win64 SOCKET and INVALID_SOCKET size is 64bit (UINT_PTR)

from luasec.

I temporary solve the problem this way:

--- a/src/ssl.lua
+++ b/src/ssl.lua
@@ -126,7 +126,8 @@ function wrap(sock, cfg)
local s, msg = core.create(ctx)
if s then
core.setfd(s, sock:getfd())

•  sock:setfd(core.invalidfd)
  

•  --sock:setfd(core.invalidfd)
  

•  sock:setfd(-1)
  

  registry[s] = ctx
  return s
  end

Works for me in linux32/64 and win32/64, lua 5.1 and 5.2

from luasec.

It seems that LuaSocket transforms -1 into INVALID_SOCKET.

Other libraries, like luaevent, use the descriptor directly. Luckily (or not), when we cast (-1) to uint32 or uint64 we have UINT32_MAX (UINT64_MAX), that is INVALID_SOCKET on win32/64.

from luasec.

Note: if Windows returns big numbers for socket, we still have problem due to double representation. Integer numbers of Lua 5.3 can help us...

from luasec.