648 reputation
517
bio website
location
age 26
visits member for 3 years, 9 months
seen Apr 9 at 15:23

Graduated 2010 in Computer Science and Spanish, now working professionally in iOS development.


Jun
2
comment Security for data produced by ASP.NET web serivce
@Steven A. Lowe - no smokescreen. I've been told that SSL plus some kind of key will indeed solve the security issue, but that it would be better to find another way in order to avoid the cost of setting up an SSL certificate, which I've been told is more than is being indicated here.
Jun
1
comment Security for data produced by ASP.NET web serivce
SSL will take a nontrivial amount of time to implement, because the site getting the certificate needs a unique IP, which means more router settings and stuff like that to configure.
Jun
1
comment Security for data produced by ASP.NET web serivce
The problem isn't as much the cost of buying the certificate as assigning the site a unique IP and the associated setup with that.
Jun
1
comment Security for data produced by ASP.NET web serivce
You mean without also doing something like SSL? Requests are made via HTTP, so anyone can watch the traffic and see what parameters are being passed. If not, then see my edit to the question to clarify.
Jun
1
revised Security for data produced by ASP.NET web serivce
Clarified (see EDIT section)
Jun
1
comment Security for data produced by ASP.NET web serivce
Also, I believe you mean "there really isn't a good reason to be so stuck in 2004", or whatever year ASP 2.0 came out in. And you're right, and I'd love to be using newer stuff if only for the cool new C# 3.0/3.5/4.0 language features, but that's the basis for the platform I'm building on top of.
Jun
1
comment Security for data produced by ASP.NET web serivce
I want to avoid SOAP if possible, though. And is the concept of SOAP encryption useless if it's not already under SSL? My understanding of SOAP is that it's a fancier, more purposed XML structure. SOAP encryption just encrypts the meaningful data in the structure, as explained halfway down the page in the link I provided, under "Next comes the response:"
Jun
1
comment Security for data produced by ASP.NET web serivce
I want my data protected, but setting up SSL is apparently a pain, so I've been told to find other options and find out how this is done elsewhere (i.e. banks)
Jun
1
awarded  Commentator
Jun
1
comment Best practices for web application Authentication/Security (Any Platform)
What's the reasoning behind using SSL instead of rolling one's own encryption? Would you consider using something like WS-Security rolling your own encryption? Setting up SSL can be a pain.
Jun
1
asked Security for data produced by ASP.NET web serivce
May
24
accepted Do testers have to look at source code?
May
24
awarded  Teacher
May
24
answered How do you tell if advice from a senior developer is bad?
May
20
asked Do testers have to look at source code?
May
12
comment Coming up with a version control strategy for SVN
Are you saying that only tested, production-ready code should be in trunk? I think any code that is committed should build and probably pass tests, and trunk code should of course pass tests. But it seems like the purpose of SVN is to be able to follow development history, and that's easier if it's not split across multiple branches. Perhaps there should be a branch that you merge trunk into when trunk is in a tested, production-ready state?
May
11
accepted Subversion/source control only for production code?
May
11
awarded  Scholar
May
11
accepted Un-Explainable Bugs?
May
6
asked Un-Explainable Bugs?