c++ - If a winsock2 socket is non-blocking, would an SSL object associated with it also exhibit non-blocking behavior? -

-

i'm asking question because unsure whether ssl object treats socket sink/source messages bio object. gut telling me yes, i'm not certain.

goal: integrating ssl authentication existing tcp code. rather calling conventional send()/receive(), direct messages through openssl's ssl_read()/ssl_write() instead. other requirement communication non-blocking , data can partially sent.

here's how i've associated ssl object socket (server code).

ssl_init(std::wstring &peer_hostname, socket sock){         //...         //initialize ssl structure                 ssl = ssl_new(context);                 if (ssl == null){                     mr = appzreturn(e_fail, l"%ls (%d) : ssl_new failed. unable create ssl structure", __functionw__, __line__);                 }                  //agent uses winsock class, openssl uses unix socket. surpressed warning added here 4244. works                 if (ssl_set_fd(ssl, sock) == 0){    //set file descriptor ssl                     //operation failed                     return -1;         }         //...         int status = ssl_accept(ssl);            ssl_set_mode(ssl, ssl_mode_accept_moving_write_buffer|ssl_mode_enable_partial_write);         //...     }

according documentation ssl_read() [https://www.openssl.org/docs/ssl/ssl_read.html], ssl non-blocking if underlying bio non-blocking. if assumption correct, mean if socket non-blocking, ssl well?

extension of question: winsock tcp socket non-blocking default (assuming have created tcp socket, have not called ioctlsocket , set non-blocking mode)

thank taking time read this. it's appreciated.

if assumption correct, mean if socket non-blocking, ssl well?

yes.

is winsock tcp socket non-blocking default (assuming have created tcp socket, have not called ioctlsocket , set non-blocking mode)

unix sockets default blocking. haven't used winsock. sure winsock should default blocking.


Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall...
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge...
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co...
Read more